@opengsd/gsd-path 1.3.1 → 1.5.0

package/HOOKS.md

@@ -42,7 +42,8 @@ node scripts/install.mjs --claude --project /path/to/repo --hooks
 ```
 
 For a project that already has `AGENTS.md` and `WORKFLOW.md`, initialize only
-the guards and keep those contracts unchanged:
+the guards and keep those contracts unchanged (use `--update --project` to
+refresh the `AGENTS.md` block):
 
 ```bash
 npx @opengsd/gsd-path --hooks-init --claude --project /path/to/repo
@@ -86,11 +87,13 @@ manual activation is complete, Codex's guaranteed manifest tier is `git-only`;
 changing the hook requires review again.
 
 **Windows / interpreter caveat:** hooks and native host settings invoke a
-Python interpreter that the installer probes at install time — `python3` first,
-then `python` (plain `python3` usually does not exist on Windows). If neither
-runs, hook installation stops before writing instead of pinning a missing
-interpreter. The `sh` hook scripts themselves need a POSIX shell (Git for
-Windows provides one).
+Python interpreter that the installer probes at install time: `python3` first,
+then `python`, then the `py -3` launcher (plain `python3` usually does not
+exist on Windows). If none runs, hook installation stops before writing
+instead of pinning a missing interpreter. The `sh` hook scripts themselves need
+a POSIX shell, which Git for Windows provides. Claude Code runs Windows hook
+commands in Git Bash, so wrapped Core hooks are bash-quoted and their original
+command runs through Git Bash, not cmd.exe.
 
 ### Updating after package upgrade
 
@@ -130,7 +133,8 @@ See [UPDATE.md](UPDATE.md).
   `git checkout -- .`/`git restore .`
 - shell writes (redirections, `tee`, `cp`, `mv`, `rm`, `sed -i`, ...) that
   target a routing control (`.git`, `.project/STATE.md`, `.project/next`,
-  `.gsd-path`) while `.project/STATE.md` exists
+  `.gsd-path`) while `.project/STATE.md` exists, or target a product file
+  outside the routed build phase (same rule as direct file-edit tools)
 - repeated assignments to the same shell variable within one command; split
   these into separate tool calls so write targets can be resolved
 - copies whose destinations, including nested recursive-copy entries, resolve
@@ -142,7 +146,8 @@ See [UPDATE.md](UPDATE.md).
   source trees containing directory symlinks are denied; use literal directory
   paths and copy directory links separately
 - shell commands that reference the archive unless the whole command is a
-  recognized standalone read or a single-command invocation of the bundled
+  recognized standalone read, a pipeline in which each segment is a recognized
+  read, or a single-command invocation of the bundled
   `pipeline_state.py` / `archive_milestone.py` helper, resolved to a regular file
   inside the verified runtime selected by `.gsd-path/runtime.json` (legacy projects use `.gsd-path/runtime/` beside `guard_hook.py`
   in the repository layout), using exactly `python` or `python3` with optional
@@ -158,11 +163,93 @@ See [UPDATE.md](UPDATE.md).
 - deletion or move commands outside a single simple segment, including command
   chains, pipes, newlines, grouping, directory changes, and command substitution
 - deletion or move commands with any argument outside the literal-path character
-  set: ASCII letters, digits, `.`, `_`, `-`, and `/` (plus a drive prefix and
-  backslashes on Windows). One matching pair of surrounding quotes is allowed;
-  spaces, parameters, wildcards, braces, and tilde paths are denied even when
-  quoted. This also applies to `find -delete` and supported destructive aliases
+  set: ASCII letters, digits, `.`, `_`, `-`, `/`, and ASCII spaces inside one
+  shell unit (plus a drive prefix and backslashes on Windows). One matching
+  pair of surrounding quotes is allowed; parameters, wildcards, braces, and
+  tilde paths are denied even when quoted. This also applies to
+  `find -delete` and supported destructive aliases
 - destructive Git commands nested in supported shell and command wrappers
+- Git arguments that contain a shell parameter. Only plain `$name` and
+  `${name}` expansions pass, and only inside plain double-quoted spans of
+  read-only subcommands (`status`, `log`, `diff`, `show`, and the other
+  inspection commands) that the guard parses directly, such as
+  `git log --format="$t %H"` or `git show "HEAD:$f"`, because only double
+  quoting prevents word-splitting into options. A parameter outside double
+  quotes (`$x`, `HEAD:$f`, `--format=$x`, `"a b"$x`) is denied because its
+  expansion can split into a write option such as `--output`. Every other
+  parameter form (`${=x}`, `${(z)x}`, `${x:-y}`, `$x[@]`, `$1`, `$@`, `$*`,
+  `$#`, and the unbraced zsh flags `$=x`, `$~x`, `$^x`, `$+x`) is denied even
+  inside double quotes, because it can expand to more than one word; a
+  backslash-escaped marker (`"\$t"`) is likewise denied, because the shell
+  executes the literal text while the argument still shows the bare marker.
+  The same four zsh flags are denied in a `git -C` directory. A literal `$`
+  that starts no expansion (a regex anchor such as `--grep='fix$'`) passes.
+  A `-c`/`--config` key whose value git executes as a program —
+  `core.fsmonitor`, editors and pagers, `core.sshCommand`,
+  `core.askPass`, `filter.*` clean/smudge/process, `diff.*`
+  textconv/external/command, `merge.*` drivers, `core.gitProxy`,
+  `interactive.diffFilter`,
+  `remote.*` uploadpack/receivepack, `gpg.program` and `gpg.*.program`, `credential.helper` and
+  `credential.*.helper`, each `pager.<cmd>` key — is denied with a literal
+  value as with a parameter, because git runs it during an otherwise
+  read-only subcommand. A disabling form of such a key passes: the bare key,
+  an empty value, or `false`. A `--config-env` form is always denied, because
+  its value comes from the environment. A key through which git loads code —
+  `core.hooksPath`, `include.path`, `includeIf.*.path`, `url.*.insteadOf`,
+  `url.*.pushInsteadOf` — is denied with each value. `git config` is denied
+  when it sets one of these keys; to read or unset the key stays allowed.
+  A redirection at the end of a read (`git config <key> 2>/dev/null`) is not
+  a value. A separate digit before a redirection (`5 >/dev/null`), a word of two
+  or more digits (`12>/dev/null`) and a quoted operator are values, so they
+  make a set.
+  Each `git config` argument must be a plain literal word, bare or in one
+  pair of quotes: a backslash, mixed quotes, an unquoted glob (`*`, `?`, `[`),
+  an unquoted brace list or range (`{a,b}`, `{1..3}`) or a line continuation
+  in the word or one that joins it to the next word is denied, because the shell can make a different
+  argument list from it.
+  An unquoted word that starts with `#` among the `git config` arguments
+  is denied, because the shell reads it and the words after it as a comment.
+  The git subcommand word must be a plain literal word in each git command:
+  `git {config,...}` and a subcommand split by a line continuation are denied.
+  A program that runs the command in its arguments (`nice`, `nohup`,
+  `timeout`, `sudo`, `watch`, `time`, `env`, `stdbuf`, `setsid`) is
+  unwrapped: the guard skips the options of the program and checks the
+  command that it runs, so `nice git -c core.fsmonitor=/abs/h.sh status` is
+  denied by the git rule and `sudo apt install git` passes. A runner
+  option that writes, edits or enters a file or directory by itself is
+  denied (`time -o`, `sudo -e`, `sudo -D`, `sudo -R`, `watch -s`). The
+  `timeout` duration and the `watch` interval must be literal numbers, and
+  each runner option word must be a literal word; only a separate option
+  value can be a parameter in double quotes (`sudo -u "$USER" ls`). A short
+  option word is read as getopt reads it, so the attached value in
+  `sudo -upostgres psql` is not taken as more options. With an archive working directory a command runner is not
+  unwrapped and is denied as an unknown program. Other command
+  runners (`doas`, `ionice`, `noglob`) are not unwrapped, and `watch` with
+  the command in one quoted word is not checked.
+  Each git global option word, and the value word of `-c`, `-C`,
+  `--git-dir`, `--work-tree`, `--namespace` and `--config-env`, must resolve
+  to one word: a backslash, an unquoted glob or an unquoted brace list or
+  range in it is denied (`git -c {core.fsmonitor=/abs/h.sh,status}`,
+  `git -{p,c} core.fsmonitor=/abs/h.sh status`). A parameter in such a value
+  is denied also when no subcommand follows (`git -c $x`). Plain quoted parts
+  pass (`git -c user.name='A B' log`).
+  `git config` section renames and removals (`--rename-section`,
+  `--remove-section`) and `--edit` are denied, because a rename can move a
+  key into an executed section and `--edit` starts an editor.
+  Command substitution output, a parameter that starts an
+  argument, and a parameter in the value of an option that git writes to or
+  runs as a command (`--output`, `--upload-pack`, `--receive-pack`, `--exec`,
+  `-c`, `--config-env`, or a `<transport>::<address>` remote) are denied in
+  every form. These option names match by prefix (`--upload-pa`, `--exe`),
+  because git accepts abbreviated long options; in archive context the same
+  prefix match applies to `--output`, `--ext-diff`, and `--textconv`. The
+  exact read-only option `--text` is not an abbreviation and stays allowed. Any
+  other quoting construct in the command (`$'...'`, `$"..."`, quotes inside `${...}`, quotes or
+  backslashes in a comment, here-documents and here-strings) disables the
+  exception, so every parameter in a git argument of that command is denied.
+  The exception applies only to commands the guard parses directly, never
+  inside wrapped shell strings (`eval`, `bash -c`, `sh -c`, PowerShell or
+  `cmd` command strings), where the outer shell expands the parameter first
 - archive glob/brace expansions and execution-capable read options such as
   `rg --pre`
 - direct write, edit, and patch tool calls targeting `.project/STATE.md`,
@@ -262,9 +349,12 @@ writes nor verifies that wiring. To add it yourself, register
 | Antigravity | `.agents/hooks.json` `PreToolUse` | [Antigravity hooks](https://antigravity.google/docs/hooks) |
 | OpenCode | JS plugin `tool.execute.before` | [OpenCode plugins](https://opencode.ai/docs/plugins/) |
 | Zed | no hook API — git hooks only | — |
+| Muse Code | no GSD Path hook integration — git hooks only | — |
 
-**Caveats:** The hook cannot prove which skill initiated a shell command or a
-build-phase edit, so AGENTS.md owns those re-entry cases. Grok and Kimi
+**Caveats:** The hook cannot prove which skill initiated a build-phase edit
+when the routed build phase is already active. Shell product writes use the
+same phase gate as file-edit tools; AGENTS.md still owns plain-prompt re-entry
+when no `.project/STATE.md` exists. Grok and Kimi
 fail-open on hook errors by design. Copilot, Kimi, Kiro, and Antigravity may
 not intercept subagent tools — treat coverage as orchestrator-level.
 

package/QUICK.md

@@ -14,7 +14,7 @@ One router skill drives a gated pipeline: inspect → define → research → de
 plan → build → ship. Every handoff lives in `.project/` so any session can resume from disk.
 
 **Hosts:** Codex, Claude Code, Grok, OpenCode, Copilot CLI, Qwen, Antigravity,
-Cursor, Zed, Kiro, Kimi Code.
+Cursor, Zed, Kiro, Kimi Code, Muse Code.
 
 ---
 
@@ -22,7 +22,7 @@ Cursor, Zed, Kiro, Kimi Code.
 
 ```text
 [ ] 1. Install skills (step 1)
-[ ] 2. Install project rules in your repo (step 2) — skip if repo already has AGENTS.md
+[ ] 2. Install project rules in your repo (step 2) — an existing AGENTS.md keeps its text
 [ ] 3. Restart agent session
 [ ] 4. Open repo in agent; invoke router (step 3)
 [ ] 5. Approve gates as they appear (step 4)
@@ -105,6 +105,9 @@ Codex invokes it as `$gsd-path-discuss`.
 | Build | Escalations only |
 | Ship | Approve patch waves if blocked; approve archive and ship when green |
 
+For unattended quick-lane runs, see
+[pre-approval in the README](README.md#start-your-first-project).
+
 ---
 
 ## 5. Resume

package/README.md

@@ -10,20 +10,20 @@ parallel under `.project/next/` (lookahead); a building milestone can also be
 abandoned on an explicit ruling, archiving its partial work for a re-slice.
 
 **Supported hosts:** Codex, Claude Code, Grok, OpenCode, GitHub Copilot CLI,
-Qwen Code, Antigravity CLI, Cursor, Zed, Kiro, and Kimi Code.
+Qwen Code, Antigravity CLI, Cursor, Zed, Kiro, Kimi Code, and Muse Code.
 Support means the installer and dispatch contract exist. See the
 [host trust matrix](https://github.com/open-gsd/gsd-path/blob/main/docs/trust-validation/HOST-MATRIX.md) for live milestone
 proof and each host's guard tier.
 
 <!-- release-docs -->
-**Latest npm release:** [@opengsd/gsd-path@1.3.1](https://www.npmjs.com/package/@opengsd/gsd-path/v/1.3.1) — [release notes](CHANGELOG.md#131---2026-09-22)
+**Latest npm release:** [@opengsd/gsd-path@1.5.0](https://www.npmjs.com/package/@opengsd/gsd-path/v/1.5.0) — [release notes](CHANGELOG.md#150---2026-10-09)
 
 **Recent highlights**
-- describe untracked legacy migration in help
-- preserve older untracked runtimes during migration
-- Clarify legacy runtime backup guidance
-- Consolidate legacy runtime migration guidance
-- prepare 1.3.1 patch candidate
+- record runtime hotfix provenance on the declaration
+- add signed self-update
+- add the Skills, Stats, Settings, and Environment pages and the setup wizard
+- register the hosts, project operation, and env routes
+- add project setup operations for the app
 
 <!-- /release-docs -->
 
@@ -40,43 +40,52 @@ proof and each host's guard tier.
 | [WORKFLOW.md](WORKFLOW.md) | Phase-by-phase agent SOP |
 | [HOOKS.md](HOOKS.md) | Optional archive/git guard hooks |
 | [Jev screening](skills/gsd-path/references/jev-review.md) | Optional evidence screening; disabled by default, no SDK required |
-| [daemon/README.md](daemon/README.md) | Dashboard, menu-bar app, and monitoring setup |
-| [CHANGELOG.md](CHANGELOG.md) | Published release notes |
+| [daemon/app/README.md](daemon/app/README.md) | Desktop app: develop, release, and updates |
+| [daemon/README.md](daemon/README.md) | Monitor daemon: routes, configuration, and manual setup |
+| [CHANGELOG.md](CHANGELOG.md) | npm package release notes |
+| [daemon/app/CHANGELOG.md](daemon/app/CHANGELOG.md) | Desktop app release notes |
 | [RELEASE.md](RELEASE.md) | Maintainer CI and npm release cycle |
 | [GUIDE.md](GUIDE.md) | Pointer to the guides above |
 
-## What's new — September 19, 2026
+## What's new — October 2, 2026
 
 These changes are merged into the source checkout; npm installs use the latest
 published release.
 
-- **Dashboard settings and history:** edit Path settings, browse project files
-  and Git versions, and load full recorded evidence. See the
-  [dashboard guide](daemon/README.md#project-history-and-files).
-- **Model and effort policy:** set user, project, host, and task choices through
-  one resolver. Recorded assignments stay pinned; unsupported explicit choices
-  stop the affected dispatch. See the
-  [model policy](skills/gsd-path/references/model-policy.md).
-- **External worktrees and pinned runtimes:** new parallel task, verification,
-  and integration worktrees live outside project checkouts. Projects pin runtime
-  versions by content digest, with explicit upgrade, restore, and legacy migration
-  commands. See
-  [worktree locations](DOCS.md#worktree-locations) and
-  [runtime versions](DOCS.md#project-runtime-versions).
-- **Clearer project updates:** the dashboard shows project runtime versions and
-  update results. After verified integration, ordinary branches can resume
-  product work while archived milestones remain protected. See
-  [update guidance](UPDATE.md#update-the-project-runtime-and-guard-hooks).
-- **Optional Jev screening:** reviewers can request advisory checks of selected
-  criteria and evidence. It is disabled by default and never replaces recorded
-  verification or review gates. See
-  [Jev screening](skills/gsd-path/references/jev-review.md).
+- **Desktop app (pre-release):** one app for macOS, Windows, and Linux shows
+  your projects, manages skills in each coding agent, and updates itself. See
+  [Desktop app](#desktop-app).
+- **Skills from the published release:** the monitor installs skills from the
+  npm release, checks the download against the registry's sha512, and refuses
+  one that does not match. A release picker lets you stay on an older version.
+- **Safer monitor writes:** a monitor started by the app accepts changes only
+  with the app's local token, so another web page cannot change your setup.
+- **Environment editor:** edit a project's `.env` files with values masked and
+  a diff before each save.
+- **Usage charts:** tokens and cost per day, time per phase, tasks per wave,
+  and verify history. Missing data shows as missing, never as zero.
+- **Muse Code** is a supported host.
 
 ## Install from npm
 
 Requires **Node.js 18.17+** for the npm installer and **Python 3.9+** for
 project contracts and pipeline helpers. Install and sign in to a supported
 coding-agent host separately; GSD Path installs its skills, not the host itself.
+
+**Windows** runs natively; WSL is not required. Install
+[Git for Windows](https://git-scm.com/download/win): git hooks and task Verify
+commands run in its Git Bash, never the System32 WSL launcher (`GSD_PATH_BASH`
+overrides the path). Install a real Python from python.org or
+`winget install Python.Python.3.12`; the Microsoft Store `python` alias stub
+does not count. The installer accepts `python3`, `python`, or the `py -3`
+launcher. For deep managed-worktree paths, turn on long paths
+(`git config --global core.longpaths true` and Windows' `LongPathsEnabled`);
+`--doctor` warns about both. Git for Windows defaults to
+`core.autocrlf=true`, so project installs add a managed
+`/.project/** text eol=lf` rule to the repository's local `.git/info/attributes`
+(never committed; delete the `# gsd-path:begin` block to remove it). That keeps
+pipeline state LF in every worktree while product files follow your setting.
+
 The public npm package is **[@opengsd/gsd-path](https://www.npmjs.com/package/@opengsd/gsd-path)**.
 
 ```bash
@@ -98,7 +107,9 @@ npx @opengsd/gsd-path@latest --update --project /path/to/your-repo
 Use host flags such as `--claude --codex` instead of `--all` to select hosts.
 For project-local skills, run from your project directory and add `--local`
 to install and update commands. `--project PATH` selects where contracts are
-written; it does not change the directory used by `--local`. Run
+written; it does not change the directory used by `--local`. If the repo
+already has an `AGENTS.md`, the install adds a marked GSD Path block and keeps
+your text; see [project contracts](UPDATE.md#update-project-contracts). Run
 `npx @opengsd/gsd-path@latest --help` for all options. After installing, invoke
 `$path` in Codex or `/path` on slash-command hosts to start the pipeline.
 See [Install (summary)](#install-summary) for the host list and source-checkout commands.
@@ -116,6 +127,12 @@ contain newer changes.
 4. Resume later from the same folder with the router. Use `$path status`
    (Codex) or `/path status` to inspect progress without advancing.
 
+For an unattended quick-lane run, invoke `$gsd-path --pre-approve intent,plan`
+in Codex or `/gsd-path --pre-approve intent,plan` on slash-command hosts before
+milestone intent approval. This grants those two gates for one milestone when
+their checks pass. Required answers, failed checks, and other approval gates
+still pause for you. Shipping always needs manual approval.
+
 For a missing skill or an install problem, run:
 
 ```bash
@@ -134,65 +151,52 @@ project settings. Dashboard users can open **Settings → Path settings** for th
 same shipping, model/effort, and future review-panel controls. See
 [Path settings](skills/gsd-path/references/config.md) for precedence and locks.
 
-## Dashboard and menu-bar toolbar
-
-The optional **OpenGSD Path monitor** shows your projects without opening each
-project's `.project/` files. It watches the folders you choose and reads project
-state without advancing phase gates. Explicit Path settings saves use the
-validated configuration helper; background monitoring remains read-only.
-The monitor is a separate install from the npm skills package.
-
-### Dashboard
-
-The project board shows blocked, active, and shipped work, with milestone and
-phase progress, task counts, last activity, and available usage data. Use the
-[dashboard controls](daemon/README.md#dashboard) to filter or search projects,
-switch between Board and Milestones, refresh status, and manage settings.
-
-![OpenGSD Path project board showing sample projects, status filters, milestone progress, tasks, and usage](docs/images/dashboard-board.png)
-
-Click a project to see its milestone roadmap, tasks, success criteria, review
-results, verification history, and activity. Usage includes tokens and turns
-from supported host session logs; cost estimates require model prices in the
-daemon configuration.
-
-![Project dashboard showing the history viewer link, milestone progress, expandable evidence, and usage with sample data](docs/images/dashboard-project.png)
-
-*Dashboard screenshots captured from the current source on September 19, 2026,
-using the repository's sample projects.*
-
-Open **History & files** to browse project files and archived milestones,
-preview Markdown, or read a file at a selected Git commit. Relative document
-links keep that selected version. **Records & sources → Load full records**
-loads recorded usage, verification, activity, and indexed host turns on demand,
-with coverage details that make missing or invalid data visible.
-
-Open **Settings → Path settings** to change user defaults or project overrides
-for shipping mode, model and effort choices, and future review panels. Each
-setting shows its source and any lock reason; changes are saved explicitly.
-
-The **Plugin** settings page shows each watched project's runtime version and
-provides an explicit **Update** action with progress and failure details.
-Updating global skills does not update a project's pinned runtime.
-
-### macOS menu bar
-
-Click the OpenGSD Path menu-bar icon for a compact project list with phase
-meters and task progress. Click a project to open its dashboard page. The
-bottom toolbar opens the dashboard, plugin settings, and watched folders;
-it also provides rescan, appearance, and quit controls. The daemon row shows
-its running state and provides restart and stop controls. Option-click the
-menu-bar icon to open the dashboard directly.
-
-<img src="docs/images/macos-menu-bar.png" alt="OpenGSD Path native macOS panel with sample projects and its bottom toolbar" width="400">
-
-*Screenshots show the current UI with sample project data. The native panel is
-captured in its preview window.*
-
-### Install the monitor
-
-The monitor requires Python 3.9+. From a source checkout, preview the setup,
-then install (macOS/Linux shell):
+## Desktop app
+
+The **OpenGSD Path app** shows your projects without opening each project's
+`.project/` files, and manages the Path setup on your computer. It is a
+pre-release for testers.
+
+**Get it:** download the installer for your system from the newest `app-v`
+entry on the [releases page](https://github.com/open-gsd/gsd-path/releases):
+`.dmg` (macOS, Apple Silicon or Intel), `.msi` (Windows), `.deb` or AppImage
+(Linux). The app needs Python 3.9+ and Git; its first screen checks for both
+and shows the fix when one is missing.
+
+macOS builds are signed with a Developer ID and notarized by Apple from 0.1.1
+on, so they open without an approval in Privacy & Security. Windows builds have
+no code signature yet: SmartScreen shows a warning; choose **More info → Run
+anyway**.
+
+What the app does:
+
+- **Projects:** blocked, active, and shipped work with milestone and phase
+  progress, tasks, last activity, and usage. A project page shows its
+  roadmap, tasks, success criteria, reviews, verification history, files at
+  any Git version, and full recorded evidence.
+- **Skills:** which coding agents have Path skills, at which version, with
+  preview, install, update, and uninstall. Every write shows a preview or a
+  plan first.
+- **Project setup:** runtime version, guard hooks, health check, and, for a
+  multi-repo coordinator, member hooks and marker repair.
+- **Settings:** updates, Path settings (shipping mode, models, review panel),
+  watched folders, model prices, launch at login, and appearance.
+- **Stats** and the per-project **Environment** editor.
+- **Tray:** a compact project list, items that need attention, and controls
+  to start, restart, and quit.
+
+The app only watches and sets up. It never advances a phase; approvals and
+rulings stay in your agent. It updates itself: it checks a signed update file,
+asks before it installs, and refuses an update whose signature does not match.
+
+Background monitoring is read-only. The app starts a local monitor (the
+daemon) and stops it on quit. See the [app guide](daemon/app/README.md) and the
+[daemon guide](daemon/README.md).
+
+### Manual monitor (without the app)
+
+From a source checkout you can still run the monitor and its browser
+dashboard without the app. It requires Python 3.9+:
 
 ```bash
 git clone https://github.com/open-gsd/gsd-path.git
@@ -201,33 +205,20 @@ PYTHONPATH=daemon python3 -m gsd_daemon install --dry-run
 PYTHONPATH=daemon python3 -m gsd_daemon install
 ```
 
-On Windows, after cloning and entering `gsd-path`, use PowerShell:
+On Windows, use PowerShell in the `gsd-path` folder. The last command starts
+the monitor for this session; it starts by itself at later logins:
 
 ```powershell
 $env:PYTHONPATH = "daemon"
 python -m gsd_daemon install --dry-run
 python -m gsd_daemon install
-```
-
-On Windows, launch the installed shortcut for this session before opening the
-dashboard. It starts automatically at future logins:
-
-```powershell
 Start-Process "$env:APPDATA\Microsoft\Windows\Start Menu\Programs\Startup\gsd-path-daemon.lnk"
 ```
 
-Open **http://127.0.0.1:8765**, then use **Settings → Watched folders** to add
-your project folders. The installer creates an isolated Python environment and
-configures autostart. On macOS it also builds and installs the native menu-bar
-app; this requires macOS 12+ and Xcode Command Line Tools (`swiftc`). On
-macOS, use `--no-tray` for the dashboard only. Linux autostart runs the
-dashboard; launch the optional tray separately with
-`~/.gsd-path/venv/bin/gsd-path-daemon tray`. Windows uses a tray-and-dashboard
-Startup shortcut; see the [daemon guide](daemon/README.md) for platform details.
-
-See the [daemon guide](daemon/README.md) for configuration, usage pricing,
-manual startup, and platform setup, or the [macOS guide](daemon/macos/README.md)
-for native menu-bar details.
+Then open **http://127.0.0.1:8765**. The first launch of the desktop app
+removes this older autostart entry so only one monitor runs. See the
+[daemon guide](daemon/README.md) for platform details, configuration, and
+usage pricing.
 
 ## Skills
 
@@ -362,6 +353,35 @@ default checkout, `gsd-path/M001` branch, and sibling linked worktree. A
 journaled helper performs the approved creation and safely resumes a matching
 partial remote/clone/worktree transaction; the default checkout stays clean.
 
+## Multi-repo milestones
+
+One project can change several repositories in the same milestone. The
+**coordinator** repo holds `.project/` and runs the pipeline; each other repo
+is a **member** listed in `.project/MEMBERS.md`. A member needs a GitHub.com
+`origin` whose default is `main`. See
+[ADR 0002](docs/adr/0002-multi-repo-coordinator.md) for the design.
+
+- Add members at a milestone boundary: ask the router to add an existing repo
+  (`members.py add`) or to create a new one (`members.py add --create`, after
+  you approve the exact owner, name, visibility, and checkout). For optional
+  guard hooks, install them in the member with
+  `npx @opengsd/gsd-path@latest --member-of <coordinator> --project <member>`.
+- The planner gives each member task `repo: <member>`; one task changes one
+  repo. Project Verify runs from the coordinator and reaches a member as
+  `../<member>`.
+- Build works in Path-owned member branches `gsd-path/<project>-M00N` and
+  records each member landing in the coordinator. The final review names each
+  member's reviewed HEAD.
+- Ship closes members in order before the coordinator: `close-members` merges
+  each member in its own `direct` or `pull-request` mode and tags it
+  `milestone/<project>-<archive>`, then the ship commit records each member.
+  A pull-request member waits for you to merge it. The next milestone retires
+  the member branches.
+- `members.py detect --checkout <path>` reports whether a repo is a member.
+
+Out of scope: submodules, one task across two repos, non-GitHub remotes, and
+an atomic close across repos.
+
 ## Handoff contract
 
 ```text
@@ -422,7 +442,7 @@ node scripts/install.mjs --all --update --project /path/to/project   # refresh .
 
 | Flag | User skills root | Invoke |
 | --- | --- | --- |
-| `--codex`, `--zed` | `~/.agents/skills` | Codex: `$path` or `$gsd-path`; Zed: `/path` or `/gsd-path` |
+| `--codex`, `--zed`, `--muse` | `~/.agents/skills` | Codex: `$path` or `$gsd-path`; Zed, Muse: `/path` or `/gsd-path` |
 | `--claude` | `~/.claude/skills` | `/path` or `/gsd-path` |
 | `--cursor` | `~/.cursor/skills` (+ subagent) | `/path` or `/gsd-path` |
 | `--grok` | `~/.grok/skills` | `/path` or `/gsd-path` |

package/RUNTIME.md

@@ -68,7 +68,7 @@ skeptic attempts under `skeptics/`.
 | `skeptics --repo <root> --wave <N> --cycle <C> --child-command '<cmd>' [--wait <s>] [--child-timeout <s>]` | Step 7 skeptic branch: one read-only skeptic per `skeptic_groups` locator in its own sidecar at the recorded review base, briefed with the criterion, every observation, and the cited tasks verbatim; validate with `review_findings.py`, collect, retire, then rerun the helper. `none` without skeptic groups; `escalate` for structural blockers or the cycle cap. The skeptic files stay uncommitted for the fix-task or ruling checkpoint. |
 | `fix-tasks --repo <root> --wave <N> --cycle <C>` | Step 7 batching: one fix task per `review_findings.py collect` batch with the failed criteria and observations verbatim, lint-checked; `escalate` for structural blockers, skeptic groups, cycle cap, or all-refuted. |
 | `complete --repo <root>` | Completion: clean primary at `build/active` (or a crash-left `build/done`), no unfinished wave, the archive-time review cycle check (`discussion_validate.review_cycle_counts`: contiguous cycles, passing last cycle, panel and skeptic artifacts present); `workflow_run.py build-evidence` at HEAD; `pipeline_state.py transition` to `ship/active` with event `build done; final review pending`; checkpoint `build: complete milestone`. |
-| `finish --repo <root> --task-id <id>` | Recover first; return a proven landing without repeating Verify, or verify, land, record, and retire one returned task. Without a dispatch record, derive the isolate from task frontmatter. |
+| `finish --repo <root> --task-id <id>` | Recover first; return a proven landing without repeating Verify, or verify, land, record, and retire one returned task. Without a dispatch record, or when the newest record is settled and its base differs from the task's current in-progress base (a native retry after a driver block), read the primary task's in-progress state; if it lacks a recorded base, use the parallel task isolate's state only if that worktree is authorized. A blocked record at the same base still refuses the retry. A deactivated isolate stays blocked. |
 | `answer --repo <root> --task-id <id> --answer '<text>'` | Append `Orchestrator answer:` to the isolate's task Log; the next `round` redispatches that isolate. |
 | `status --repo <root>` | Every task's newest dispatch record. |
 
@@ -91,7 +91,7 @@ argument slots defined in the dispatch model policy.
 calls. In `round`, an unfinished earlier wave blocks dispatch before the bookkeeping
 checkpoint. Child completion is recorded in `exit.json`; the parent alone
 writes `state.json`.
-For `review`, `panel`, and `skeptics`, when the child process is gone and `finished_at` is
+For `round`, `review`, `panel`, and `skeptics`, when the child process is gone and `finished_at` is
 unset, the driver rereads that attempt's state and exit receipt before
 collecting the result or blocking with
 `child wrapper exited without recording a result`.