Skip to content

fix(amicode): land #84 on mainline (locked vault context) — stacked-merge miss - #86

Merged
kateebonner merged 1 commit into
local/amicodefrom
kate/context-tree-locked-affordance
Jul 29, 2026
Merged

fix(amicode): land #84 on mainline (locked vault context) — stacked-merge miss#86
kateebonner merged 1 commit into
local/amicodefrom
kate/context-tree-locked-affordance

Conversation

@kateebonner

Copy link
Copy Markdown
Contributor

#84 merged into its stacked base kate/context-tree-drop-prompt-text after #83 had already landed that branch on mainline — so the locked-affordance commit (9b1caf6) never reached local/amicode. This PR re-lands it; the diff is exactly #84's content (see #84 for full description and verification).

TL;DR of what lands: GET /amicode/vaults stamps per-mount browsable; context-tree nodes in non-browsable (proprietary) vaults render dimmed + padlocked, not-allowed cursor, click no-op, a11y announce; pointer cursor only on genuinely openable nodes.

🤖 Generated with Claude Code

Not every tree node was openable, but nothing said so: turn nodes wore a
pointer cursor that clicked into nothing, and files in non-browsable
(proprietary) vaults dead-ended in a Vault-panel refusal after the click.

- GET /amicode/vaults now stamps each mount with `browsable`, computed by
  the vault-browser's fail-closed law (deployment gate + kind/marker rules)
- tree leaves in a non-browsable mount render locked: dimmed dot, padlock
  glyph by the label, not-allowed cursor, click is a no-op, and keyboard
  nav announces "locked — this vault does not allow browsing"
- cursor law is now honest everywhere: pointer only where a click opens
  something; grab (pan) on turns/skills/agents/actions; the click ring
  only fires on openable nodes

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jack-champagne
jack-champagne force-pushed the kate/context-tree-locked-affordance branch from 9b1caf6 to e642558 Compare July 28, 2026 22:52
@kateebonner
kateebonner merged commit 9a8268d into local/amicode Jul 29, 2026
2 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant