[SamErde]

Closes #107.

Summary

 README.md
+  Features: "Easy to navigate": highlight under the pointer or focus, pinned extension names
~  Requirements: VS Code Stable or Insiders 1.101 or newer
 docs/project-memory/history.md
+  ## 2026-10: Cleanup, packaging, and v1.1.0 → v1.2.0
 docs/local-build-test-and-release.md
+  Manual scenarios 15–17: highlight (incl. high contrast), workspace hand-off, pinned name column

Evidence

• Release history:
  • v1.1.0 = feat: require VS Code 1.101; fix workspace-local manifests on Node 22 hosts #82.
  • v1.1.1 = fix: shared CLI runner with timeout and injected platform #84.
  • v1.1.2 = refactor: consolidate path handling into one module #86–fix: surface swallowed IO errors, remove dead code, merge duplicated helpers #88.
  • v1.1.3 = refactor: align naming with the glossary #90–fix(release): publish with the locked vsce and keep sourcemaps out of the VSIX #93.
  • v1.2.0 = feat(matrix): highlight the row and column under the pointer or focus #100, feat(matrix): hand off workspace enable/disable to the Extensions view #103, fix(matrix): outline crosshair labels in high-contrast themes #104 and feat(matrix): keep the extension-name column visible when scrolling sideways #106.
  • docs: fix stale docs, add glossary and ADRs, align toolchain #80, chore: move spike probes out of test/ and scripts/ #96 and ci(release): skip install scripts in the Marketplace publish job #97 are docs, chore and ci commits, which don't produce a release.
• VSIX sizes come from the GitHub release assets: v1.1.2 is 121,099 bytes and v1.1.3 is 55,425 bytes.
• Test counts come from npm test on main (215 passed, 2 skipped, 12 files) and the 2 it(...) cases in test/integration/suite/inventory.test.ts.
• Minimum VS Code version comes from engines.vscode: ^1.101.0 in package.json.
• git diff --check is clean.

Merge Danger

Door: two-way. Docs only.

Blast Radius: none

A docs: commit doesn't trigger a release-please release.

🤖 Generated with Claude Code

[SamErde]

@codex review

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 36 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 4e9f3967-d689-468e-9115-faccc30f774b

📥 Commits

Reviewing files that changed from the base of the PR and between 319f2f8 and 3f2c99a.

📒 Files selected for processing: 3

• README.md
• docs/local-build-test-and-release.md
• docs/project-memory/history.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-23T14:41:25.386727Z	3f2c99a	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. Breezy!

Reviewed commit: 3f2c99ab8f

ℹ️ 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".