chore(ward): drop dead ward.yaml keys #818
No reviewers
Labels
No labels
burndown-2026-06
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure!818
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/mg96"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of the coilysiren/inbox#365 teardown. Provably-dead keys only, no behavior change.
Removed
catalog.kind/type/system/owner/lifecycle- the retired Backstage vocab.agentic_os/pre_commit/check_catalog_block.pyexplicitly ignores them and the catalog-graph builder no longer reads them. agentic-os already dropped them, infrastructure was the straggler.ssh:- traced to zero consumers. The only otherworking_dirhits in the repo are an unrelated Windows Terminal convergence test. Ward's own schema doc (ward/docs/ward-yaml.md) says unknown fields consumed by neither Ward nor cli-guard have no effect and should be removed, so this is the doc's own instruction.Kept for now
catalog.descriptionandagent.workflow- ruled in inbox#365 but their moves need other work first.catalog.dependsOn- ruled delete, but it is live and ward-consumed. Retirement is tracked at coilyco-flight-deck/ward#1660.Verified
ward doctorpasses. All 85 commands still parse.