Standardize structured workflow comment markers #1522
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
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/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1522
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-698"
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?
The current inventory used
WARDED_WORKFLOW:as the emitted workflow header, with olderWARD-OUTCOME, reservation, dispatch, QA, status, reap, and triage headers still accepted by parsers. This PR makes the literalWARD-WORKFLOW:header canonical without disturbing historical threads.WARD-WORKFLOW:for workflow, reservation, broker, review/QA outcome, reaper, and PR-handoff comments.WARDED_WORKFLOW:and typed legacyWARD-*headers parse-compatible; document the vocabulary and update the generated Forgejo surface text.ward exec testpassed. Thebuild-ward-kdlregeneration attempt is blocked by its configured external spec host (git.example.com) being unavailable; the tracked generated asset mirrors the source edit.closes #698
ward.workflow: pull-request-and-merge