Repository navigation
Let the tool drawer put rows straight into the collection plan - #67
Merged
Merged
Conversation
F18. The realistic entry point is "this host runs Claude Desktop", and that led to a drawer, then Show all 32 artifacts, then the catalog, then 32 individual ticks. Nothing on that path picked anything, though the drawer already ranks the rows by volatility two sections above the button. Two buttons in the drawer footer: Add volatile (n) and Add all n. Both reuse picks and savePicks, so a row added here is indistinguishable from one ticked by hand, and neither introduces a second way into the plan. Called it volatile rather than p1, which is what the handoff proposed. triage_priority lives on the tool, not on the row, so there is no p1 subset of these rows to offer - a button labelled p1 would be naming a field the data does not carry at that level. Volatility is the field that answers "what do I lose if I reboot first", it is already on every row, and the drawer's own Order of collection section ranks by it, so the button matches the section above it. Add-only on purpose. A button that un-picked on a second press would silently lose work, and per-row removal already exists in the plan. Pressing again reports Already in plan and adds nothing. Verified in a browser rather than reasoned about. On AIRT-0011: buttons render Add volatile (8) and Add all 32; two clicks from a closed drawer leave 8 picks, matching the 8 live and rotating rows exactly, persisted to localStorage and showing as 8 rows in the plan view. Add all then tops up to 32 without duplicating and reports Added 24. A third press reports Already in plan and leaves the count at 32. On AIRT-0013, which has no volatile rows, the volatile button is correctly absent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
F18. The realistic entry point is "this host runs Claude Desktop". That led to a drawer →
Show all 32 artifacts→ the catalog → 32 individual ticks. Nothing on that path picked anything, though the drawer already ranks those rows by volatility two sections above the button.Two buttons in the drawer footer:
Add volatile (n)andAdd all n. Both reuse the existingpicks/savePicks, so a row added here is indistinguishable from one ticked by hand — no second path into the plan.Why "volatile", not "p1"
The handoff proposed
Add p1 paths.triage_prioritylives on the tool, not on the row, so there is no p1 subset of these rows to offer — a button labelled p1 would name a field the data doesn't carry at that level.Volatility is on every row, it answers "what do I lose if I reboot first", and the drawer's own Order of collection section already ranks by it. The button now matches the section above it.
Add-only on purpose
A button that un-picked on a second press would silently lose work, and per-row removal already exists in the plan. Pressing again reports
Already in planand adds nothing.Verified in a browser
On AIRT-0011:
Add volatile (8),Add all 32localStorageAdd allAdded 24Already in planOn AIRT-0013, which has no volatile rows, the volatile button is correctly absent.
Accept-when from the handoff: "a responder can go from Tools → a populated plan in two clicks." Met.
Gates
All pass.
🤖 Generated with Claude Code