[alecthomas]

What changed and why

Two problems with the document type icons in the workspace list:

• The tooltip never showed. plan_type_icon already sets title to the type name. But in _plan_row, the title link's ::after stretches over the whole card, and it sat on top of the icon. Hovering the icon hovered the overlay instead. The icon is now its own link to the same plan. That lifts it above the overlay, through the existing .plan-row a:not(.plan-row__title) rule. Clicking the icon still opens the plan. The link is out of the tab order, since the title link is already the keyboard target. Its accessible name includes the plan title and type.
• "Research" was red. Tints come from Zlib.crc32(name) % 6, and "Research" hashes to tint 4, #e0637a. A red icon reads as an error. Tint 4 is now olive green, #8a9c2a. I avoided orange because docs/DESIGN.md reserves it for attention states.

Other places that show the icon (header, feed, search) have no stretched link, so their tooltips already worked.

Evidence

The author could not run the app locally. Maintainer preparation now includes an isolated Ruby 3.4/MySQL preview, with light and dark screenshots below. Hover targeting, icon clicks, and Tab/Enter title navigation were exercised in both modes.

How to try it

1. Sign in as hampton@example.com (no password), then open /hampton/demo-content/rich-text. The demo index remains at /hampton/demo-library.
2. Hover a row's type icon. The type name should show as a tooltip.
3. Click the icon. The plan should open.
4. A "Research" document should have an olive icon, not red.
5. Use Appearance to switch modes. Tab should skip the duplicate icon link; Enter on the title opens the document.

Maintainer local preview: http://localhost:3328/hampton/demo-content/rich-text (available on Hampton’s machine).

Testing

• Added a request spec: the row's icon is a link to the plan, out of the tab order, with the type name as its title.

• Added a system spec: the icon is the topmost element at its centre, and clicking it opens the plan.

• The author could not run specs locally. Maintainer preparation passed all 164 examples in spec/requests/plans_spec.rb and spec/system/folders_workspace_spec.rb, including the added keyboard regression, plus focused RuboCop. The full local suite also passed: 3,573 examples, zero failures.

• Added or updated real JavaScript-enabled browser specs in spec/system/.

• Added request specs.

• Ran bundle exec rspec — 3,573 examples, zero failures on the isolated MySQL test database.

• Tested in light and dark mode — isolated Chrome for Testing, shared demo library.

• Attached images — light and dark local previews below.

🤖 Generated with Claude Code

Product acceptance remains with Hampton.

Maintainer preparation generated with Codex.

[HamptonMakes]

🤖 @codex review

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-13T10:20:12.386123Z	691652f	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 691652fe2a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[HamptonMakes]

🤖 Prepared for Hampton’s product review. Hampton requested local review, routine repairs, an isolated tryout, and light/dark evidence; this is engineering preparation, not product acceptance.

• Pushed bdc86f55: icon links now announce the plan title and type, with a regression covering Tab/Shift+Tab and Enter. Alec’s overlay fix and olive tint are preserved.
• Local validation: 3,573 examples, zero failures in the full suite; all 164 focused request/browser examples and focused RuboCop passed.
• All 15 CI checks pass on bdc86f553eeb8be1282b53cde3b04fc3bdc2a1e9. GitHub reports MERGEABLE / REVIEW_REQUIRED; there are no merge conflicts.
• Codex found no issues on 691652fe. The subsequent label/test correction is bounded and was reviewed locally; no new automated round was needed under the maintenance guidance.
• Exercised icon hover targeting, icon clicks, and title Tab/Enter navigation in isolated Chrome for Testing, in both modes. Screenshots: light, dark.

Local tryout on Hampton’s machine: http://localhost:3328/hampton/demo-content/rich-text. Sign in as hampton@example.com, no password; return to that folder after login. Hover an olive Research icon, click it, and compare Appearance → Light/Dark. Tab skips the duplicate icon link; Enter on its title opens the same document. The preview remains running. Approval and merge remain with Hampton.