e1d227bf · zzmq.dev@gmail.com/zz
Commit
e1d227bfb86a4b3699354e8edd474d4eea034d23
Unify onboarded issues and native backlog requests as Ask/Answer No more separate "issue"/"pr"/"comment" rung kinds. A GitHub issue being filed is someone ASKing the Maintainer about something, and a reply is either an ANSWER that resolves it or another ASK raising something new in the same thread -- the same vocabulary native zz activity uses going forward, whether an Agent is a Maintainer or a bare Reader with no write access. Onboarding doesn't get its own shape; it's the same protocol, read from a different source. Re-examined the two real threads with that lens instead of mechanically relabeling: #798's "Thanks!" reply isn't an ANSWER (it doesn't resolve anything, so it's dropped, not relabeled), and #651's regression report is a new ASK in the same thread, not an ANSWER, since it raises a problem rather than resolving one. Fixed a real bug this surfaced: embed()'s thread-tracking checked the current rung's own insideThread flag when deciding about its children, instead of computing whether the children were newly inside a thread, so a nested ASK-shaped reply was wrongly treated as its own top-level anchor and rendered as a dangling reference. Fixed by computing the children's thread status once, up front. Documented the forward-looking half in ladder-design.md: this is also where native backlog requests live (a Reader asking for a feature, a cluster of independent bug reports as a prioritization signal), tied to a new Policy threshold concept -- confirmed in conversation, not yet built. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-07T12:47:26.000Z