mandrel 1.70.0 → 1.72.0

package/.agents/workflows/{qa-run-harness.md → qa-run.md}

@@ -2,7 +2,7 @@
 description: Drive Gherkin scenarios through a real browser as an agent-driven QA sweep
 ---
 
-# /qa-run-harness
+# /qa-run
 
 Execute a consumer's Gherkin `.feature` scenarios through a **real browser**
 (the chrome-devtools MCP surface), with the agent acting as the step executor
@@ -31,7 +31,7 @@ console filtering.
 ## Slash Command
 
 ```text
-/qa-run-harness <selector>
+/qa-run <selector>
 ```
 
 ### Arguments
@@ -58,9 +58,9 @@ deterministic, `(file, line)`-sorted scenario set under the contract's
 ### Examples
 
 ```text
-/qa-run-harness feature:login
-/qa-run-harness "tag:@smoke and not @wip"
-/qa-run-harness domain:billing
+/qa-run feature:login
+/qa-run "tag:@smoke and not @wip"
+/qa-run domain:billing
 ```
 
 The canonical tag taxonomy — `@smoke`, `@risk-high`, `@platform-web`,

package/README.md

@@ -158,6 +158,26 @@ npx mandrel sync                        # re-materialize ./.agents/
 npx mandrel doctor                      # verify the install
 ```
 
+## Benchmarking
+
+Mandrel's effectiveness is measured by a separate companion repo,
+**[mandrel-bench](https://github.com/dsj1984/mandrel-bench)** — a *consumer* of
+the published `mandrel` package. It pins a specific framework version,
+materializes it via `mandrel sync`, and drives Mandrel's own `/plan`→`/deliver`
+pipeline (plus a bare-model control) over a scenario corpus. Each run is scored
+across five dimensions — Quality, Planning fidelity, and Autonomy (what the
+scaffolding *buys*) versus Efficiency and Overhead ratio (what it *costs*) —
+reported as distributions with a noise-band, tracking the framework's
+**value-add over the bare-model baseline** across versions and models.
+
+The benchmark lives in its own repo on purpose: holding the harness fixed while
+varying the pinned `mandrel` version cleanly decouples harness-version from
+framework-version, and running through the published-package + `mandrel sync`
+path exercises the real consumer contract. The dependency is one-directional —
+`mandrel-bench` depends on `mandrel`, never the reverse. See the
+[mandrel-bench README](https://github.com/dsj1984/mandrel-bench#readme) for the
+dimensions, run model, and how to benchmark a new version.
+
 ## Contributors
 
 Only `.agents/` is distributed to consumers — it ships inside the

package/docs/CHANGELOG.md

@@ -2,6 +2,29 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.72.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.71.0...mandrel-v1.72.0) (2026-06-17)
+
+
+### Added
+
+* **plan:** add a headless/non-interactive flag to suppress the ideation one-pager + Phase-7 review gate ([#4223](https://github.com/dsj1984/mandrel/issues/4223)) ([#4226](https://github.com/dsj1984/mandrel/issues/4226)) ([9ffa355](https://github.com/dsj1984/mandrel/commit/9ffa35543f897199c096ad45a568de39b0424ba7))
+
+
+### Fixed
+
+* **deliver:** fail open on unparseable code-review severity bullets in auto-merge gate (refs [#4222](https://github.com/dsj1984/mandrel/issues/4222)) ([#4224](https://github.com/dsj1984/mandrel/issues/4224)) ([ca949bd](https://github.com/dsj1984/mandrel/commit/ca949bd7d98eea440571db6636f8be2f2128c3b9))
+
+## [1.71.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.70.0...mandrel-v1.71.0) (2026-06-16)
+
+
+### ⚠ BREAKING CHANGES
+
+* **workflows:** three operator-facing slash commands are renamed and three git commands are consolidated. Consumers must update muscle memory and any scripts: `/agents-update`→`/mandrel-update`, `/qa-run-harness`→`/qa-run`, and `/git-commit-all` / `/git-push` / `/git-pr-all`→`/git-deliver` (detection picks the old behavior by default; `--no-push` reproduces `/git-commit-all`, a feature-branch run reproduces `/git-push`, and a base-branch run or `--pr` reproduces `/git-pr-all`).
+
+### Changed
+
+* **workflows:** rename agents-update→mandrel-update, qa-run-harness→qa-run; collapse 3 git commands into git-deliver ([#4209](https://github.com/dsj1984/mandrel/issues/4209)) ([fc30a3d](https://github.com/dsj1984/mandrel/commit/fc30a3d579d80fd854217e066f97899b813c6be9))
+
 ## [1.70.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.69.0...mandrel-v1.70.0) (2026-06-16)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mandrel",
-  "version": "1.70.0",
+  "version": "1.72.0",
   "description": "Claude Code-first opinionated workflow framework: instructions, personas, skills, and SDLC workflows that govern AI coding assistants.",
   "files": [
     ".agents/",

package/.agents/workflows/git-commit-all.md

@@ -1,15 +0,0 @@
----
-description: Stage every untracked and modified file, then create a single conventional-commit on the current branch (no push).
----
-
-# /git-commit-all [Message]
-
-This is a compatibility alias for [`/git-push --no-push`](git-push.md) — it
-stages and commits all outstanding changes without pushing. See
-[`git-push.md`](git-push.md) for the canonical procedure, hook-failure guidance,
-and the parallel-execution warning.
-
-## Constraint
-
-Follow every constraint in [`git-push.md`](git-push.md) — this alias does not
-relax any of them.

package/.agents/workflows/git-pr-all.md

@@ -1,281 +0,0 @@
----
-description: >-
-  Stage all outstanding changes, commit, push to a feature branch, and open a
-  pull request with native auto-merge enabled.
----
-
-# /git-pr-all [Message] [--draft] [--no-auto-merge] [--branch <name>] [--base <branch>]
-
-This workflow is the **ad-hoc PR ergonomics** counterpart to the heavyweight
-`/deliver` pipeline. Use it when you have outstanding changes that do not
-belong to a planned Epic (typo fixes, file deletions, doc tweaks, dependency
-bumps, operator housekeeping) and you want a single command to take them from
-the working tree to a PR queued for auto-merge.
-
-It composes the three steps that used to live in
-[`/git-commit-all`](git-commit-all.md), [`/git-push`](git-push.md), and a
-manual `gh pr create` — no more dance, no more manually slugging branch
-names. Quality gates remain enforced by the existing pre-push hook; this
-workflow does not bypass them.
-
-> **When to run**: After making changes on `main` (or any base branch) that
-> are too small or too out-of-band for `/plan` + `/deliver` but
-> still need to land via the PR-required flow.
->
-> **Persona**: `devops-engineer` · **Skills**:
-> `core/git-workflow-and-versioning`
-
----
-
-## Arguments
-
-```text
-/git-pr-all [Message] [--draft] [--no-auto-merge] [--branch <name>] [--base <branch>]
-```
-
-- `Message` — the commit subject. First line becomes the PR title; if
-  the message contains a blank line, everything after the blank line
-  becomes the PR body. When omitted, an interactive prompt is suppressed
-  and a timestamped fallback (`chore: ad-hoc changes <ISO>`) is used.
-- `--draft` — open the PR in draft state and skip the auto-merge enable
-  step. Useful when you want CI to run before flipping to ready-for-review.
-- `--no-auto-merge` — open a normal (non-draft) PR but do not enable
-  GitHub's native auto-merge queue. The operator merges through the UI
-  when ready. Default behaviour is `gh pr merge --auto --squash --delete-branch`.
-- `--branch <name>` — override the auto-generated feature branch name.
-  When omitted, the branch is slugged from the commit subject (see
-  Step 2).
-- `--base <branch>` — override the merge target. When omitted, reads
-  `project.baseBranch` from `.agentrc.json` (default `main`).
-
----
-
-## Step 0 — Resolve Context
-
-1. Resolve `[BASE_BRANCH]` from `--base` or `.agentrc.json` →
-   `project.baseBranch` (default `main`).
-2. Read the current branch with `git rev-parse --abbrev-ref HEAD`.
-3. Determine the operating mode:
-   - **`from-base` mode** — current branch equals `[BASE_BRANCH]`. The
-     workflow must cut a feature branch in Step 2 before committing.
-   - **`from-feature` mode** — current branch is anything else. The
-     workflow commits + pushes to the existing branch in Step 3 and
-     opens (or updates) a PR from it.
-4. Verify the working tree has outstanding changes with
-   `git status --porcelain`. If the output is empty: **STOP** and tell
-   the operator there is nothing to PR.
-
----
-
-## Step 1 — Compose Commit Message
-
-If the operator passed `[Message]`, use it verbatim. Otherwise, fall back
-to `chore: ad-hoc changes <ISO 8601 timestamp>` so the commit is never
-unmessageable.
-
-Split the message on the first blank line:
-
-- **Subject** — the first line, used as the commit subject AND the PR
-  title.
-- **Body** — everything after the first blank line, used as the commit
-  body AND the PR body. May be empty.
-
----
-
-## Step 2 — Cut Feature Branch (from-base mode only)
-
-Skip this step in `from-feature` mode — the branch already exists.
-
-When `--branch <name>` is set, use it verbatim. Otherwise generate a
-branch slug from the commit subject:
-
-1. Detect the Conventional Commit type prefix (`<type>(<scope>): …`).
-   If matched, use `<type>` as the branch namespace. Allowed types:
-   `feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `build`, `ci`,
-   `perf`, `style`. Anything else (or no prefix) → `chore`.
-2. Strip the type prefix and any leading punctuation from the subject.
-3. Lowercase, replace non-alphanumeric runs with `-`, collapse repeated
-   hyphens, trim leading/trailing hyphens.
-4. Truncate to 50 chars on a word boundary.
-5. Combine: `<type>/<slug>`. Example: `"Delete unused files"` →
-   `chore/delete-unused-files`. `"fix(observability): drop stale handler"`
-   → `fix/observability-drop-stale-handler`.
-
-Cut and check out the branch:
-
-```powershell
-git checkout -b <branch-name>
-```
-
-If a local branch with that name already exists: pick a fresh name by
-appending `-2` (then `-3`, etc.) until `git rev-parse --verify` returns
-non-zero, and check that out instead.
-
----
-
-## Step 3 — Stage + Commit
-
-Stage all outstanding changes:
-
-```powershell
-git add -A
-```
-
-> **Why `-A` and not explicit paths?** `/git-pr-all` is operator-driven
-> (not parallel-agent-driven), so the single-tree assumption that
-> blocks `git add .` inside `/deliver` does not apply here. See
-> the parallel-execution warning at the bottom of this file.
-
-Commit:
-
-```powershell
-git commit -m "<subject>" -m "<body>"
-```
-
-If the body is empty, omit the second `-m`. If the pre-commit hook
-fails:
-
-1. Read the failure output.
-2. Fix the issue (run `npm run format`, fix lint errors, etc.).
-3. `git add -A` again.
-4. Re-run `git commit` (do **not** pass `--no-verify`).
-
----
-
-## Step 4 — Push with Upstream
-
-Push the branch and set its upstream so subsequent pushes do not need
-the explicit ref:
-
-```powershell
-git push -u origin <branch-name>
-```
-
-If the pre-push hook fails:
-
-1. Read the failure output.
-2. Fix the offending baseline / test / lint issue in the working tree.
-3. `git add -A`, `git commit --amend --no-edit` (the original commit
-   has not been pushed yet, so amend is safe).
-4. Re-run the push.
-
-If the pre-push hook is correctly blocking a real regression, fix the
-regression — never bypass the hook with `--no-verify`.
-
----
-
-## Step 5 — Open PR
-
-```powershell
-gh pr create --base <BASE_BRANCH> --head <branch-name> \
-  --title "<subject>" --body "<body-or-default>"
-```
-
-When `--body` would otherwise be empty, fall back to a single line:
-`Opened via /git-pr-all`. Pass `--draft` to `gh pr create` when the
-operator set the `--draft` flag.
-
-Capture the resulting PR URL from `gh pr create`'s stdout for the
-final summary.
-
----
-
-## Step 6 — Enable Auto-Merge (default)
-
-Skip this step when `--draft` or `--no-auto-merge` is set.
-
-```powershell
-gh pr merge <PR_NUMBER> --auto --squash --delete-branch
-```
-
-This queues the PR for merge as soon as required checks turn green and
-schedules deletion of the head branch on merge. Auto-merge requires
-`allow_auto_merge: true` on the repo (set by `/agents-bootstrap-github`,
-Story #1239).
-
-If `gh pr merge --auto` fails (missing repo feature, insufficient
-token scope), log the failure and surface it to the operator — the PR
-itself remains open and mergeable through the GitHub UI.
-
----
-
-## Step 7 — Summary
-
-Print a single block to the operator:
-
-```text
-✅ Opened PR #<PR_NUMBER>: <subject>
-   <PR_URL>
-   branch: <branch-name> → <BASE_BRANCH>
-   auto-merge: <enabled | draft | disabled>
-```
-
-Do **not** poll CI. That is the `/deliver` Phase 7 job and is
-overkill for ad-hoc changes. The operator (or GitHub's email
-notification) is the next watcher.
-
----
-
-## Troubleshooting
-
-- **Hook failures**: Treat the same way `/git-push` does — read the
-  output, fix the underlying issue, never `--no-verify`. The pre-push
-  hook (lint + format + maintainability + audit + coverage + CRAP) is
-  the same gate every PR has to pass eventually; failing here lets you
-  fix it before opening the PR rather than after CI fails.
-- **Branch already exists locally**: appended `-2`/`-3` per Step 2; this
-  is the same behaviour `gh repo` uses. If you want a specific name,
-  pass `--branch <name>` explicitly.
-- **`gh pr create` fails with "no commits between branches"**: the push
-  in Step 4 did not actually move the branch (e.g., it was already at
-  the same SHA as `[BASE_BRANCH]`). Verify `git log <BASE_BRANCH>..HEAD`
-  shows commits before re-running.
-- **PR template wins over `--body`**: if `.github/pull_request_template.md`
-  exists, `gh pr create --body` overrides it. To opt into the template
-  flow, drop the `--body` flag in Step 5 and pass `--editor` instead —
-  but that requires an interactive session. For ad-hoc PRs the explicit
-  body is the right default.
-- **Auto-merge does not fire after CI green**: confirm the PR's required
-  checks match the auto-merge requirements. The framework's quality gate
-  (`Validate and Test`) is the canonical required check; other checks
-  may be informational. Use the GitHub UI's "Merge when ready" surface
-  to inspect the queue state.
-
----
-
-## Constraint
-
-- **Never** push directly to `[BASE_BRANCH]`. Step 2's branch cut is
-  mandatory in `from-base` mode; remove it and the workflow becomes a
-  silent bypass of the PR-required policy.
-- **Never** pass `--no-verify` to `git commit` or `git push` to bypass
-  the quality gate. Fix the failure at the source.
-- **Never** force-push from `/git-pr-all`. This workflow is for opening
-  new PRs, not for rewriting history. Force-pushes belong to
-  `/git-merge-pr` (with `--force-with-lease` after a rebase) and
-  `/deliver` Phase 7 (with the operator's explicit context).
-- **Always** delete the head branch on merge (Step 6's
-  `--delete-branch` flag handles this for `--auto` mode; for
-  `--no-auto-merge` PRs the operator is responsible for the cleanup).
-- **Always** prefer `--auto --squash --delete-branch` unless the
-  operator explicitly opts out. The squash + auto-merge default gives
-  the same merge ergonomics `/deliver` produces, so main's commit
-  history stays uniform across both surfaces.
-
----
-
-## ⚠️ Parallel Story Execution
-
-Do **not** use this workflow from inside a parallel story-execution
-context (`/deliver #<storyId>`, `/deliver` wave dispatch).
-`git add -A` sweeps any untracked files in the working tree, which in
-a shared working directory may belong to another agent. In those
-contexts stage explicit paths only and confirm
-`git branch --show-current` reports the expected `story-<id>` branch
-before committing — see
-[`helpers/worktree-lifecycle.md`](helpers/worktree-lifecycle.md) for the
-shared-tree hazard and the worktree-isolation model that contains it.
-
-The same warning applies to any workflow that calls `git add .` or
-`git add -A`; this is not unique to `/git-pr-all` (see
-[`git-push.md`](git-push.md) for the canonical version).

package/.agents/workflows/git-push.md

@@ -1,63 +0,0 @@
----
-description: Commit all outstanding changes then push to the remote repository.
----
-
-# /git-push [Message] [--no-push]
-
-This workflow is the single source of truth for "stage + commit [+ push]"
-ergonomics. It accepts an optional `[Message]` and an optional `--no-push` flag.
-
-- **Default mode** — stage all outstanding changes, commit, then push the
-  current branch to its upstream remote.
-- **`--no-push` mode** — stage and commit only. Useful when you want to chain
-  several commits or defer the push. `/git-commit-all` is a compatibility alias
-  that maps to this mode.
-
-## Steps
-
-1. **Stage Changes**: Stage all new, modified, and deleted files.
-
-   ```powershell
-   git add .
-   ```
-
-2. **Commit Changes**: Commit the staged changes. If no message is provided, a
-   generic timestamped message will be used.
-
-   ```powershell
-   git commit -m "[Message]"
-   ```
-
-3. **Push to Remote** _(skip when `--no-push` is set)_: Push the current branch
-   to the upstream repository.
-
-   ```powershell
-   git push
-   ```
-
-## Troubleshooting
-
-- **Hook Failures**: If `git commit` or `git push` fails due to Husky/pre-commit
-  hooks (e.g., linting, formatting, or test failures), you MUST analyze the
-  error output, fix the issues in the codebase, and then re-run the failed
-  command.
-- **Upstream Conflicts**: If the push is rejected because the remote contains
-  work that you do not have locally, pull the latest changes first
-  (`git pull --rebase`) and resolve any conflicts before pushing again.
-
-## Constraint
-
-Never use `--no-verify` to bypass quality gates. If a hook fails, identify and
-fix the root cause (e.g., run `npm run format` or fix lint errors) before
-attempting to commit or push again.
-
-## ⚠️ Parallel Story Execution
-
-Do **not** use this workflow from inside a parallel story-execution context
-(`/deliver #<storyId>`). `git add .` sweeps any untracked files in the
-working tree, which in a shared working directory may belong to another agent.
-In that context, stage explicit paths only and confirm
-`git branch --show-current` reports the expected `story-<id>` branch before
-committing — see
-[`helpers/worktree-lifecycle.md`](helpers/worktree-lifecycle.md) for the
-shared-tree hazard and the worktree-isolation model that contains it.