Skip to content

M7: Plan and publish Matt tickets in their own Session from the published spec #295

Description

@Sandstorm831

Parent

Spec #276; implementation sub-issue of M7 #275.

What to build

A new built-in version of the Matt Bundle keeps grill and write-spec in the spec Session and moves plan-tickets and publish-tickets to a new tickets Session that opens fresh on first use. plan-tickets already reads the spec through spec-ref; its "use everything we discussed in this same conversation" line is removed. The manifest description describes the two conversations. The manifest version is bumped and the built-in lock digest updated in the same change (ADR 0029 as amended by ADR 0030), so the new version installs beside 2.6.0 through the ordinary startup ensure and resting Runs stay pinned. There is no source edit and no branch on Bundle identity. This supersedes M6 spec story 9's shared planning Session. Agent-declared completion (#253) is out of scope (stories 103–110).

Acceptance criteria

  • A Projection Port test proves the Turn Sessions are spec, spec, then tickets, tickets, with spec-ref reaching plan-tickets.
  • The built-in lock test and Bundle build tests cover the new version; package smoke proves it is embedded, locked, and installed on first start beside 2.6.0, and that a second start is a no-op.
  • No src/ edit.
  • Human step: a maintainer re-records the Claude Code Matt-front fixture with a real Claude Code so replay evidence matches the new Sessions (real Harnesses do not run in CI).
  • CI scenario: the Port test, Bundle tests, and package smoke are green on Windows x64, macOS arm64, and Linux x64.

Blocked by

Implementation packet

Owner: the Matt Bundle (manifest, prompts), the built-in lock, the recorded Claude Code Matt-front fixture

Ratchet: Port test for the spec/tickets Session split; package smoke for the new built-in version

Deletes: the shared planning Session for ticket stages and the prompt line telling the agent to use the earlier conversation

Gate: ADR 0027 three-OS CI and recorded human evidence, with the slice scenario above.

Dependencies: no new runtime dependency

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions