fix(org-workbench), test(browser-drive): drive-proven relations + tags; hover-only actions now keyboard-reachable

The Playwright drive (#54) walked the full round-trip on the live shell —
relate → Part of renders → click-through navigation → Contains on the
reverse side → tag chip add/remove → relation remove with confirm — with
throwaway drive-proof-* orgs, accessibility snapshots, zero console
errors, and zero DB residue after cleanup.

Its one finding is fixed here: RelatedOrgs' hover-revealed ✎/× used
visibility:hidden, which also removed the buttons from keyboard focus and
the a11y tree (the drive's click couldn't reach them). Now opacity-based
with :focus-within so Tab reveals them.

svelte-check clean after the fix.

Refs #54.

Files changed:
- apps/org-workbench/src/RelatedOrgs.svelte
- changelog/2026-07-27_01_Organizations-Learn-Their-Family-Tree-Parent-Child-Peer-Relations-Plus-Org-Tags.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RW28dw3kQAKXr2ZNefCukE

Author: mpstaton

apps/org-workbench/src/RelatedOrgs.svelte

@@ -261,7 +261,9 @@
   .ro-kind { font-size: 0.72rem; padding: 0.05rem 0.4rem; border: 1px solid var(--color-border, #2a2c33); border-radius: 999px; opacity: 0.8; white-space: nowrap; }
   .ro-desc { font-size: 0.78rem; opacity: 0.6; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; flex: 1; min-width: 0; }
   .ro-actions { margin-left: auto; display: inline-flex; gap: 0.25rem; }
-  .ro-row:not(:hover) .ro-actions { visibility: hidden; }
+  /* opacity, not visibility — the buttons stay focusable/clickable for
+     keyboard users and assistive tech; :focus-within reveals them on Tab */
+  .ro-row:not(:hover):not(:focus-within) .ro-actions { opacity: 0; }
   .ro-add { display: flex; flex-direction: column; gap: 0.25rem; }
   .ro-picked, .ro-edit-name { font-size: 0.85rem; font-weight: 600; white-space: nowrap; }
 </style>

changelog/2026-07-27_01_Organizations-Learn-Their-Family-Tree-Parent-Child-Peer-Relations-Plus-Org-Tags.md

@@ -145,3 +145,21 @@ deliberately share one vocabulary). Tag removal rides its own verb rather
 than `resolver.update_org`, because tags are per-client observations, not
 fields on the shared org row. The row renders even when empty so the
 affordance is discoverable — an untagged org shows the ➕, not nothing.
+
+### The agent drove it before asking a human to (#54)
+
+Playwright drive against the live shell (`localhost:3100`, Augment-from-DB
+flow), throwaway `drive-proof-*` orgs only, accessibility snapshots
+throughout, deleted to zero residue after: relate via the ➕ form →
+**Part of** renders with kind badge + description → row click navigates
+the workbench to the parent → reverse projection shows **Contains** →
+tag add renders the chip → ✕-confirm removes it (empty row keeps its ➕)
+→ relation ✕-confirm removes the edge. Zero console errors across the
+whole drive.
+
+One finding, fixed live: the hover-revealed ✎/× used `visibility: hidden`,
+which also removed them from keyboard focus and the accessibility tree —
+the drive's click literally couldn't reach them. Now opacity-based with
+`:focus-within`, so Tab reveals them too. The drive proving the buttons
+*work* is exactly the rung that caught the button you couldn't Tab to;
+the human walk-through still judges whether the surface is *usable*.