Status-bar state changes now land in the shell log with their reason, and
identical re-reports skip both the log line and the tooltip rebuild. The fmt
stack logs each request the way prettier-vscode does (entry and outcome at
info with duration, resolution detail at debug), forwards the CLI's stderr
tail on successful runs, and explains once per folder why a request in an
undetected folder did nothing.

The extension-host debugger inherits the developer's own profile, so a
personal language-scoped defaultFormatter silently outranks the fixture's
folder settings; with extensions disabled that formatter is unavailable and
format-on-save does nothing. Launch the playground with an isolated,
auto-created profile instead (the debugger strips --user-data-dir, so
--profile is the supported mechanism), and give the rstack fixture
format-on-save through the extension under development.

VS Code's CI-only extension inventory and AgentHost info logs drowned the
test output; --log=warn keeps them out while VSCODE_TEST_LOG_LEVEL preserves
an opt-in for verbose diagnosis.

The watch matcher's endsPattern matched the per-target "built in" line, and
the worker bundle finishes seconds before the extension bundle — the first
F5 launched against a half-written dist/ and the extension failed to load.
Match the once-per-build "build completed" line instead.

A config or lockfile change can reshape the set of fmt-detected folders
while reconciliation deliberately keeps the controller alive, leaving the
status hover and shell log with stale folder names until the next
successful format. Report from the detection listener instead; an empty
snapshot stays silent because the shell's retire path owns the off states.

Mocha's reporter writes to the extension host's stdout, which never reaches
the harness log — CI showed only the failure count. The rejection message is
the one channel that does surface, so it now carries each failed test's
title and assertion message.

Detection can change while a format request is in flight; the success path
reported from the request's captured snapshot and reverted the hover and
shell log to the pre-change folder list.

The Windows runners check fixtures out with CRLF (autocrlf), and VS Code
drops EOL-only changes from computeMoreMinimalEdits, so the formatted
document keeps \r\n and the fmt E2E's exact-output assertion fails. Byte-
identical fixtures make the assertion hold everywhere without loosening it.

- Install 15 skills into .agents/skills/ as the single source of truth,
  with .claude/skills/ symlinks so both Claude Code and Codex read them
- Record the install in skills-lock.json
- Configure the issue tracker (GitHub Issues via gh) and single-context
  domain doc layout under docs/agents/, referenced from AGENTS.md
- Ignore the per-developer .claude/settings.local.json