← NightshiftCONTENT HISTORY

Update to Nightshift

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.25.3

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Read-only shift status: items, parked decisions, snags, deadline, STOP or stall state.",
  "included_files": [],
  "name": "status",
  "skill_md_contents": "---\nname: status\ndescription: Read-only shift status: items, parked decisions, snags, deadline, STOP or stall state.\nlicense: MIT\n---\n\nReport the shift status for the host-opened project **without starting or changing anything** —\nthis is read-only. Modify no file, begin no work.\n\nResolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}`\non Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was\nattached from (`skills/status/SKILL.md`). Run every command below through\n`\"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns\"` — native Windows: `& \"$NIGHTSHIFT_PLUGIN_ROOT\\runtime\\windows\\ns.ps1\"`\nin the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the\nverbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,\n`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working\ndirectory persists between calls. Each `$NS/...` path below is where the current layout keeps that file;\n`ns path <key>` prints where this workspace keeps it, and `ns path --list` names every key.\n\n## 1. Run the two read-only inspectors\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns\" status\n\"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns\" doctor\n```\n\n`ns status` prints every fact: workspace, schema, armed or not, item counts and the current open\nitem, parked entries, staged drafts and Hunt orders, recent snag dispositions, opportunity counts\nand any building entry, deadline remaining, `STOP`, stall attempts, session, lease, watch reason,\nwork mode and target, artifact receipts, the completion record, and recent transitions. `ns doctor` adds the checks Status\ncannot make safely on its own — process liveness, the lease lines, and every Warning about a path\nthat is not a usable file.\n\n## 2. Render, never re-derive\n\nEvery number and every name above is already computed. Do not count boxes, subtract a deadline from\nthe clock, read a marker, or work out what a state means: the fact lines carry their own meaning\nwhere there is one to carry.\n\nDo not reimplement liveness, do not read the runtime-owned lease file directly, and never re-derive\npolicy precedence. The inspectors validate through the shared library, classify the recorded pid\nand the watchman pid themselves, and never print a session id, a session scope, or an ownership\ncapability.\n\nWrite a compact, glanceable summary in plain language. Lead with what matters tonight — that is\nyour judgement, and the only judgement this skill asks for. What the facts say is not.\n\n**Relay every Warning either inspector prints.** Each one is a real finding: a planted symlink\nwhere a marker should be is not an empty night, a malformed work mode is not a working site, and a\nfailed clock-out is not a finished shift. Say what it means for the owner and name the confirm\naction the inspector offers. Never soften a warning into silence.\n\nDo not print a project tool's raw output, credentials, raw evidence, a session id, or a transcript\npath. The inspectors do not emit them; do not go looking.\n\nThe project inventory is a separate optional report the owner asks for by name:\n`\"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns\" inventory`. Status never prints it unasked — a table of\npackages is not a glance.\n"
}

SHA-256 of public snapshot: b61288bf7a81e8b61b86f33e48b9345b1ed3edd6eb314edd292596297bd46edb