Recover workflow mirror work from ward-salvage/ward-33ebc07c #667

New issue

Closed

opened 2026-07-08 08:45:20 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-08 08:45:20 +00:00

Member

Goal

Recover the useful workflow-mirror work from ward-salvage/ward-33ebc07c onto current main.

Context

The salvage audit in #666 classified this branch as recover. The branch appears tied to ward#214 and contains recoverable work around mirroring the GitHub test workflow onto Forgejo plus adding a workflow drift checker.

Branch-only content includes:

.forgejo/workflows/test.yml
.github/workflows/test.yml updates
.pre-commit-config.yaml and .ward/ward.yaml updates
docs/workflow-mirror.md
scripts/check_workflow_mirror.py
scripts/check_workflow_mirror_test.go

The audit warns the branch is stale and should not be cherry-picked blindly. Recover the intent against current origin/main.

Do

Fetch ward-salvage/ward-33ebc07c.
Inspect the implementation and compare it to current workflow/release conventions.
Rebuild the workflow mirror and drift-checker work on current main.
Keep only the pieces that still make sense.
Run ward validation.
Land a commit that closes this issue and cross-references #666 / ward#214 as appropriate.

Filed from the read-only director surface (she/her).

## Goal Recover the useful workflow-mirror work from `ward-salvage/ward-33ebc07c` onto current `main`. ## Context The salvage audit in #666 classified this branch as `recover`. The branch appears tied to ward#214 and contains recoverable work around mirroring the GitHub test workflow onto Forgejo plus adding a workflow drift checker. Branch-only content includes: * `.forgejo/workflows/test.yml` * `.github/workflows/test.yml` updates * `.pre-commit-config.yaml` and `.ward/ward.yaml` updates * `docs/workflow-mirror.md` * `scripts/check_workflow_mirror.py` * `scripts/check_workflow_mirror_test.go` The audit warns the branch is stale and should not be cherry-picked blindly. Recover the intent against current `origin/main`. ## Do * Fetch `ward-salvage/ward-33ebc07c`. * Inspect the implementation and compare it to current workflow/release conventions. * Rebuild the workflow mirror and drift-checker work on current `main`. * Keep only the pieces that still make sense. * Run ward validation. * Land a commit that closes this issue and cross-references #666 / ward#214 as appropriate. Filed from the read-only director surface (she/her).

coilyco-ops added the

headless

labels

2026-07-08 08:45:20 +00:00

coilyco-ops commented

2026-07-08 08:45:42 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-667 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T08:45:40Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#667 · branch issue-667 · harness codex · workflow direct-main
Run: engineer-codex-ward-667 · ward v0.443.0 · dispatched 2026-07-08T08:45:40Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Issue body as seeded:

## Goal

Recover the useful workflow-mirror work from `ward-salvage/ward-33ebc07c` onto current `main`.

## Context

The salvage audit in #666 classified this branch as `recover`. The branch appears tied to ward#214 and contains recoverable work around mirroring the GitHub test workflow onto Forgejo plus adding a workflow drift checker.

Branch-only content includes:

* `.forgejo/workflows/test.yml`
* `.github/workflows/test.yml` updates
* `.pre-commit-config.yaml` and `.ward/ward.yaml` updates
* `docs/workflow-mirror.md`
* `scripts/check_workflow_mirror.py`
* `scripts/check_workflow_mirror_test.go`

The audit warns the branch is stale and should not be cherry-picked blindly. Recover the intent against current `origin/main`.

## Do

* Fetch `ward-salvage/ward-33ebc07c`.
* Inspect the implementation and compare it to current workflow/release conventions.
* Rebuild the workflow mirror and drift-checker work on current `main`.
* Keep only the pieces that still make sense.
* Run ward validation.
* Land a commit that closes this issue and cross-references #666 / ward#214 as appropriate.

Filed from the read-only director surface (she/her).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.443.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-667` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T08:45:40Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#667` · branch `issue-667` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-ward-667` · ward `v0.443.0` · dispatched `2026-07-08T08:45:40Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). **Issue body as seeded:** ``` ## Goal Recover the useful workflow-mirror work from `ward-salvage/ward-33ebc07c` onto current `main`. ## Context The salvage audit in #666 classified this branch as `recover`. The branch appears tied to ward#214 and contains recoverable work around mirroring the GitHub test workflow onto Forgejo plus adding a workflow drift checker. Branch-only content includes: * `.forgejo/workflows/test.yml` * `.github/workflows/test.yml` updates * `.pre-commit-config.yaml` and `.ward/ward.yaml` updates * `docs/workflow-mirror.md` * `scripts/check_workflow_mirror.py` * `scripts/check_workflow_mirror_test.go` The audit warns the branch is stale and should not be cherry-picked blindly. Recover the intent against current `origin/main`. ## Do * Fetch `ward-salvage/ward-33ebc07c`. * Inspect the implementation and compare it to current workflow/release conventions. * Rebuild the workflow mirror and drift-checker work on current `main`. * Keep only the pieces that still make sense. * Run ward validation. * Land a commit that closes this issue and cross-references #666 / ward#214 as appropriate. Filed from the read-only director surface (she/her). ``` Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.443.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-08 08:52:35 +00:00

feat(ci): recover workflow mirror

coilyco-ops referenced this issue from a commit

2026-07-08 08:52:35 +00:00

chore: close workflow mirror issue

coilyco-ops closed this issue

2026-07-08 08:52:35 +00:00

coilyco-ops commented

2026-07-08 08:52:55 +00:00

Author

Member

WARD-OUTCOME: done - recovered the mirrored test workflow and drift checker on current main.
The workflow side was straightforward once I trimmed the salvage snapshot to the current release shape. The review gate only reached advisory because opencode is unavailable here, so the panel could not get a second family. Confidence is high.
PR-BODY-NOTE: ADVISORY-ONLY REVIEW: no heterogeneous reviewer family was available besides the worker (codex), so the adversarial panel could not run and did NOT gate this diff. Dropped: opencode (unavailable: opencode not on PATH); codex (worker's own family - never reviews its own diff). A human should review this change with the extra scrutiny an unrun panel would have applied.

WARD-OUTCOME: done - recovered the mirrored test workflow and drift checker on current main. The workflow side was straightforward once I trimmed the salvage snapshot to the current release shape. The review gate only reached advisory because opencode is unavailable here, so the panel could not get a second family. Confidence is high. PR-BODY-NOTE: ADVISORY-ONLY REVIEW: no heterogeneous reviewer family was available besides the worker (codex), so the adversarial panel could not run and did NOT gate this diff. Dropped: opencode (unavailable: opencode not on PATH); codex (worker's own family - never reviews its own diff). A human should review this change with the extra scrutiny an unrun panel would have applied.