feat(bitacora): auto-move assigned issues to In Progress + codify status lifecycle (HARNESS-010)#286
Merged
Conversation
…tus lifecycle Close the manual-transition gap (HARNESS-010): the bitácora Status lagged reality because nothing flipped it when work started — observed when #261 was implemented while still in Backlog. - bitacora-status.yml: on issues:[assigned], set Status=In Progress (idempotent item-add + item-edit, open-state guard, BITACORA_PAT). - AGENTS.md Standing Order #8 + Neural Hive Loop touchpoints: self-assign on pickup, Blocked on a hard blocker, Done on close. - guide-bitacora-setup.md §4/§5/§7: register the workflow in the per-repo deployment bundle (OPS-002 rollout); In Progress is now automated on assign. - specs/HARNESS-010-...: SDD spec (proposal, tasks, verification, features). The /handoff status-reconciliation step lands in the vault separately. Closes #270
This was referenced Jun 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The bitácora (Project #1) has a
Statusfield but nothing flipped it when work started — observed 2026-06-06 when #261 was actively implemented while still inBacklog. Built-ins coverBacklog(on add) andDone(on close); the start-of-work transition was pure manual discipline that, in practice, got skipped. A board whoseStatuslags reality is worthless as a real-time cross-repo picture.What
.github/workflows/bitacora-status.yml: onissues: [assigned], setStatus = In Progress. Self-assigning at pickup now flips the board automatically. Idempotent (item-addreturns the existing item), guarded to skip closed issues, authenticates withBITACORA_PAT(no default-token perms).AGENTS.mdStanding Order feat(tmux): focus-events, vi visual-mode bindings, slower status refresh #8 + Neural Hive Loop touchpoints (Phase 1 self-assign on pickup, Phase 2Blockedon a hard blocker, Phase 3Doneon close). The canonical cross-agent rule.docs/runbooks/guide-bitacora-setup.md§4/§5/§7: registers the workflow in the per-repo deployment bundle and marksIn Progressautomated-on-assign;Blockedstays a deliberate manual transition.specs/HARNESS-010-bitacora-status-lifecycle/(proposal/tasks/verification/features).The
/handoffboard-status reconciliation step (AC5) lands in the vault (00_meta/skills/handoff/SKILL.md) separately — it is not a dotfiles file.Scope
dotfiles; register it as the template.Blockedauto-detection (no reliable signal). A PR-linked trigger (a PR opens after work starts — late signal).Verification
actionlint→ exit 0; YAMLsafe_load→ OK;spec-gate→ OK (spec folder present).item-editmoved HARNESS-010: Codify bitácora status-lifecycle discipline (start→In Progress, close→Done, block→Blocked) #270 → In Progress;item-addidempotency confirmed (no duplicate). Liveassign → In Progressvia the deployed workflow is verifiable once this is onmain(workflows run from the default branch).Closes #270