coilyco-flight-deck/ward

Watch

Remove public verification-fixture mode #1645

New issue

Closed

opened 2026-08-05 10:08:47 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-08-05 10:08:47 +00:00

Member

Outcome

Remove --verification-fixture as a public Ward product surface. Normal synthetic or disposable repositories and ordinary governed workflows provide verification without a bespoke mode.

Scope

Delete the flag from director, engineer, and QA entrypoints and broker forwarding.
Delete its configuration, special label and admission behavior, workflow forcing, help, documentation, and mode-specific tests.
Replace test-verification-fixture and external fixture scripts with normal synthetic or disposable repositories using ordinary dispatch. Use remote-branch-only when a non-landing workflow is required.
Do not add a replacement product mode.

Preserved boundary

Direct dispatch, brokered QA, and ordinary fixed workflows remain.
Verification stays bounded to synthetic or disposable repositories. This issue grants no live-operations authority.

Acceptance

No verification-fixture flag, configuration, label, admission rule, or documentation remains.
Ordinary fixture tests prove the same critical boundaries without a special product mode.
Direct goal primitives from #1620 and brokered QA from #1255 remain usable.

Coordinates with #1620 and #1255. Blocks documentation consolidation in #1624.

## Outcome Remove `--verification-fixture` as a public Ward product surface. Normal synthetic or disposable repositories and ordinary governed workflows provide verification without a bespoke mode. ## Scope * Delete the flag from director, engineer, and QA entrypoints and broker forwarding. * Delete its configuration, special label and admission behavior, workflow forcing, help, documentation, and mode-specific tests. * Replace `test-verification-fixture` and external fixture scripts with normal synthetic or disposable repositories using ordinary dispatch. Use `remote-branch-only` when a non-landing workflow is required. * Do not add a replacement product mode. ## Preserved boundary * Direct dispatch, brokered QA, and ordinary fixed workflows remain. * Verification stays bounded to synthetic or disposable repositories. This issue grants no live-operations authority. ## Acceptance * No verification-fixture flag, configuration, label, admission rule, or documentation remains. * Ordinary fixture tests prove the same critical boundaries without a special product mode. * Direct goal primitives from #1620 and brokered QA from #1255 remain usable. Coordinates with #1620 and #1255. Blocks documentation consolidation in #1624.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-05 10:08:47 +00:00

coilyco-ops referenced this issue

2026-08-05 10:09:42 +00:00

Collapse the documentation tree into durable product contracts #1624

coilyco-ops referenced this issue

2026-08-05 10:09:50 +00:00

Retire autonomous burndown in favor of harness-native goal orchestration #1620

coilyco-ops commented

2026-08-05 10:51:04 +00:00

Author

Member

Decision resolved with Kai:

Hard-delete the public verification-fixture mode.
Delete verification_fixture.go, mode-specific tests, flag wiring, broker forwarding, Director cycle state, QA branch special cases, configuration fields, environment variables, container labels, admission rules, and workflow forcing.
Delete test-verification-fixture from .ward/ward.yaml without adding a replacement fixture verb.
Delete docs/verification-fixtures.md and every reference from help, generated flag docs, FEATURES, role docs, schema docs, and indexes.
Add no deprecated alias, migration path, custom legacy error, tombstone test, or replacement product mode.
Retain ordinary dispatch, exact-head QA, and remote-branch-only as normal product contracts. #1627 and #1628 own their focused synthetic tests.
Regenerate command documentation from the actual command tree. Prove removal through repository-wide absence checks rather than preserving the removed spelling in negative tests.
Priority is P2 because this blocks #1624.

Kai deleted coilyco-flight-deck/ward-qa-fixture on 2026-08-05. Cross-repository removal of its stale skill and inventory pointers is owned by coilysiren/inbox#332. Do not recreate the repository.

Decision resolved with Kai: * Hard-delete the public verification-fixture mode. * Delete `verification_fixture.go`, mode-specific tests, flag wiring, broker forwarding, Director cycle state, QA branch special cases, configuration fields, environment variables, container labels, admission rules, and workflow forcing. * Delete `test-verification-fixture` from `.ward/ward.yaml` without adding a replacement fixture verb. * Delete `docs/verification-fixtures.md` and every reference from help, generated flag docs, FEATURES, role docs, schema docs, and indexes. * Add no deprecated alias, migration path, custom legacy error, tombstone test, or replacement product mode. * Retain ordinary dispatch, exact-head QA, and `remote-branch-only` as normal product contracts. #1627 and #1628 own their focused synthetic tests. * Regenerate command documentation from the actual command tree. Prove removal through repository-wide absence checks rather than preserving the removed spelling in negative tests. * Priority is P2 because this blocks #1624. Kai deleted `coilyco-flight-deck/ward-qa-fixture` on 2026-08-05. Cross-repository removal of its stale skill and inventory pointers is owned by coilysiren/inbox#332. Do not recreate the repository.

coilyco-ops referenced this issue from a commit

2026-08-05 23:55:48 +00:00

refactor: remove public verification fixture

coilyco-ops closed this issue

2026-08-05 23:55:48 +00:00

coilyco-ops commented

2026-08-05 23:56:03 +00:00

Author

Member

Landed and closed on canonical main.

Ward: 4112b2a9 removes the public flag, config schema, admission and workflow forcing, broker forwarding, QA branch shortcut, container evidence, focused verb/tests, generated help, feature entry, and docs.
AOS: 1d22b96b removes the downstream live fixture script, Ward config, command, feature entry, and docs.
Ordinary remote-branch-only coverage and exact-head QA verdict coverage remain. A new ordinary QA plan test covers the read-only ephemeral checkout shape.
Ward validation passed: full tests, command tests, lint, vet, build, generated flags/roster, format, and full pre-commit.
AOS validation passed: ward doctor and full pre-commit.
The deleted repository’s separate skill and fleet-inventory cleanup remains owned by coilysiren/inbox#332. Ward did not recreate or inspect that repository.

Landed and closed on canonical main. * Ward: `4112b2a9` removes the public flag, config schema, admission and workflow forcing, broker forwarding, QA branch shortcut, container evidence, focused verb/tests, generated help, feature entry, and docs. * AOS: `1d22b96b` removes the downstream live fixture script, Ward config, command, feature entry, and docs. * Ordinary `remote-branch-only` coverage and exact-head QA verdict coverage remain. A new ordinary QA plan test covers the read-only ephemeral checkout shape. * Ward validation passed: full tests, command tests, lint, vet, build, generated flags/roster, format, and full pre-commit. * AOS validation passed: `ward doctor` and full pre-commit. * The deleted repository’s separate skill and fleet-inventory cleanup remains owned by coilysiren/inbox#332. Ward did not recreate or inspect that repository.

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/ward#1645

No description provided.

Rows
Columns