moldea 8.2.8

Skill 8.2.8 closes gaps an external review found in 8.2.7: repair Git evidence in partial clones and on older Git, Claude Code integration checks, and CLI setup in Yarn workspaces and when the CLI was declared as a regular dependency. It retains CLI 11.0.6, Node.js >=22.17.0, Git >=2.30.0, every numeric limit and the existing continuation behavior.

Changes

• The repair Git helper never fetches. Every helper Git read disables lazy fetching and allows no transport protocol, so an object missing from a partial clone becomes unavailable evidence and repair reassesses every completed owner instead of contacting the remote.
• The file monitor is disabled on every supported Git. The helper's override is now core.fsmonitor= (empty). Git 2.35 and earlier treated the previous false value as the name of a program to run.
• Claude Code integration is checked. When a repository has a root CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md, Claude Code does not load AGENTS.md by default unless one of those files imports it or is a symbolic link to it. Initialization, setup checks and repair now check this. Imports resolve relative to the file that contains them, so a root file uses @AGENTS.md and .claude/CLAUDE.md uses @../AGENTS.md. A shared file must carry the integration, because CLAUDE.local.md covers only its owner. The coding agent adds the line only when host instructions permit editing that file, never writes through a link, and otherwise reports the exact line and file.
• Yarn Classic workspace roots. Yarn Classic 1.x installs and removes with -W, which a workspace root requires and other projects accept.
• Moving a CLI declared as a regular dependency. With every manager, a CLI declared outside root devDependencies is first removed with the manager's targeted removal and then added as an exact root development dependency, both with scripts disabled. Adding alone left the declaration in dependencies with Yarn Classic and was refused by Yarn 4.

Verification

• The repair Git helper's integration tests run on Linux, Windows and macOS and, in a new required conformance job, on Debian Bullseye's Git 2.30. In a blobless partial clone, continuation reports unavailable evidence and leaves Git storage unchanged, while a plain Git read of the same object does fetch. A stored file-monitor index extension never runs a false program from PATH. Debian's Git 2.30 package backports GIT_NO_LAZY_FETCH, so each no-fetch setting was also shown to block the fetch on its own.
• The package-manager harness now installs Yarn at a real workspace root and moves a CLI declared in dependencies for every manager, preserving an unrelated dependency's declaration and lock entries. Before this release it passed locally against the published CLI 11.0.6 closure on every release-candidate entry (npm 7 through 12, pnpm 8.3.1 through 12.3.1 including Vitest 3.2.4 coexistence, Yarn 1.22.22, 4.14.1 and 4.18.0) and Yarn 3.8.7, and a Yarn Classic workspace run without -W failed as expected.
• Evaluator protocol 50 adds the setup-check-claude-instructions scenario for the .claude/CLAUDE.md variant and tightens the ordinary final-validation exemption so an unreadable patch never earns it. Neither has been recorded.

Pinned semantic evidence

The semantic evidence was recorded on Skill 8.2.3 with CLI 11.0.6. None of the 8.2.8 changes was re-evaluated. Whether a coding agent checks Claude Code's files or chooses the correct import or package-manager command is not established by that evidence, and deterministic checks do not establish the new rules' behavioral reliability.

The selected bundle remains semantic-sem-20261018051032668-1465f9ee.json.gz under evidence-8.2.3-20261018: 120 cases, 115 passed and five recovered, with the same two disclosed exclusions. Its compressed SHA-256 is baa883450e1087efafbf3c685e311859fb63575dfa839761c20db48de292342d. No paid run, regrading or evidence repacking was performed for 8.2.8.

Install this exact release:

npx skills add "moldea-ai/skill#v8.2.8"