feat(portal): visible zero-proposals, durable triage, local link chips (27 S.3/S.4)#177
Closed
bryanmatthewsimonson wants to merge 1 commit into
Closed
Conversation
…s (27 S.3/S.4) Phase 27 slices S.3/S.4 — the "accepted a proposal, then what?" fixes. - synthesis-review: the Proposals heading always renders with its open count; a zero-proposal run says "0 proposals" instead of rendering nothing (absence disclosed, not implied). Accept/Dismiss now persist on the brief record (record.triage, keyed by the exported proposalKey — the filterProposals dedup identity, endpoint-order insensitive and pin-tested), so reopening the case no longer resurrects triaged rows: accepted rows render checked, dismissed rows fold into a collapsed Dismissed section that stays reachable (accepting from there clears the dismissal). Nothing auto-applies — unchanged. - case-view: claims now also show LOCAL relationship links (accepted proposals and hand-drawn links not yet published) as "(local)" chips beside the published-30055 chips, including a local ⚠ contradicted badge — closing the hole where accepting a link produced no visible change anywhere on the dashboard (T1.3 residue). Canonical-ref matching both sides; published links stay wire-chip territory. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 16, 2026
Owner
Author
|
Landed on main via the #183 consolidation merge (the stacked-merge cascade closed/retargeted intermediates; every commit from this PR is in main). |
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
1 participant
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.
Summary
Phase-27 slices S.3/S.4 — the visibility half of the corpus-proposals fix. Stacked on #176.
record.triage, keyed by the exportedproposalKey— endpoint-order-insensitive, pin-tested). Accepted rows render checked; dismissed rows fold into a collapsed, still-reachable section (accept from there clears the dismissal). The human-accept firewall is unchanged.(local)chips — including a local ⚠ contradicted badge. Previously an accepted link produced no visible change anywhere on the dashboard.Tests: 1,791 green (1 new) · build clean · lint 0 errors.
Next
The forensic F ladder (misattribution + baselines) follows on its own stack.
🤖 Generated with Claude Code