interactive: remove the stale-main race from PR AOS CLI tests #913

New issue

Closed

opened 2026-08-05 21:53:27 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-05 21:53:27 +00:00

Member

Evidence

PR #911 at commit 103c4e85e3a62f6a2a367aa8c4cf1e750b79a9f2 triggered Forgejo run #2866.
aos-cli-tests failed in the Test the AOS CLI step with: ward: refusing repo verb "repo.aos-test" - 1 commits behind origin/main.
ward-doctor and the required gate job passed. Local ward exec repo-test-gate passed with 537 tests.
The PR branch was based on 3aae3082, then origin/main advanced to 942d58e6 before the runner invoked Ward. The release patch does not touch the AOS CLI test path.

Operator verification

Inspect the checkout and pull-request merge attachment in run #2866.
Confirm the intended CI behavior when origin/main advances after a PR run starts.
Remediate the runner or workflow boundary so the synthetic PR revision satisfies Ward without weakening the synced-branch invariant.
Verify on a disposable PR or a single post-remediation rerun. The expected evidence is all three jobs green with Ward reporting a synced branch.

#911
#910

## Evidence - PR #911 at commit `103c4e85e3a62f6a2a367aa8c4cf1e750b79a9f2` triggered Forgejo run [#2866](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/2866). - `aos-cli-tests` failed in the `Test the AOS CLI` step with: `ward: refusing repo verb "repo.aos-test" - 1 commits behind origin/main`. - `ward-doctor` and the required `gate` job passed. Local `ward exec repo-test-gate` passed with 537 tests. - The PR branch was based on `3aae3082`, then `origin/main` advanced to `942d58e6` before the runner invoked Ward. The release patch does not touch the AOS CLI test path. ## Operator verification 1. Inspect the checkout and pull-request merge attachment in run #2866. 2. Confirm the intended CI behavior when `origin/main` advances after a PR run starts. 3. Remediate the runner or workflow boundary so the synthetic PR revision satisfies Ward without weakening the synced-branch invariant. 4. Verify on a disposable PR or a single post-remediation rerun. The expected evidence is all three jobs green with Ward reporting a synced branch. ## Related - #911 - #910

coilyco-ops added the

autonomy

live-collab

label

2026-08-05 21:53:27 +00:00

coilyco-ops commented

2026-08-05 22:43:29 +00:00

Author

Member

Ward-side fix landed on canonical main:

Ward issue: coilyco-flight-deck/ward#1649
Commit: coilyco-flight-deck/ward@5642fc6df8
Change: ward exec now admits a clean Forgejo Actions pull-request merge checkout when the runner temporarily names it, as AOS does with ward-ci, by validating the immutable CI evidence before applying the stale upstream branch gate.

Local Ward validation passed:

ward exec format
ward exec test-cmd -- -run TestRunExecGateIntegration
ward exec test
ward exec pre-commit
ward exec vet

Release status is the remaining live boundary. Ward promote run https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2579 failed for commit 5642fc6df8049c394d13bbbe4991026dd60e2dd0, so AOS CI will still install the previous Ward release until Ward release advances. From this session, direct job/log endpoints returned 404 and the AOS log bridge hit local Python certificate verification failure, so I could not retrieve the failing step body.

Operator evidence needed next: inspect Ward run 2579, resolve the promote failure, and confirm the Ward release branch/tag advances to a build containing 5642fc6d. After that, rerun or requeue the affected AOS PR CI and expect ward exec aos-test to pass through the validated Forgejo PR merge evidence instead of reporting commits behind origin/main.

Ward-side fix landed on canonical `main`: - Ward issue: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1649 - Commit: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/commit/5642fc6df8049c394d13bbbe4991026dd60e2dd0 - Change: `ward exec` now admits a clean Forgejo Actions pull-request merge checkout when the runner temporarily names it, as AOS does with `ward-ci`, by validating the immutable CI evidence before applying the stale upstream branch gate. Local Ward validation passed: - `ward exec format` - `ward exec test-cmd -- -run TestRunExecGateIntegration` - `ward exec test` - `ward exec pre-commit` - `ward exec vet` Release status is the remaining live boundary. Ward promote run https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2579 failed for commit `5642fc6df8049c394d13bbbe4991026dd60e2dd0`, so AOS CI will still install the previous Ward release until Ward `release` advances. From this session, direct job/log endpoints returned 404 and the AOS log bridge hit local Python certificate verification failure, so I could not retrieve the failing step body. Operator evidence needed next: inspect Ward run 2579, resolve the promote failure, and confirm the Ward `release` branch/tag advances to a build containing `5642fc6d`. After that, rerun or requeue the affected AOS PR CI and expect `ward exec aos-test` to pass through the validated Forgejo PR merge evidence instead of reporting `commits behind origin/main`.

coilysiren closed this issue

2026-08-05 22:47:13 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#913

No description provided.

Rows
Columns