315 — tp overview: the answer page's five niggles (#315)
Why
The review of #311 passed every row and left five notes on the answer
page of tp overview. None is serious alone; the first loses the
human's typing. They are small, they are in one place, and they are
cheaper fixed together than carried as five ideas.
What changes
tp overview, the press of "answer": when nothing was written
because the forge could not be reached, the typed answer is kept.
tp overview, the press of "answer": a press that joins an agent
still starting gets the same page as the press that started it, when
the start fails.
tp overview, a blocked card: the "answer" link shows only when the
board can answer.
tp overview, the answer page: a link to the issue or the story is
made only from an http or https address.
tp overview, the answer page: a call's date is in this machine's
zone, and says which.
docs/overview.md, "Answering": the table gains the unreachable
forge; the date's zone is said.
Acceptance
Terms are those of story 311.
Every row of its tables not named here stands.
The press, nothing written
| The box |
The forge |
Written |
The browser |
| text |
not reached, or failing, when the issue, its labels or its branches are read at the press; reached again for the page |
nothing |
the answer page again, what went wrong above the box, the text still in it |
| text |
as above, and the page cannot be read either |
nothing |
a page saying what went wrong, with the text in a box and "answer" to press again; a link back |
| text |
reached; the issue not called, closed or not story |
nothing |
as story 311: a page saying why, a link back; no box |
The press, joining an agent still starting
| The first press |
The second, within the minute |
The second's page |
| its agent prints its address |
waits for it |
as story 311: the answer is recorded, the running agent has not been told, a link to its session |
| its agent ends, or prints no address and is stopped |
waits for it |
the same as the first's: the answer is recorded; the last line it printed; the worktree's path; a link back |
The card
| Card |
The board |
Has |
| blocked |
can answer, as tp overview always serves it |
the "answer" link |
| blocked |
served with a button, but without the means to read a call or to answer |
no "answer" link |
Links from the forge
| The address the forge gives for the issue, or the story |
On the answer page |
http:// or https:// |
linked, as story 311 |
| anything else, or none |
the same words, not a link |
Dates
A Called: comment's time from the forge |
Shown |
| in any zone |
the date and time in this machine's zone, followed by the zone's name |
Out of scope
- Keeping the text when the forge refuses the label: the comment is
then written, and story 311's page says what to do.
- The links on the board's cards, which take the forge's addresses
the same way; only forges of the user config are read.
- Dates anywhere but the answer page.
- Telling a running agent of the answer, and the rest of story 311's
out of scope.
Decisions
None.
Done when