v0.4.1: npm registry refresh + post-launch audit fixes

🔧 v0.4.1 — npm registry refresh + post-launch fixes

v0.4.0 published the new stetkeep brand to npm, but the tarball baked in the previous MDBRAIN ASCII header (npm pins READMEs at publish time). This patch republishes with the correct header and a batch of genuine bug fixes and platform-parity items uncovered in a 4-person post-launch audit.

🐛 Bug fixes

• bin/stetkeep.js: bare stetkeep invocation now exits 0 (was 1). GNU / npm convention; matches stetkeep --help.
• lib/install.js: bootstrap detection regex matches mdbrain and claude-brain legacy references. v0.3.0 users upgrading no longer get a duplicate bootstrap appended to CLAUDE.md.

🪟 Platform parity (Windows PowerShell)

• hooks/safety-net.ps1: ported Bash redirect (>) and tee bypass checks from .sh. Previously cat > legacy/foo.ts would bypass the Safety Net on PowerShell-only setups.
• hooks/safety-net.ps1: $Input automatic-variable conflict renamed to $Stdin to prevent pipeline-enumerator shadowing.

🎯 Marker detection (false-positive fix)

The @craft-* / @perf-* hook detection now requires a reason= / baseline= / date= field alongside the marker token.

• Why: Before this fix, simply mentioning @perf-optimized in docs (for example "honor @perf-optimized markers") caused the Safety Net to block edits to that file.
• After: Only real markers like // @perf-optimized reason="profiled: 62% CPU" block edits. Bare mentions in prose pass through.
• This is the actual format documented in CRAFT.md and PERF.md, so no user change required.

💬 UX improvements

• Slash commands: /brain-scan, /craft-audit, /perf-audit now declare argument-hint frontmatter for the slash-command picker UI.
• /brain-scan: body now actually substitutes $ARGUMENTS into the scan scope (was documented in trailing note but silently dropped in the prompt body).
• brain-router subagent: description now leads with "Use PROACTIVELY for ambiguous or compound code-quality requests" for reliable auto-delegation.
• craft-specialist subagent: description replaces vague "make this artistic" trigger with concrete keywords (refactor, cleanup, anti-pattern removal, readability, dead-code removal).

🧹 Metadata consistency

• package.json and plugin.json descriptions unified (minor drift before).
• package.json files includes CONTRIBUTING.md so the README "PRs Welcome" badge resolves on the npm page.

📝 Docs

• README: STETKEEP ANSI Shadow header (was still MDBRAIN in v0.4.0 tarball), version badge v0.4.0 → v0.4.1, "Why the name stetkeep?" FAQ added, footer updated with rename date.
• CHANGELOG v0.4.0 in-tarball metadata refreshed: removes the stet proxy package mention (the proxy attempt was blocked by npm's typosquatting policy; the stet CLI shorthand still works as a bin alias inside stetkeep).

🔄 Migration

No user action required.

npm install -g stetkeep  # upgrades 0.4.0 → 0.4.1 automatically

CLI behavior is unchanged except for the bare-invocation exit code (1 → 0), which should only affect CI scripts that intentionally used stetkeep as a fail check. Use stetkeep --help || true or stetkeep --version for that pattern instead.