Point the hub debt at the issue carrying the proposed wording - #18
Conversation
The intake thread holds the questions and their answers, and the change itself needs an issue that can be worked without reconstructing which framing stands. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the hub-tracking note in TODO.md so it points readers to the specific hub issue that contains the proposed spec wording, while keeping the intake/measured-answers thread referenced for context. This makes it clearer where to read or act next when addressing the publishing-type spec debt.
Changes:
- Reworded the “Owed to the hub” entry to reference ProjectTemplate#558 as the source of proposed spec wording.
- Added a new link reference for
hub-spec-issue(ProjectTemplate#558) alongside the existinghub-issuelink.
The reference sat beside a spelled-out one in the same sentence, so the bare form read as a local issue number. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The review loop was hand-rolled, which re-discovered two failures the hub script exists to prevent: findings suppressed into a review body reach no thread, and a request nothing picks up is indistinguishable from a slow reviewer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
TODO.md:102
- This bullet says “The two traps below…”, but there are now three consecutive “trap” bullets immediately below it (the new inert-review-request trap plus the two existing ones). This makes the note internally inconsistent and harder to follow.
- **The hub authors `scripts/pr_review.py`, and hand-rolling the review loop re-discovers its bugs.** One `status` call reports rounds, head coverage, unresolved threads, suppressed findings across every round, and whether a request was ever picked up. `wait` runs the backoff in-process, so a review wait costs one turn rather than one per poll. It is read-only by design and the mutations stay explicit, so fetch and run it rather than reimplementing it. The two traps below are both documented in its README as the reason it exists.
A count of the bullets that follow it is wrong as soon as one is added. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Fixed in 994fa64. Valid, and it was mine to cause: I wrote "The two traps below" and then added a third bullet in the same edit. Removed the count rather than correcting it, since a cross-reference that counts the bullets following it is wrong again the next time one is added. The sentence now names the README as the source without asserting how many follow. Raised as a suppressed comment, which reaches no thread. Worth noting this round was the first run through the hub's |
Why
The hub debt recorded in
TODO.mdpointed at the intake thread, which asks six questions and now also holds an answer plus a correction superseding its own framing. A reader has to reconstruct which parts stand before they can act.The change itself is now ProjectTemplate#558, carrying proposed wording for both additions: a deploy-to-host row in
Output Seam by Destination, and one D4 guarantee that a deploy is verified against the running host by release id rather than by transport success.TODO.mdnow points at both, and says which holds what.Note
No release dispatch accompanies this. Per the release model a release marks a functional change rather than mechanical churn, and this is a backlog pointer.
🤖 Generated with Claude Code