pdurlej/platform

Fork 0

docs(status): record RS2000 F3 closeout state #318

Merged

pdurlej merged 1 commit from codex/cutover/rs2000-closeout-status into main

2026-05-17 08:58:46 +02:00

codex commented

2026-05-17 08:53:01 +02:00

Collaborator

Canary status: missing - status-only closeout; rely on required Forgejo checks before merge.

Canary Context Pack

Product story

RS2000 migration has landed operationally, but the canonical operator status file still described the pre-F3 ramp. The next agent needs a 30-second readback that says F3 is complete and explains what still must not be touched.

What changed

Updated state/STATUS_NOW.md to record the post-F3 closeout state: current release-root, green final smoke evidence, clean #260 runner pickup soak, legacy path semantics, and remaining follow-ups.

Why it changed

The status file is the canonical operator-facing state per ADR-0006. Leaving it stale would cause future agents to re-open completed migration work or mistake /opt/vps-home-platform-infra cleanup for a safe immediate action.

Files touched

state/STATUS_NOW.md

Relevant context

Issue #142 final RS2000 migration checkpoints
Issue #260 runner pickup soak evidence
Issue #310 minio-init follow-up
ADR-0006 single operator status file

Runtime evidence

Release-root API/run evidence checked via Forgejo Actions API: latest platform-smoke.yml run has index_in_repo=1134, commit 2a2a66ffcdc097fd557e1a8f52899577c521e6f4, status success.
Existing #142 closeout checkpoint records final F3 wave and platform smoke evidence.

Known constraints

This PR does not mutate production.
/opt/vps-home-platform-infra must not be deleted or pruned from this closeout.
Infisical Token Auth soak still gates direct PAT fallback removal.

Explicit out-of-scope

Runtime cleanup of legacy paths.
DR restore drill.
Closing #310.
Removing direct PAT fallback before soak completion.

Requested decision

Merge the status closeout so the canonical repo state matches runtime reality.

Merge blockers

Any evidence that final F3/platform smoke did not actually complete.
Any evidence that the release-root hash differs from the recorded value.

Spec sources read

state/STATUS_NOW.md - target canonical status file.
Forgejo Actions API latest runs - verify current platform smoke/release-root evidence.
Existing issue #142/#260 context from this session - source of migration and runner-pickup closeout evidence.

Canary status: missing - status-only closeout; rely on required Forgejo checks before merge. ## Canary Context Pack ### Product story RS2000 migration has landed operationally, but the canonical operator status file still described the pre-F3 ramp. The next agent needs a 30-second readback that says F3 is complete and explains what still must not be touched. ### What changed Updated `state/STATUS_NOW.md` to record the post-F3 closeout state: current release-root, green final smoke evidence, clean #260 runner pickup soak, legacy path semantics, and remaining follow-ups. ### Why it changed The status file is the canonical operator-facing state per ADR-0006. Leaving it stale would cause future agents to re-open completed migration work or mistake `/opt/vps-home-platform-infra` cleanup for a safe immediate action. ### Files touched - `state/STATUS_NOW.md` ### Relevant context - Issue #142 final RS2000 migration checkpoints - Issue #260 runner pickup soak evidence - Issue #310 minio-init follow-up - ADR-0006 single operator status file ### Runtime evidence - Release-root API/run evidence checked via Forgejo Actions API: latest `platform-smoke.yml` run has `index_in_repo=1134`, commit `2a2a66ffcdc097fd557e1a8f52899577c521e6f4`, status `success`. - Existing #142 closeout checkpoint records final F3 wave and platform smoke evidence. ### Known constraints - This PR does not mutate production. - `/opt/vps-home-platform-infra` must not be deleted or pruned from this closeout. - Infisical Token Auth soak still gates direct PAT fallback removal. ### Explicit out-of-scope - Runtime cleanup of legacy paths. - DR restore drill. - Closing #310. - Removing direct PAT fallback before soak completion. ### Requested decision Merge the status closeout so the canonical repo state matches runtime reality. ### Merge blockers - Any evidence that final F3/platform smoke did not actually complete. - Any evidence that the release-root hash differs from the recorded value. ## Spec sources read - `state/STATUS_NOW.md` - target canonical status file. - Forgejo Actions API latest runs - verify current platform smoke/release-root evidence. - Existing issue #142/#260 context from this session - source of migration and runner-pickup closeout evidence.

codex added 1 commit

2026-05-17 08:53:01 +02:00

docs(status): record RS2000 F3 closeout state

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / collect-diff (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Has been skipped

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 20s

Details

739cfa6e22

codex referenced this pull request

2026-05-17 08:53:32 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this pull request

2026-05-17 08:53:32 +02:00

ops(forgejo): deploy-host runner intermittently fails to pick up waiting jobs #260

codex commented

2026-05-17 08:54:25 +02:00

Author

Collaborator

Merge note from codex:

All visible PR checks on commit 739cfa6 are green:

base-is-main / guard (pull_request)
canary-required / collect-diff (pull_request)
canary-required / canary (pull_request) skipped as expected
patchwarden-pr-sanity / collect-diff (pull_request)
patchwarden-pr-sanity / sanity (pull_request)

API merge attempt failed with Forgejo branch-protection status mismatch:

not allowed to merge [reason: Not all required status checks successful]

This appears to be the known required-context mismatch around base-is-main / guard versus base-is-main / guard (pull_request). Operator/admin UI merge is needed for this closeout PR.

Merge note from codex: All visible PR checks on commit `739cfa6` are green: - `base-is-main / guard (pull_request)` - `canary-required / collect-diff (pull_request)` - `canary-required / canary (pull_request)` skipped as expected - `patchwarden-pr-sanity / collect-diff (pull_request)` - `patchwarden-pr-sanity / sanity (pull_request)` API merge attempt failed with Forgejo branch-protection status mismatch: ```text not allowed to merge [reason: Not all required status checks successful] ``` This appears to be the known required-context mismatch around `base-is-main / guard` versus `base-is-main / guard (pull_request)`. Operator/admin UI merge is needed for this closeout PR.