chore: align AIOpsLab fork with upstream baseline

[vitrixLab]

Purpose

This PR is the clean upstream-alignment successor to closed PR #3. PR #3 remains closed/not merged and is treated as historical provenance only.

It does not replay the internship branch or its historical merge commits.

Base

• Target: vitrixLab/AIOpsLab:main
• Head: vitrixLab/AIOpsLab:cleanup/align-aiopslab-main
• Head SHA: b9a814e75a98e670787dac7c2ed6794b4b68dae2
• Upstream reference: microsoft/AIOpsLab:main
• Upstream SHA: b9a814e75a98e670787dac7c2ed6794b4b68dae2

The cleanup branch is an exact snapshot of the selected upstream baseline.

Cleanup rationale

The previous PR #3 proposed integrating historical internship material from the internship repository. That repository is now treated as archive/historical context, not as the active integration path.

This PR intentionally:

• does not replay historical merge commits;
• does not modify historical branches;
• does not modify PR Integrate AIOpsLab Internship Infrastructure and SC-MVP Documentation #3;
• does not introduce application code, dependencies, or new workflows.

Starting from current upstream main excludes the previously identified VitrixLab-only SC-MVP Node workflow and REVIEW.md.

Preserved

• Current upstream AIOpsLab tree
• aiopslab-applications submodule boundary
• Upstream Python/Kubernetes architecture
• Upstream LICENSE and README forms

No legal or maintainer decision on future LICENSE/README attribution is implied.

Non-goals

• No Node.js → Python application rewrite is proposed. The audit established that the Node surface was CI-only.
• No modification of vitrixLab/AIOpsLab:main is made by the branch itself.
• No merge authorization is implied.
• No historical internship commits are replayed.
• No new mutable image references are introduced.

Inherited upstream reference note

The exact upstream snapshot includes:

.github/workflows/integration-test.yml

which contains:

docker pull jacksonarthurclark/aiopslab-kind-x86:latest

This reference is inherited from upstream, not authored by this PR. Any fork-specific supply-chain hardening around that reference should be proposed separately and must not be silently changed as part of this alignment.

Validation

• Cleanup branch verified equal to microsoft/AIOpsLab:main at:

  b9a814e75a98e670787dac7c2ed6794b4b68dae2

• Legacy .github/workflows/main.yml absent

• REVIEW.md absent

Review requested

Please review whether maintaining vitrixLab/AIOpsLab on this upstream-aligned baseline is the appropriate foundation for future repository-specific engineering work.

[vitrixLab]

Fork-local internship contribution — provenance-preserving implementation path

This comment records the intended contribution boundary for the historical internship work without reopening or replaying the closed historical integration PR.

Contribution provenance

The internship work is technically distinct but relevant to the current fork and includes:

• AI Safety Engineering research: Issue AttributeError when LiteLLM encounters API errors microsoft/AIOpsLab#98 → AI Safe Engineering Research - Check Point FY2026 microsoft/AIOpsLab#130, including LiteLLM exception-handling research framed around reproducibility, traceability, provenance, exception safety, and agent reliability.
• SC-MVP engineering: Issues Add a CI Pipeline microsoft/AIOpsLab#19, Sanity Check Integration Map microsoft/AIOpsLab#131 and historical PRs Create BASIC INFRA REQS.md microsoft/AIOpsLab#132/Create HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md microsoft/AIOpsLab#133, covering cluster readiness, application deployment, structured checkpoints/evidence, failure handling, and audit/provenance.
• Historical integration proposal: PR Integrate AIOpsLab Internship Infrastructure and SC-MVP Documentation #3 remains CLOSED / HISTORICAL and is provenance only; its commits/branch should not be replayed or reused as the active implementation history.

Current fork boundary

PR #4 is the clean upstream-aligned baseline. The active fork should preserve the upstream Python/Kubernetes architecture rather than introducing the historical Node→Python rewrite or silently changing upstream behavior.

The appropriate next step is therefore a new fork-local Draft PR, based on main, with a dedicated provenance/documentation layer and a bounded implementation of the useful SC-MVP concepts.

Proposed implementation layer

SC-MVP-01  cluster readiness
SC-MVP-02  application deployment
SC-MVP-03  structured evidence/logging
SC-MVP-04  failure/recovery handling
SC-MVP-05  audit/provenance

Local validation target:

kind/k3d
  ↓
AIOpsLab application
  ↓
Hotel Reservation problem
  ↓
sanity checkpoint
  ↓
structured result
  ↓
failure evidence / logs

Required evidence should include clean-state verification, reproducible cluster creation, readiness/rollout checks, successful and failure-path results, cleanup, credential/secret exclusion, and confirmation that no upstream repository is mutated.

Documentation boundary

A future fork-local PR should preserve the distinction between:

historical source
fork-local artifact
upstream artifact
current implementation

Suggested tree:

docs/internship/
├── README.md
├── ai-safe-engineering/
│   ├── ISSUE-98-LITELLM.md
│   └── ISSUE-130-AI-SAFE-ENGINEERING.md
├── aiopslab-scmvp/
│   ├── ISSUE-19.md
│   ├── ISSUE-131.md
│   ├── PR-132.md
│   ├── PR-133.md
│   └── IMPLEMENTATION-PROCEEDINGS.md
└── provenance/
    └── CONTRIBUTION-LEDGER.md

Governance

PR #3       CLOSED / HISTORICAL
PR #4       MERGED / UPSTREAM-ALIGNED BASELINE
NEXT PR     DRAFT / FORK-LOCAL IMPLEMENTATION

microsoft/AIOpsLab
NO MUTATION
NO PR
NO MERGE REQUEST

This preserves the internship provenance and contribution record while allowing the engineering work to become real, reproducible, and testable inside vitrixLab/AIOpsLab only, without attributing the historical work to Microsoft or implying that the historical PR was merged upstream.

No implementation, push, merge, or upstream mutation is authorized by this comment; it documents the proposed contribution boundary and proceedings.

[vitrixLab]

CERTIFIED SHA-256 / MERGED HISTORICAL PROVENANCE — PR #1

For completeness of the contribution/provenance record, the fork contains an earlier merged contribution that should remain explicitly attributable to the fork rather than represented as a direct Microsoft upstream contribution.

• Repository: vitrixLab/AIOpsLab
• Upstream lineage: fork of microsoft/AIOpsLab
• Historical PR: #1
• Status: MERGED
• Merge commit SHA-256 identifier: 8ca4cbb9f61dc09b21d064beee0aca190ea876e9
• GitHub commit verification: Verified
• Merge date: 2025-01-23
• Change recorded by PR Update c-ares download URL in Dockerfile for proper installation #1: update to the c-ares download source in TargetMicroservices/socialNetwork/Dockerfile
• Merge parents: b7ecfde7209d6c57393edffe20e63546c0aeabdc and 7b9ea6123f9218aebe85c8d25274f55fde7fb63f

Provenance qualification

This is a certified historical merged commit in vitrixLab/AIOpsLab, preserving the fork's contribution history and its relationship to the Microsoft AIOpsLab lineage.

It is not being represented as a commit merged directly into the official microsoft/AIOpsLab repository.

The full commit SHA is recorded to support reproducibility, integrity verification, and contribution attribution.

This historical record is complementary to the contribution/provenance record above covering:

• AI Safety Engineering AttributeError when LiteLLM encounters API errors microsoft/AIOpsLab#98 → AI Safe Engineering Research - Check Point FY2026 microsoft/AIOpsLab#130
• SC-MVP Add a CI Pipeline microsoft/AIOpsLab#19 / Sanity Check Integration Map microsoft/AIOpsLab#131 / Create BASIC INFRA REQS.md microsoft/AIOpsLab#132 / Create HOTEL RESERVATION APP MICROSERVICE ARCHITECTURE.md microsoft/AIOpsLab#133
• historical PR Integrate AIOpsLab Internship Infrastructure and SC-MVP Documentation #3 (closed; not replayed)
• PR chore: align AIOpsLab fork with upstream baseline #4 as the upstream-aligned baseline
• the fork-local Draft PR as the proper implementation path
• SC-MVP-01 through SC-MVP-05
• Hotel Reservation local validation pipeline
• evidence, security, and provenance requirements

Security / authorization boundary

This comment records provenance only.

• No mutation of microsoft/AIOpsLab
• No implementation authorization
• No push authorization
• No merge authorization
• No claim that fork history constitutes Microsoft upstream authorship or acceptance

Source: vitrixLab/AIOpsLab PR #1