304 — tp story define becomes tp story accept (#304)

Why

The act the command records is a human's: they read the offered story and accept it. tp overview already calls it that, on the button that does the same thing against the forge, and so do the messages tp prints ("accept the story on #N … or with tp story define there"). The command alone is named for the state it leaves behind, so one act has two names and the reader has to learn that they are the same.

What changes

  • tp story accept: the new name of tp story define. What it checks, writes and prints is unchanged, apart from the name in its own errors.
  • tp story define: removed. It is an unknown story subcommand, as any other name is.
  • Messages that name the command (tp story land refusing a story not defined, tp story query's next step, the usage text and the command list): they name tp story accept.
  • CLAUDE.md, docs/story.md, docs/idea.md, docs/overview.md: the command is named tp story accept.

Acceptance

Command Issue Outcome
tp story accept, on a story branch at code level 3, acceptance filled labelled story defined added; #N defined
tp story accept, the same labelled defined already #N is already defined; nothing changed
tp story accept, refused for any reason define was (level, branch, blank cell, not a story) any the same error, beginning tp story accept:
tp story define any the unknown-subcommand error and the usage; nothing written
tp story land, the story not defined not labelled defined the error names tp story accept
tp story query, the story not defined not labelled defined stands not defined; the human's next step names tp story accept
"accept" on tp overview labelled story as today
Searched Outcome
the usage text, tp -a, CLAUDE.md, docs/story.md, docs/idea.md, docs/overview.md no tp story define

Out of scope

  • The label defined, and the words that follow from it: the state "not defined", the board's "Not yet defined" column and its anchor, tp story call -undefined. The label is on issues already and is what every reader of the flow tests; renaming it is a migration of the forge, not of a command. Accepting a story is the act, defined the state it leaves.
  • An alias or a deprecation message for define.
  • Mentions in CHANGELOG.md, earlier stories and ADRs, which record what was.

Decisions

None.

Done when

  • tests express the acceptance table and pass
  • spec updated
  • changelog entry
  • issue closed with a link to the release