status

never-stale — status of this project

A read-only health check for the current project. It writes nothing — it inspects and reports. Use it to answer "is never-stale on here, and what would the gate do?"

Project root = the path in $ARGUMENTS if given, else the current working directory. Call it <ROOT>.

Step 1 — Resolve the governing marker (the gate's own walk)

Walk up from <ROOT> to the nearest ancestor that carries a marker, bounded by the git repo root:

1. At each directory D, check D/.claude/never-stale.local.json then D/.claude/never-stale.json.
2. If either exists, that directory governs — stop. (local overrides team at the same directory — but a local file that fails to PARSE is ignored in favour of the team one, so a typo'd local marker never silently disables a team opt-in.)
3. Otherwise, if D/.git exists, stop (repo root — no governing marker).
4. Else go to the parent and repeat.

Record the governing directory <GOV>, which marker is effective (local vs team), and whether the launch dir is the marker's own directory or a descendant (the upward walk).

Step 2 — Inspect the artifacts

Read the installed plugin version from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json (version); call it <PV>. Use it for the drift checks below. If you cannot resolve ${CLAUDE_PLUGIN_ROOT}, skip the version-drift line rather than guessing.

• Marker — read the effective marker. Report: scope (team/local), enabled (true / false / invalid if the JSON is corrupt — the gate treats corrupt as disabled, except that a corrupt local marker falls back to the team marker beside it), recorded spoken / written (with spokenCode / writtenCode if present), per-event flags (events.compact, events.edit; absent = on), version, createdAt. If both a team and a local marker exist at <GOV>, note that the local one wins when it parses and show both.
  • Version drift — if version !== <PV>, note it: "marker written by <version>, plugin is <PV>." Make clear this is cosmetic — the gate ignores the version — and that /never-stale:update reconciles it.
  • Language codes — if spokenCode / writtenCode are missing, or the display string is non-canonical (not one of English / Traditional Chinese / Traditional Chinese (Hong Kong) / Simplified Chinese, nor a deliberate "Other"), note it and point at /never-stale:update to normalize. Also informational only.
  • Drift pairs (syncPairs) — if the marker declares syncPairs, show a resolution preview for each pair so a misconfiguration is visible rather than silent (the gate ignores a pair it cannot resolve). For each { source, snapshot, mode }:
    • resolve both paths relative to <GOV>; flag any that is unsafe (absolute / drive-qualified / UNC / parent-escaping .., or resolving through a symlink/junction to outside the repo) or missing on disk — the gate silently skips those;
    • for mode: "mtime" (the default), read both files' mtimes and state the verdict: drift (source newer than snapshot → "snapshot may be behind, verify") or clean (snapshot at least as new);
    • for mode: "hash" (v0.10.0+), read the snapshot's synced-to marker (<!-- never-stale:synced-to <hex> -->) and the source's current normalized hash, then state the verdict: drift (the marker is not a prefix of the current source hash → "snapshot recorded <declared>, source is now <current>; reconcile and update the marker"), clean (they match), or unknown (no synced-to marker in the snapshot, or the source is missing / larger than the 512 KB cap — the gate skips these silently, so surfacing them here is the whole point);
    • for mode of declared / version, note it is deferred — not planned (a reserved value the gate treats as a silent no-op).