session-orchestrator 3.24.0 → 4.0.1

package/templates/_shared/journey-manifest.md

@@ -1,12 +1,15 @@
 <!-- source: session-orchestrator plugin (canonical: templates/_shared/journey-manifest.md) -->
 <!--
+  Retired with /journey-audit in 4.0.0 — kept as a template for a per-repo
+  product-truth manifest; no command consumes it.
+
   Copy to `.orchestrator/journey-manifest.md` in the target repo and fill in every
-  section. `/journey-audit` REFUSES to run without this file.
+  section. While `/journey-audit` existed, it refused to run without this file;
+  with the command removed, filling this in is optional documentation only.
 
-  The `## SAFETY` block is what gates R5 (the real end-to-end run against
-  production with a real account). Absent or empty → R5 is not dispatched and the
-  audit runs as a dry-run (R1–R4 + R7). Nothing else in this file can substitute
-  for it: the skill reads THIS heading, not your intent.
+  The `## SAFETY` block described what gated R5 (the real end-to-end run against
+  production with a real account) when the skill still ran. Kept below for
+  reference in case a future consumer re-adopts the same manifest shape.
 
   Credentials: env-var NAMES only, never values. A value pasted here is a secret
   in a tracked file.
@@ -14,7 +17,8 @@
 
 # Journey Manifest — <REPO NAME>
 
-> Per-repo input for `/journey-audit`. Product truth, not code structure.
+> Per-repo product-truth manifest, not code structure.
+> Retired with `/journey-audit` in 4.0.0 — no command consumes this file today.
 > Last verified: <YYYY-MM-DD> by <operator>
 
 ## Personas & Einstiegspunkte

package/.cursor/commands/autopilot-multi.md

@@ -1,14 +0,0 @@
----
-description: Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice)
-argument-hint: [--dry-run|--apply] [--max-stories=N] [--max-hours=H] [--inactivity-timeout=S] [--stall-seconds=S] [--draft-mr=off|on-loop-start|on-green] [--json] [--verbose]
----
-
-# /autopilot-multi
-
-Use the Session Orchestrator command definition at `commands/autopilot-multi.md`.
-
-Arguments: $ARGUMENTS
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.
-
-Cursor has no Skill tool. When the command says to invoke a skill, Read `skills/<skill-name>/SKILL.md` and follow it. Supporting files (`soul.md`, phase docs) live in that same `skills/<skill-name>/` directory.

package/.cursor/commands/contract-version-bump.md

@@ -1,14 +0,0 @@
----
-description: Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift
-argument-hint: [--contract <path>]
----
-
-# /contract-version-bump
-
-Use the Session Orchestrator command definition at `commands/contract-version-bump.md`.
-
-Arguments: $ARGUMENTS
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.
-
-Cursor has no Skill tool. When the command says to invoke a skill, Read `skills/<skill-name>/SKILL.md` and follow it. Supporting files (`soul.md`, phase docs) live in that same `skills/<skill-name>/` directory.

package/.cursor/commands/journey-audit.md

@@ -1,14 +0,0 @@
----
-description: Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
-argument-hint: [manifest-path]
----
-
-# /journey-audit
-
-Use the Session Orchestrator command definition at `commands/journey-audit.md`.
-
-Arguments: $ARGUMENTS
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.
-
-Cursor has no Skill tool. When the command says to invoke a skill, Read `skills/<skill-name>/SKILL.md` and follow it. Supporting files (`soul.md`, phase docs) live in that same `skills/<skill-name>/` directory.

package/.cursor/skills/contract-version-bump/SKILL.md

@@ -1,12 +0,0 @@
----
-name: contract-version-bump
-description: "Use this skill when changing a machine-readable contract — a JSON Schema, an API spec, or a config schema — and bumping its version: tightening a constraint, adding/removing/renaming a field, introducing a breaking change, raising an API version, or writing the changelog entry for a schema change. Trigger on \"change the schema\", \"tighten this constraint\", \"bump the schema version\", \"breaking change to the API\", \"new API version\", \"changelog entry for a schema change\". Runs six phases — classify against the contract's OWN versioning rule (not generic semver instinct), find every version literal and vendored copy, check consumer compatibility for new keywords, apply consistently, write the changelog entry, and report downstream drift — codifying three non-obvious traps hit in a real case (GitLab issue #17, `aiat-enablement` repo, 2026-07-25)."
----
-
-# contract-version-bump
-
-Canonical skill: `skills/contract-version-bump/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/contract-version-bump/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the contract-version-bump skill" as: Read `skills/contract-version-bump/SKILL.md`.

package/.cursor/skills/daily/SKILL.md

@@ -1,12 +0,0 @@
----
-name: daily
-description: "Use this skill when creating today's daily note in the Meta-Vault (03-daily/YYYY-MM-DD.md) with valid vaultFrontmatterSchema-compliant YAML frontmatter. Idempotent: re-running on the same day opens the existing note instead of overwriting. Use when starting a work day, capturing scratch notes, or bootstrapping the inbox flow."
----
-
-# daily
-
-Canonical skill: `skills/daily/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/daily/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the daily skill" as: Read `skills/daily/SKILL.md`.

package/.cursor/skills/domain-model/SKILL.md

@@ -1,13 +0,0 @@
----
-name: domain-model
-description: Use when the user wants to stress-test a plan against the existing domain model and documented decisions. Grilling session that interviews the user one question at a time, sharpens fuzzy terminology inline, updates CONTEXT.md lazily, and offers ADRs sparingly under a 3-criteria gate. Reads docs/adr/ and CONTEXT.md if present.
-disable-model-invocation: true
----
-
-# domain-model
-
-Canonical skill: `skills/domain-model/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/domain-model/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the domain-model skill" as: Read `skills/domain-model/SKILL.md`.

package/.cursor/skills/journey-audit/SKILL.md

@@ -1,13 +0,0 @@
----
-name: journey-audit
-description: "Use this skill when the user wants the PRODUCT audited from the outside in — what the website promises vs what the code does vs what a real user experiences vs what actually arrives by mail vs what the data says is used. Runs a 7-role read-only wave (R5 writes only under an explicit SAFETY block) against a per-repo `.orchestrator/journey-manifest.md` and writes a dossier to docs/audits/. Distinct from /discovery, which checks code quality inside-out — this checks product truth outside-in; they complement, neither replaces the other. Triggers \"journey audit\", \"Nutzersicht-Audit\", \"audit the product from the user's side\", \"/journey-audit\"."
-disable-model-invocation: true
----
-
-# journey-audit
-
-Canonical skill: `skills/journey-audit/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/journey-audit/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the journey-audit skill" as: Read `skills/journey-audit/SKILL.md`.

package/.cursor/skills/skill-creator/SKILL.md

@@ -1,13 +0,0 @@
----
-name: skill-creator
-description: "Use when creating a new skill from scratch, modifying an existing skill, or optimizing a skill's triggering description. Guides intent capture, structure, writing patterns, and progressive-disclosure organization so skills reliably trigger and stay maintainable. Trigger on phrases like \"turn this into a skill\", \"write a skill for X\", \"improve this skill\", \"my skill isn't triggering\"."
-disable-model-invocation: true
----
-
-# skill-creator
-
-Canonical skill: `skills/skill-creator/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/skill-creator/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the skill-creator skill" as: Read `skills/skill-creator/SKILL.md`.

package/.cursor/skills/ubiquitous-language/SKILL.md

@@ -1,13 +0,0 @@
----
-name: ubiquitous-language
-description: "Use when the user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\". Extracts a DDD-style glossary from the current conversation into UBIQUITOUS_LANGUAGE.md, flags ambiguities and synonyms, and proposes opinionated canonical terms."
-disable-model-invocation: true
----
-
-# ubiquitous-language
-
-Canonical skill: `skills/ubiquitous-language/SKILL.md`
-
-Read that file and follow it exactly. Resolve relative links against `skills/ubiquitous-language/`, not this wrapper.
-
-Cursor has no Skill tool. Treat "invoke the ubiquitous-language skill" as: Read `skills/ubiquitous-language/SKILL.md`.

package/commands/autopilot-multi.md

@@ -1,74 +0,0 @@
----
-description: Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice)
-argument-hint: "[--dry-run|--apply] [--max-stories=N] [--max-hours=H] [--inactivity-timeout=S] [--stall-seconds=S] [--draft-mr=off|on-loop-start|on-green] [--json] [--verbose]"
----
-
-# Autopilot Multi
-
-Phase D `--multi-story` autopilot orchestrator. Runs N parallel issue pipelines in isolated git worktrees with per-loop kill-switches. v1 thin-slice — dry-run plan + basic apply mode. The user has invoked `/autopilot-multi` with arguments: **$ARGUMENTS**.
-
-## Status
-
-**v3.6 Phase D thin-slice (deep-1 2026-05-11).** Built on ADR-364 substrate: sessions.jsonl optional fields (`agent_identity`, `worktree_path`, `parent_run_id`), autopilot.jsonl extensions, 10th `STALL_TIMEOUT` kill-switch, `scripts/gc-stale-worktrees.mjs`, `validateWorkspacePath` helper. Runtime entrypoint at `scripts/autopilot-multi.mjs` with libs under `scripts/lib/autopilot/{dep-graph,worktree-pipeline,multi-killswitch,mr-draft,stall-sampler}.mjs`.
-
-Production-ready in v1: dry-run plan emission, basic apply mode (issue fetch + worktree spawn). Deferred to Phase D.2: cross-loop commit-wait, real SIGTERM cohort enforcement, on-green MR-draft trigger.
-
-## Usage
-
-```bash
-node scripts/autopilot-multi.mjs [OPTIONS]
-```
-
-## Flags
-
-| Flag | Default | Description |
-|------|---------|-------------|
-| `--max-stories <N>` | `3` | Max parallel loops (clamped 1..10) |
-| `--max-hours <H>` | `8` | Wall-clock budget in hours (0.5..24) |
-| `--inactivity-timeout <S>` | `300` | Seconds without completion → stop (60..3600) |
-| `--draft-mr <policy>` | `off` | `off` \| `on-loop-start` \| `on-green` |
-| `--stall-seconds <S>` | `600` | Per-loop STALL_TIMEOUT threshold in seconds (60..3600) |
-| `--dry-run` | `true` | Emit plan only, do not execute |
-| `--apply` | `false` | Execute the plan (mutex with `--dry-run`) |
-| `--json` | `false` | Machine-readable canonical envelope output |
-| `--verbose` | `false` | Diagnostic output to stderr |
-| `-h`, `--help` | — | Show usage and exit |
-| `--version` | — | Print plugin version and exit |
-
-## Exit Codes
-
-| Code | Meaning |
-|------|---------|
-| `0` | Success |
-| `1` | User error (bad flags, mutex violation) |
-| `2` | System error (libs/binaries/probe failed) |
-
-## Behaviour
-
-**Issue selection (OPEN-1):** queries `glab issue list --label "status:ready"`. Only issues with that label are eligible for parallel pickup.
-
-**Concurrency cap (OPEN-2):** `min(--max-stories, floor(free_ram_gb / 4) - 1)`. On a 24 GB host this typically resolves to 3 parallel loops; on a 16 GB host, 2.
-
-**Stop condition (OPEN-3):** first of (a) any loop kill-switch trips, (b) backlog drained, (c) inactivity timeout exceeded, (d) wall-clock `--max-hours` exhausted.
-
-**Cross-loop wait (OPEN-4):** loop B waits for loop A's **commit on its branch** (not MR-merge). B rebases onto A's branch when A's commit lands. Dependency graph computed via `scripts/lib/autopilot/dep-graph.mjs`.
-
-**Failure isolation (OPEN-5):** first `SPIRAL` triggers a retry on the affected loop. A second `SPIRAL` triggers a cohort abort — all sibling loops receive SIGTERM (Phase D.2 will enforce a real kill; v1 marks them for abort and lets them exit naturally).
-
-**Draft MR (OPEN-6):** opt-in via `--draft-mr=on-loop-start` (immediate draft on worktree spawn) or `--draft-mr=on-green` (deferred until quality gates green — Phase D.2). Default `off` — no auto-merge in v1.
-
-**Worktree isolation:** every loop runs in its own `git worktree` rooted at `.orchestrator/worktrees/<issue-id>/`. `validateWorkspacePath` defence-in-depth runs before any `fsP.rm` from the gc sweeper. Stale worktrees are reaped by `scripts/gc-stale-worktrees.mjs` (run separately as housekeeping).
-
-## Critical Rules
-
-- Never invoke `/autopilot-multi` from inside a running session — top-level command only.
-- `--dry-run` and `--apply` are mutually exclusive. The runtime rejects the invocation with exit code 1 if both are passed.
-- Telemetry routes to `.orchestrator/metrics/autopilot.jsonl` (not `failures.jsonl`) per ADR-364 cross-connection rule 4.
-- Each loop atomically writes one autopilot.jsonl record per iteration via tmp+rename. Do not append directly to that file from any other code path.
-
-## See Also
-
-- "Autopilot Phase D" (#341; archived in the private Meta-Vault) — full PRD (status: shaped)
-- `docs/adr/2026-05-10-364-remote-agent-substrate.md` — ADR-364 substrate
-- `scripts/lib/autopilot/{dep-graph,worktree-pipeline,multi-killswitch,mr-draft,stall-sampler}.mjs` — implementation
-- [`/autopilot`](autopilot.md) — single-session headless driver (Phase C-1.b)

package/commands/contract-version-bump.md

@@ -1,28 +0,0 @@
----
-description: Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift
-argument-hint: "[--contract <path>]"
----
-
-# Contract Version Bump
-
-The user wants to bump the version of a machine-readable contract (JSON Schema, API spec, or
-config schema) after changing it. Invoke the contract-version-bump skill with arguments:
-**$ARGUMENTS**.
-
-Runs six phases: classify the change against the CONTRACT'S OWN versioning rule (not generic
-semver instinct), find every version literal and vendored copy across this repo and every repo
-in the instruction file's `cross-repos:` list (`CLAUDE.md`, or `AGENTS.md` on Codex CLI — the two
-are transparent aliases), check whether every known consumer actually evaluates each
-new/changed schema keyword, apply the bump consistently (with written exceptions, never silent
-ones), write a Keep-a-Changelog entry that calls out breaking-for-consumers risk explicitly
-regardless of version tier, and report any dependent repo/copy left un-synced as follow-up work.
-
-**Usage:**
-
-- `/contract-version-bump` — infer the contract file from conversation context
-- `/contract-version-bump --contract docs/spec/estate.schema.json` — target a specific contract file explicitly
-
-Codifies three traps from a real case (GitLab issue #17, `aiat-enablement` repo, 2026-07-25): a
-missing Patch clause that silently forbade a legitimate constraint tightening, five version-
-literal locations including a vendored copy in a different repo, and a `maxLength` keyword a
-hand-written consumer would have silently ignored.

package/commands/journey-audit.md

@@ -1,43 +0,0 @@
----
-description: Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
-argument-hint: "[manifest-path]"
----
-
-# Journey Audit
-
-Invokes the `journey-audit` skill (`skills/journey-audit/SKILL.md`). Dispatches roles R1–R7 against
-the repo's journey manifest, re-verifies every P0 claim in the coordinator thread, and writes
-`docs/audits/YYYY-MM-DD-user-journey-audit.md`.
-
-Complements `/discovery` rather than replacing it: discovery checks code quality inside-out,
-journey-audit checks product truth outside-in.
-
-## Argument Validation
-
-The optional argument is a path to the manifest, overriding the default
-`.orchestrator/journey-manifest.md`. Use it for a second manifest (e.g. a staging variant) or when
-the repo keeps it elsewhere.
-
-- `/journey-audit` — uses `.orchestrator/journey-manifest.md`
-- `/journey-audit .orchestrator/journey-manifest.staging.md` — uses that file instead
-
-If the argument names a file that does not exist, say so and stop — do NOT silently fall back to
-the default path, because auditing the wrong manifest produces findings that look valid and are not.
-
-## Behavior
-
-1. **Gates** — bootstrap gate, then the manifest HARD-GATE: no manifest → refuse and point at
-   `templates/_shared/journey-manifest.md`; no filled `## SAFETY` block → run without R5 and say so.
-2. **Peer-session check** — announce the audit before dispatching (`.claude/rules/parallel-sessions.md`).
-3. **Wave** — R1–R7 in parallel, all read-only except R5, each fed from the manifest.
-4. **Coordinator re-verification** — every P0 re-checked with the coordinator's own command before
-   it enters the dossier. This step is not optional and not delegable.
-5. **Dossier + closing AUQ** — fixed section order, then fix-wave packages (multiSelect) and an
-   optional issue batch via `skills/gitlab-ops/SKILL.md` label taxonomy.
-
-## Related
-
-- `skills/journey-audit/SKILL.md` — the skill, in full
-- `templates/_shared/journey-manifest.md` — the per-repo manifest template (SAFETY block gates R5)
-- `docs/prd/2026-08-28-journey-audit-skill.md` — the PRD, incl. the first-run evidence
-- `commands/discovery.md` — the inside-out counterpart

package/pi/prompts/autopilot-multi.md

@@ -1,12 +0,0 @@
----
-description: Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice)
-argument-hint: "[--dry-run|--apply] [--max-stories=N] [--max-hours=H] [--inactivity-timeout=S] [--stall-seconds=S] [--draft-mr=off|on-loop-start|on-green] [--json] [--verbose]"
----
-
-# /autopilot-multi
-
-Use the Session Orchestrator command definition at `commands/autopilot-multi.md`.
-
-Arguments: $@
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/contract-version-bump.md

@@ -1,12 +0,0 @@
----
-description: Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift
-argument-hint: "[--contract <path>]"
----
-
-# /contract-version-bump
-
-Use the Session Orchestrator command definition at `commands/contract-version-bump.md`.
-
-Arguments: $@
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/journey-audit.md

@@ -1,12 +0,0 @@
----
-description: Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
-argument-hint: "[manifest-path]"
----
-
-# /journey-audit
-
-Use the Session Orchestrator command definition at `commands/journey-audit.md`.
-
-Arguments: $@
-
-Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.