@mmerterden/multi-agent-pipeline 16.4.0 → 16.6.0

package/pipeline/scripts/website-deploy-commit.sh

@@ -0,0 +1,97 @@
+#!/usr/bin/env bash
+#
+# website-deploy-commit.sh  -  commit and push the website sync under the identity
+# the deploy platform will actually build, then prove the build happened.
+#
+# Why this is a script and not three lines in the sync doc: the deploy platform
+# refuses to build a commit whose author is not a contributor on the project. The
+# push still succeeds, the deployment is created and sits at UNKNOWN with a 0ms
+# build (API `readyState: BLOCKED`), and the live site keeps serving the previous
+# version. v16.4.0 and v16.5.0 were both pushed that way and neither was built,
+# while the sync reported the website as synced both times.
+#
+# Usage:
+#   website-deploy-commit.sh <identity-name> <identity-email> <version> [repo-dir]
+#
+# Env:
+#   WEBSITE_SYNC_NO_PUSH=1     commit and verify locally, never push (smoke/dry-run)
+#   WEBSITE_SYNC_NO_VERIFY=1   skip the deployment check (offline, or no CLI)
+#   WEBSITE_SYNC_WAIT=<sec>    how long to wait for a Ready build (default 45)
+#
+# Exit: 0 committed+pushed (or nothing to do), 1 wrong author (nothing pushed),
+#       2 usage or environment, 3 pushed but no Ready production build.
+
+set -uo pipefail
+
+NAME="${1:-}"
+EMAIL="${2:-}"
+VERSION="${3:-}"
+DIR="${4:-$PWD}"
+
+if [ -z "$NAME" ] || [ -z "$EMAIL" ] || [ -z "$VERSION" ]; then
+  echo "usage: website-deploy-commit.sh <identity-name> <identity-email> <version> [repo-dir]" >&2
+  exit 2
+fi
+
+# An empty fourth argument is a caller bug, not a request for the current
+# directory: falling back to $PWD there commits whatever repo the caller happens
+# to be standing in.
+[ -n "$DIR" ] || { echo "FAIL: empty repo directory argument" >&2; exit 2; }
+cd "$DIR" 2>/dev/null || { echo "FAIL: cannot enter $DIR" >&2; exit 2; }
+git rev-parse --git-dir >/dev/null 2>&1 || { echo "FAIL: $DIR is not a git repository" >&2; exit 2; }
+
+# Read before writing. The website clone's own config is usually already correct,
+# and overwriting it with whatever identity the caller passed is the failure mode
+# this guard exists to prevent, not a convenience.
+[ "$(git config user.email || true)" = "$EMAIL" ] || git config user.email "$EMAIL"
+[ "$(git config user.name || true)" = "$NAME" ] || git config user.name "$NAME"
+
+git add -A
+if git diff --cached --quiet; then
+  echo "website: already in sync, nothing to commit"
+  exit 0
+fi
+
+git commit -q -m "chore: sync pipeline v${VERSION}" || { echo "FAIL: commit failed" >&2; exit 2; }
+
+# git config loses to an exported GIT_AUTHOR_EMAIL, so the recorded author is read
+# back off the commit itself. Anything else is a hope, not a check.
+ACTUAL="$(git log -1 --format=%ae)"
+if [ "$ACTUAL" != "$EMAIL" ]; then
+  echo "HALT: website commit authored by $ACTUAL, expected $EMAIL." >&2
+  echo "Nothing was pushed. Re-author it (git commit --amend --reset-author) and run this again;" >&2
+  echo "a commit the deploy platform does not recognise is accepted by the push and never built." >&2
+  exit 1
+fi
+
+if [ "${WEBSITE_SYNC_NO_PUSH:-0}" = "1" ]; then
+  echo "website: committed as $ACTUAL (push skipped)"
+  exit 0
+fi
+
+git push -q origin HEAD || { echo "FAIL: push rejected" >&2; exit 2; }
+echo "website: pushed v${VERSION} as $ACTUAL"
+
+# A push is not a deploy.
+if [ "${WEBSITE_SYNC_NO_VERIFY:-0}" = "1" ] || ! command -v vercel >/dev/null 2>&1 \
+  || [ ! -f "$DIR/.vercel/project.json" ]; then
+  echo "website: deployment not verified (no CLI or verification skipped)"
+  exit 0
+fi
+
+WAIT="${WEBSITE_SYNC_WAIT:-45}"
+ELAPSED=0
+while [ "$ELAPSED" -lt "$WAIT" ]; do
+  ROW="$(vercel ls --yes 2>/dev/null | grep -m1 'Production' || true)"
+  case "$ROW" in
+    *Ready*) echo "website: production build Ready"; exit 0 ;;
+    *Error*) break ;;
+  esac
+  sleep 5
+  ELAPSED=$((ELAPSED + 5))
+done
+
+echo "website: no Ready production build after ${WAIT}s -> ${ROW:-no deployment listed}" >&2
+echo "UNKNOWN with a 0ms build means the commit author was rejected: fix the author and push again," >&2
+echo "or deploy from the CLI with: (cd \"$DIR\" && vercel --prod --yes)" >&2
+exit 3

package/pipeline/skills/shared/core/multi-agent-analysis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: multi-agent-analysis
 language: en
-description: "Standalone feature-spec analysis (v3 template). Platform-agnostic concept layer with repo-driven convention extraction and per-platform Pass B render. 23 sections in Full mode; 8 of them in Lite mode (auto for small features). Collects Figma / Swagger / Confluence / Jira / Standards / Firebase / repo inputs, then stops. Does not chain into dev or create branches. Use when a feature needs a written specification before any code, from Figma, Swagger, Confluence, Jira or repo inputs."
+description: "Standalone feature-spec analysis. Two profiles picked at intake: global (23-section development handoff, 8 of them in Lite mode) or corporate (IG/UC/FG requirements document with traceability matrices). Platform-agnostic concept layer with repo-driven convention extraction and per-platform Pass B render; stack selection is optional. Collects Figma / Swagger / Confluence / Jira / Standards / Firebase / repo inputs, then stops. Does not chain into dev or create branches. Use when a feature needs a written specification before any code."
 user-invocable: true
 argument-hint: "[\"<analysis-name>\"] [--lite | --full] [--no-cache] [--preview-conventions]"
 ---
@@ -20,6 +20,21 @@ Produces a stakeholder-ready, platform-agnostic feature-spec document set (one m
 - To refresh a stale Confluence spec page
 - For API-only work (no Figma) or frontend-only work (no API) - the omission rule keeps the output clean
 
+## Profile
+
+Phase 0 Step 1b picks the analysis standard, and that selects the template. Both profiles read the same evidence; only the projection differs, which is what keeps them from drifting into two products.
+
+| Profile | Template | Shape |
+|---|---|---|
+| `global` (default) | `analysis-template.md` | Development handoff. Business rules with Gherkin acceptance criteria, architecture, files, tests. Zero-evidence sections drop. |
+| `corporate` | `analysis-template-corporate.md` | Requirements document. `IG -> UC -> FG` spine with three traceability matrices, current and target state with impact analysis, then technical and development analysis. The Part A backbone always renders, carrying `N/A` or `EKLENECEK`, and each `EKLENECEK` owes an open-question row. |
+
+One run emits one profile. A missing input never blocks either: the gap is written as `EKLENECEK` and raised as an open question instead of halting the run.
+
+**Stack is optional.** With no platform selected the run still completes: everything that does not need a target repository renders in full, only the development layer and the Pass B projection are skipped, and the output is a single file at `~/Desktop/multiAgentAnalysis/<feature-name>/<feature>.md` (never the current working directory, which for a repo-less run is arbitrary).
+
+**References are built, not written.** `build-references.mjs` projects `state.analysisSpec.evidence.*` into Section 21, carrying a precision anchor per row (Figma node id, Confluence pageId plus version, repo commit sha) and an access cell, so a source that could not be fetched is listed as unreachable rather than dropped. A coverage gate blocks dispatch on a consumed-but-unlisted source and on an invented row.
+
 ## Template (v3)
 
 Full mode renders 23 sections (Glossary, Changelog, References). Lite mode renders 7 sections (Summary, Goals + Non-Goals, User Stories, API Contracts, Architecture, Files to Add, References) and auto-activates for small features via three scored signals; `--lite` / `--full` flags always win.
@@ -44,7 +59,8 @@ When the rendered Section 20 (Risks and Open Questions) has open rows, the repor
 ## Detailed implementation
 
 Full steps: `$HOME/.claude/commands/multi-agent/analysis/SKILL.md`.
-Template master copy: `$HOME/.claude/multi-agent-refs/analysis-template.md`.
+Template master copies: `$HOME/.claude/multi-agent-refs/analysis-template.md` (global) and `$HOME/.claude/multi-agent-refs/analysis-template-corporate.md` (corporate).
+References builder: `$HOME/.claude/scripts/build-references.mjs`.
 Schema: `$HOME/.claude/schemas/analysis-spec.schema.json`.
 Convention extractor: `$HOME/.claude/lib/extract-conventions.sh` (output contract: `$HOME/.claude/schemas/conventions-output.schema.json`).
 

package/pipeline/skills/shared/core/multi-agent-sync/SKILL.md

@@ -175,7 +175,7 @@ npm publish --userconfig "$NPMRC"
 
 ## Website Sync (Step 4)
 
-Propagate the pipeline version, phase count, model count, and feature descriptions to the website.
+Propagate version, phase and model counts and feature descriptions to the website.
 
 ```bash
 gh auth switch --user {owner}
@@ -190,9 +190,10 @@ cd "$WEBSITE_DIR" && git pull origin main
 | `src/data/projects.ts` | Version number, tagline, description, feature list |
 
 ```bash
-cd "$WEBSITE_DIR"
-git add -A && git commit -m "chore: sync pipeline v{VERSION}"
-git push origin main  # Vercel auto-deploy
+# A commit the platform does not recognise is pushed fine and never built, so the site
+# keeps the old version. {identity} is the one routed to {owner}, not the run's own.
+# Why, signature, recovery: `$HOME/.claude/multi-agent-refs/website-deploy.md`.
+bash "$HOME/.claude/scripts/website-deploy-commit.sh" "{identity.name}" "{identity.email}" "{VERSION}" "$WEBSITE_DIR"
 ```
 
 
@@ -208,7 +209,7 @@ When invoked with the `release` argument:
 5. Commit + TAG  git commit + git tag v{VERSION}
 6. PUSH          git push --tags -> release.yml auto-publish
 7. DEV-TOOLKIT   Ship the companion MCP server if it moved (Step 3d gates, then publish)
-8. WEBSITE       Version + features -> {website-host}
+8. WEBSITE       Version + features -> {website-host} (maintainer identity, build verified Ready)
 9. COPILOT       Copilot CLI instructions + skills sync
 9b. CODEX        Codex CLI router skill + refs + agent TOML (node install.js --codex)
 10. Report       Summary: version, touched repos, deploy status