v0.7.0

A fifth check, from the audit's F3: the agent's configuration, read as data rather than as prose. A setting that points at nothing fails in silence, since the rule never applies, the skill never loads and the server never starts, and no message says so. The three older checks did not change.

AGENT CONFIG. Four shapes, all from structured sources. A rule in .cursor/rules/*.mdc, or an instruction in .github/instructions/*.md, none of whose globs: or applyTo: patterns matches a file git tracks, unless alwaysApply: true makes the patterns moot; a dead pattern beside a live one is left alone, since the rule attaches when any of them matches, and a bare extension such as .cpp is read as **/*.cpp. A SKILL.md under a skills/ folder whose front matter has no description, and one under .claude/skills/ or .agents/skills/ with no front matter at all; outside those two folders only a front matter that carries a name is read as a skill's, since a SKILL.md elsewhere may follow another schema, and a skill's name is not held against its folder, because hosts differ on whether the two must agree. An MCP server in .mcp.json, .cursor/mcp.json or .vscode/mcp.json whose command or args name a script that is not here, and a hook in .claude/settings.json that does the same, with $CLAUDE_PROJECT_DIR read as the repository root. The JSON files are read only when the context files were auto-detected, and only when git tracks them; naming a target checks that target alone.

Held back like another project. A rules folder where most rules match nothing here, at least four and six in ten, is a catalogue written for the projects it gets copied into; its rule findings are held back and the ANOTHER PROJECT section names the folder with the count, 14 of 16 rules.

Formats. The JSON gains configIssues, each with kind (glob, skill-description, config-path), cited and message, and stats.configs, the JSON configuration files read; an elsewhere entry gains unit, rules for a rules folder; schemaVersion is 4. SARIF gains the agent-config rule, the GitHub format a warning per issue, and the MCP server's tool description names the check.

Also fixed on the way. A file that opens with a byte order mark is read without it, so its front matter and its JSON parse. A **/ in a glob now stops at a folder boundary, so **/c/** no longer matches src/app.tsx; this also tightens the globs in .prumorc.json.

Measurement. The check was run on the eight public corpora at once, 443 repositories, since the three older checks did not change and every corpus was fresh to it. Six decisions were taken on that material, so the number is fitted: after them 689 findings remain, 666 in one repository whose skills have no front matter and 23 outside it, every one a SKILL.md under a host's skills folder with no front matter at all, in seven repositories. No rule was reported dead outside the folder held back, and no server or hook named a missing script in the 64 repositories that configure one, so for those two shapes the unit tests and the simulation are the only evidence. The design page has the table and the six decisions.

Tests and the shell. The two tests that read the CLI through a pipe, and the simulation, now start without the FORCE_COLOR, NO_COLOR and PRUMO_BANNER a shell may carry, since a shell with FORCE_COLOR set painted the piped output and failed them on 2026-09-05.

Suite 135 to 137, simulation 108 to 110.