setup

Set up Nightshift in this project. Do the scaffolding first, then the gates conversation, then print a summary.

State map: punch-list.md → owner-approved work active in this shift; drafting-table.md → known work staged for a later shift; parking-lot.md → unresolved owner decisions plus the default chosen so work continues; work-orders.md → timed catalog work composed only through Hunt. Ordinary plans belong in the drafting table, never in Hunt or the parking lot.

Resolve the host-opened project folder to an absolute $TASK_ROOT: use ${CLAUDE_PROJECT_DIR} on Claude Code; on Codex honor Nightshift's ${CODEX_PROJECT_DIR} recovery override when present, otherwise capture pwd -P before any other shell call. If $TASK_ROOT/.nightshift-link exists, validate the one absolute workspace path inside it and call that $NIGHTSHIFT_WORKSPACE; otherwise set NIGHTSHIFT_WORKSPACE="$TASK_ROOT".

Bind the Nightshift directory once: NS="$NIGHTSHIFT_WORKSPACE/.nightshift". On native Windows, $NS = Join-Path $NIGHTSHIFT_WORKSPACE '.nightshift'. After this bind, Nightshift files are $NS/<name> for every read, write, and shell command. Catalog and owner-facing prose may use the short names (punch-list.md, parking-lot.md, STOP). Never re-resolve. Helpers that take --project or -Project still receive "$NIGHTSHIFT_WORKSPACE". Never search surrounding folders or guess. On Claude Code, .claude/ settings stay at $TASK_ROOT. The shell's working directory persists between Bash calls, so never rely on a bare relative path.

Resolve the installed plugin root to an absolute $NIGHTSHIFT_PLUGIN_ROOT: use ${CLAUDE_PLUGIN_ROOT} on Claude Code; on Codex use $PLUGIN_ROOT when available, otherwise derive it from the absolute path attached to this skill (skills/setup/SKILL.md). Substitute that absolute path in every command below; never search for the plugin.

On native Windows, use the PowerShell tool and native paths throughout: the host variables are $env:CLAUDE_PROJECT_DIR, $env:CODEX_PROJECT_DIR, and $env:PLUGIN_ROOT, with [Environment]::CurrentDirectory as the Codex cwd fallback. Do not route setup through WSL or Git Bash. Once the workspace and work target are resolved, the bundled mechanical scaffold is:

& "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\setup.ps1" `
 -Project "$NIGHTSHIFT_WORKSPACE" -WorkTarget "$WORK_TARGET" -Mode "$WORK_MODE"

It copies only absent files, writes state version 1 for a new site, persists the work target and work mode (-Mode repository or -Mode artifact), and keeps $NS/ private. It refuses a notes folder under default repository mode: pass -Mode artifact for a notes folder that is not a Git repository. The skill still owns every owner choice below; the script asks nothing and never invents gates, permissions, profiles, migration approval, or a receipts choice.

If the user explicitly identifies a different existing workspace containing .nightshift/, show both absolute paths and ask for confirmation. On yes, run "$NIGHTSHIFT_PLUGIN_ROOT/runtime/link-workspace.sh" --host-root "$TASK_ROOT" --workspace "$PROPOSED_WORKSPACE". On native Windows, run & "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\link-workspace.ps1" -HostRoot "$TASK_ROOT" -Workspace "$PROPOSED_WORKSPACE" instead. The pointer is local-only and state remains in the authoritative workspace; never copy it.

0. Reject disposable ChatGPT scratch workspaces

Before creating or changing any file, resolve the project root to an absolute path. If it is under /workspace/scratch/, this is a disposable ChatGPT scratch workspace that cannot affect the user's repository. Stop immediately: create no $NS/ directory, rules, settings, receipts repo, or other files. Tell the user directly:

Nightshift needs a persistent software project workspace. This ChatGPT conversation is using a temporary workspace, so files created here will not affect your repository.

Open your project in Codex (a Git repository or a persistent local folder), or start Codex connected to its GitHub repository. Then mention Nightshift and say: “Set up Nightshift in this project.”