You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(planning): call the interview's record the Brief, not the contract #13185
The planning chain calls the interview's record the Brief, never "the contract": the interview checklist's "Persist the contract" step, gotchas' "Brief contract" heading, loop.md's "before the contract is persisted", and the exporter and surface-check comments say Brief. The workflow's first stage reads Interview in its list, its prose and context/steps.md.
The Brief (Problem, Goal, Constraints) is in the epic body.
Decisions
Q5-Q12: contract for the Brief retired (now Brief); the workflow stage reads Interview.
D8: versioned docs/contracts and design-stage interface contracts stay.
Done when
AC3 for this sense: the Demo command exits 0.
plugins/session-flow/skills/workflow/SKILL.md and its context/steps.md name stage 1 Interview in list and prose.
Eval samples that quote the renamed checklist line (planning's interview-*no-plan-edit / no-plan-write samples) match the new text; planning's evals validate with no FAIL; no model evals are run.
Each touched plugin's release record follows AGENTS.md.
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: #13178
Understood: a vocabulary rename across the planning, session-flow and work-items plugins. The interview's record becomes "the Brief" instead of "the contract". The workflow's first stage reads "Interview". Eval samples that quote the renamed checklist line get updated, and release records are added. The Demo command and done-when items are exact, and versioned docs/contracts and interface contracts are explicitly out of scope. I found no duplicates among the open issues. It depends on #13178 being done first.
The work-resolve-issue lane stopped on this issue (outcome-unread): the run wrote no readable outcome file: it crashed or was cut off, which says nothing about the issue.
It keeps agent-ready, and work-unblock starts it again (retry 1 of 2).
In the run's words:
The run wrote no readable outcome file, so it stopped before it finished.
Partial work is on the branch work-resolve-issue/issue-13185-41848358712-1. The next run continues from it while it is not behind the default branch, and otherwise starts fresh.
This run started fresh from the default branch instead of resuming work-resolve-issue/issue-13185-41848358712-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.
Activity
github-actions commentedon Nov 4, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: #13178
Understood: a vocabulary rename across the planning, session-flow and work-items plugins. The interview's record becomes "the Brief" instead of "the contract". The workflow's first stage reads "Interview". Eval samples that quote the renamed checklist line get updated, and release records are added. The Demo command and done-when items are exact, and versioned docs/contracts and interface contracts are explicitly out of scope. I found no duplicates among the open issues. It depends on #13178 being done first.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 4, 2026
Not admitted to the issue lane yet: blocker #13178 is not closed by a listed human or a merge.
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue lane stopped on this issue (
outcome-unread): the run wrote no readable outcome file: it crashed or was cut off, which says nothing about the issue.It keeps
agent-ready, and work-unblock starts it again (retry 1 of 2).In the run's words:
Partial work is on the branch
work-resolve-issue/issue-13185-41848358712-1. The next run continues from it while it is not behind the default branch, and otherwise starts fresh.Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41848358712
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
This run started fresh from the default branch instead of resuming
work-resolve-issue/issue-13185-41848358712-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.