fix(vscode): show an unconfigured Rstack lint config as not detected

[fi3ework]

Summary

Before	After

Follow-up to #94. A bridged lint runtime whose root rstack.config.* has no define.lint() reported running with a detail. In the status bar hover that is a green check beside Rslint, with the reason visible only in the icon's native tooltip, so a formatting-only project looked like Rslint was linting it. The status bar's existing word for "this tool has no configuration here" is not-detected, so the unconfigured verdict now maps to it, and the reason is shown as a notice row under the hover table.

 StackState
-  | { kind: 'not-detected' }
+  | { kind: 'not-detected'; detail?: string }   # set only by a runtime-level "nothing configured" verdict
 status bar
-  not-detected: spellsOutDetail: false
+  not-detected: spellsOutDetail: true           # notice row only when a detail exists
 Rslint (bridged, shim refuses: no define.lint())
-  running — no define.lint() in rstack.config.ts
+  not-detected — no define.lint() in rstack.config.ts
   ok after define.lint() appears → running (same worker, no restart)

What the user sees for a formatting-only project: hover Rstack in the status bar → the Rslint row shows the grey circle-slash icon, and one notice row reads no define.lint() in rstack.config.ts. The item text stays $(zap) Rstack, the per-stack restart action is still offered, there is still no toast, no crashed, no dependency poll, and one info line in the Output channel. Every other hover is unchanged: detection's own not-detected carries no detail and therefore adds no notice row.

Fold rules, written as comments in stacks/lint/status.ts:

• A folder whose only runtimes are unconfigured folds to not-detected with its detail (not masked into running: idle).
• A healthy native runtime beside an unconfigured bridged one wins (running): the folder is linting. The same rank applies across folders in multi-root.

The worker stays alive underneath not-detected, which is the reverse of how running: idle decouples state from process. packages/vscode/AGENTS.md adaptation 7 and the lint-shim gotcha are updated accordingly.

Evidence

• pnpm lint ✓ · pnpm fmt:check ✓ · pnpm test:unit 370 passed, 0 failed.
• Lint E2E on macOS with VSCODE_CLI=1: Rstack fmt-only config, Missing config dependency, Rstack lint bridge, JS config tests all Exit code: 0. The fmt-only suite now waits for kind === 'not-detected' with a define.lint() detail on both the folder and the runtime state, then adds define.lint() and asserts plain running plus the no-debugger diagnostic from the same worker pid.
• Negative check: with the suite's predicate reverted to the old running shape it fails with Timed out waiting for the unconfigured not-detected detail, so the assertion is live.
• Manual check with the packaged VSIX in a clean profile on a define.fmt()-only project (rstack 0.8.2): hover shows the Rslint row with the circle-slash icon and the notice no define.lint() in rstack.config.ts; the Output channel logs Rslint status: not detected — no define.lint() in rstack.config.ts.

Merge Danger

Door: two-way

Revert restores the running + detail shape from #94. No settings, protocol versions or published surfaces change; the not-detected detail is editor-internal state.

Blast Radius: status bar + lint-bridged

StackState['not-detected'] gains an optional field, read only by the status bar's notice rendering and lint's fold helpers. Only bridged lint runtimes whose shim refuses produce it; fmt, Rstest and native Rslint runtimes never set it.

Related Links

• Follow-up to fix(vscode): keep Rslint healthy when rstack.config has no define.lint() #94 (Rslint starts and fails for a formatting-only Rstack config #93).

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[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-10T06:23:50.751975Z	898d945	PR opened

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