orwa-mahmoud/nightshift/status

Report the shift status for the host-opened project without starting or changing anything — this is read-only. Modify no file, begin no work.

Resolve the installed plugin root to an absolute $NIGHTSHIFT_PLUGIN_ROOT — ${CLAUDE_PLUGIN_ROOT} on Claude Code, $PLUGIN_ROOT on Codex when set, otherwise the absolute path this skill was attached from (skills/status/SKILL.md). Run every command below through "$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" — native Windows: & "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\ns.ps1" in the PowerShell tool, same verbs — which resolves the host and the workspace; ns help lists the verbs, and ns bind prints the six resolved facts (TASK_ROOT, NIGHTSHIFT_WORKSPACE, NS, NIGHTSHIFT_PLUGIN_ROOT, HOST, SOURCE); $NS below is that NS. Never a bare relative path: the working directory persists between calls. Each $NS/... path below is where the current layout keeps that file; ns path <key> prints where this workspace keeps it, and ns path --list names every key.

1. Run the two read-only inspectors

"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" status
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" doctor

ns status prints every fact: workspace, schema, armed or not, item counts and the current open item, parked entries, staged drafts and Hunt orders, recent snag dispositions, opportunity counts and any building entry, deadline remaining, STOP, stall attempts, session, lease, watch reason, work mode and target, artifact receipts, the completion record, and recent transitions. ns doctor adds the checks Status cannot make safely on its own — process liveness, the lease lines, and every Warning about a path that is not a usable file.

2. Render, never re-derive

Every number and every name above is already computed. Do not count boxes, subtract a deadline from the clock, read a marker, or work out what a state means: the fact lines carry their own meaning where there is one to carry.

Do not reimplement liveness, do not read the runtime-owned lease file directly, and never re-derive policy precedence. The inspectors validate through the shared library, classify the recorded pid and the watchman pid themselves, and never print a session id, a session scope, or an ownership capability.

Write a compact, glanceable summary in plain language. Lead with what matters tonight — that is your judgement, and the only judgement this skill asks for. What the facts say is not.

Relay every Warning either inspector prints. Each one is a real finding: a planted symlink where a marker should be is not an empty night, a malformed work mode is not a working site, and a failed clock-out is not a finished shift. Say what it means for the owner and name the confirm action the inspector offers. Never soften a warning into silence.

Do not print a project tool's raw output, credentials, raw evidence, a session id, or a transcript path. The inspectors do not emit them; do not go looking.

The project inventory is a separate optional report the owner asks for by name: "$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" inventory. Status never prints it unasked — a table of packages is not a glance.