@ivorycanvas/qamap 0.3.0 → 0.3.2

package/docs/adoption.md

@@ -76,8 +76,8 @@ Start advisory, then tighten the gate once the findings are understood.
 When scanning a package inside a larger workspace, pass the workspace root so QAMap can separate package-local risks from repository guardrails:
 
 ```sh
-qamap doctor services/offer --workspace-root . --format markdown
-qamap scan services/offer --workspace-root . --json
+qamap doctor services/listing --workspace-root . --format markdown
+qamap scan services/listing --workspace-root . --json
 ```
 
 With `--workspace-root`, QAMap reads package-local files such as `package.json`, `.env.*`, and MCP config from the package path. It reads repo-level guardrails such as `AGENTS.md`, `.github/workflows`, `LICENSE`, `SECURITY.md`, and `CONTRIBUTING.md` from the workspace root.

package/docs/benchmarking.md

@@ -0,0 +1,31 @@
+# Benchmarking QAMap
+
+`scripts/bench.mjs` scores QAMap's plan/qa output against a fixed set of repositories with pinned commits, so heuristic changes can be judged by numbers instead of feel. The runner is read-only against every target.
+
+## Setup
+
+1. Copy `bench.config.example.json` to `bench.config.local.json` (gitignored).
+2. Point each target at a local repository checkout, pin `base`/`head` commit SHAs, and optionally declare expectations:
+   - `expect.runner` — the runner a human would pick for this repo (`playwright`, `maestro`, `manual`).
+   - `expect.mustReachFiles` — files a human QA would name for this diff window; recall against generated flows is reported.
+   - `expect.mustNameFlows` — substrings that should appear in at least one flow title.
+
+## Run
+
+```sh
+pnpm bench                      # table only
+node scripts/bench.mjs --save   # also writes bench-results/<timestamp>.json
+node scripts/bench.mjs --baseline bench-results/<file>.json   # delta vs a saved run
+```
+
+## Metrics
+
+- `runner` mismatch lines — wrong tool recommendation for a known repo shape.
+- `viaImport` — flows produced through the reverse import graph (shared-file changes reaching surfaces).
+- `diffAnchor` — flows whose selector set includes at least one selector introduced by the diff itself; higher means drafts act on what the change added instead of pre-existing UI.
+- `blank` — steps with blank action slots (must stay 0).
+- `generic` — flows with content-free names (`... primary journey`, `... smoke flow`); lower is better.
+- `reach` — recall of `mustReachFiles`; missing files are listed per target.
+- `agentBytes` — size of the `--format agent` payload.
+
+Re-run with `--baseline` before merging heuristic changes; a PR that moves these numbers should say so in its body.

package/docs/configuration.md

@@ -87,7 +87,7 @@ git switch main
 git pull
 qamap manifest context .
 qamap manifest init .
-qamap manifest init services/offer --workspace-root .
+qamap manifest init services/listing --workspace-root .
 qamap manifest validate .
 qamap manifest explain . --base origin/main --head HEAD
 ```
@@ -107,10 +107,10 @@ $schema: https://raw.githubusercontent.com/IvoryCanvas/qamap/main/schema/qamap-m
 version: 1
 
 domains:
-  - id: campaign
-    name: Campaign
+  - id: bundle
+    name: Bundle
     paths:
-      - src/pages/campaign/**
+      - src/pages/bundle/**
     criticality: medium
     source:
       kind: inferred
@@ -119,25 +119,25 @@ domains:
         - pages
 
 flows:
-  - id: campaign-application-complete
-    domain: campaign
-    name: Campaign Application Complete
+  - id: bundle-submission-complete
+    domain: bundle
+    name: Bundle Submission Complete
     entry:
-      route: /campaign/official/applicationComplete
+      route: /bundle/official/submissionComplete
       source: inferred
     runner: playwright
     anchors:
       - kind: route
-        path: src/pages/campaign/official/applicationComplete.tsx
-        route: /campaign/official/applicationComplete
+        path: src/pages/bundle/official/submissionComplete.tsx
+        route: /bundle/official/submissionComplete
         source: inferred
         confidence: high
     checks:
       - id: happy-path
-        title: Campaign Application Complete happy path works
+        title: Bundle Submission Complete happy path works
         type: success
       - id: api-failure-fixture
-        title: Campaign Application Complete handles failed, empty, or unauthorized responses
+        title: Bundle Submission Complete handles failed, empty, or unauthorized responses
         type: failure
     source:
       kind: inferred

package/docs/e2e-output-examples.md

@@ -59,19 +59,19 @@ When a repository has `.qamap/manifest.yaml`, QAMap should explain why a recomme
 ```txt
 Manifest recommendations: 3
 
-Campaign Application Complete `campaign-application-complete`
+Bundle Submission Complete `bundle-submission-complete`
 - Kind: flow
 - Confidence: high
-- Why this was recommended: Changed files match anchors for the Campaign Application Complete flow.
+- Why this was recommended: Changed files match anchors for the Bundle Submission Complete flow.
 - Evidence sources: product-qa
-- Manifest evidence: .qamap/manifest.yaml > flows.campaign-application-complete.anchors
-- If this is wrong: update .qamap/manifest.yaml > flows.campaign-application-complete.anchors
+- Manifest evidence: .qamap/manifest.yaml > flows.bundle-submission-complete.anchors
+- If this is wrong: update .qamap/manifest.yaml > flows.bundle-submission-complete.anchors
 - Next actions:
-  - Draft or review E2E coverage for the Campaign Application Complete flow.
-  - Cover the declared checks: Submit content URL successfully; Show validation error for invalid content URL.
+  - Draft or review E2E coverage for the Bundle Submission Complete flow.
+  - Cover the declared checks: Submit media link successfully; Show validation error for invalid media link.
 - Repair hints:
-  - If these files do not belong to this flow, update .qamap/manifest.yaml > flows.campaign-application-complete.anchors.
-  - If the recommended assertions feel vague, rewrite .qamap/manifest.yaml > flows.campaign-application-complete.checks in team language.
+  - If these files do not belong to this flow, update .qamap/manifest.yaml > flows.bundle-submission-complete.anchors.
+  - If the recommended assertions feel vague, rewrite .qamap/manifest.yaml > flows.bundle-submission-complete.checks in team language.
 ```
 
 This is the feedback loop: static analysis proposes a baseline, humans correct durable manifest entries, and future E2E recommendations become more specific without spending another LLM prompt on the same explanation.
@@ -93,26 +93,26 @@ Changed files: 1
 Matches: 3
 
 Matches:
-- Campaign Application Complete (flow, high)
-  Why: Changed files match anchors for the Campaign Application Complete flow.
-  Evidence: .qamap/manifest.yaml > flows.campaign-application-complete.anchors
-  If wrong: update .qamap/manifest.yaml > flows.campaign-application-complete.anchors
-  Checks: Submit content URL successfully; Show validation error for invalid content URL
+- Bundle Submission Complete (flow, high)
+  Why: Changed files match anchors for the Bundle Submission Complete flow.
+  Evidence: .qamap/manifest.yaml > flows.bundle-submission-complete.anchors
+  If wrong: update .qamap/manifest.yaml > flows.bundle-submission-complete.anchors
+  Checks: Submit media link successfully; Show validation error for invalid media link
 ```
 
 When that flow includes an entry route and checks, `qamap e2e draft` promotes it ahead of heuristic drafts:
 
 ```ts
 // Verification manifest evidence:
-// - Flow: Campaign Application Complete (campaign-application-complete)
-// - Entry route: /campaign/official/applicationComplete
+// - Flow: Bundle Submission Complete (bundle-submission-complete)
+// - Entry route: /bundle/official/submissionComplete
 // - Required checks:
-//   - [ ] Submit content URL successfully
-//   - [ ] Show validation error for invalid content URL
+//   - [ ] Submit media link successfully
+//   - [ ] Show validation error for invalid media link
 
-test("Campaign Application Complete", async ({ page }) => {
-  await test.step("Open route /campaign/official/applicationComplete.", async () => {
-    await page.goto("/campaign/official/applicationComplete");
+test("Bundle Submission Complete", async ({ page }) => {
+  await test.step("Open route /bundle/official/submissionComplete.", async () => {
+    await page.goto("/bundle/official/submissionComplete");
   });
 });
 ```
@@ -245,42 +245,42 @@ appId: ${APP_ID}
 When the changed file name exposes a narrower user action, the generated flow should use that action instead of stopping at a broad domain journey:
 
 ```txt
-Changed file: src/features/offer/components/ContentUrlSubmitModal.tsx
-Domain term: Offer
-Generated scenario: Offer Content URL Submit
-Generated draft path: .maestro/offer-content-url-submit.yaml
+Changed file: src/features/listing/components/MediaLinkSubmitModal.tsx
+Domain term: Listing
+Generated scenario: Listing Media Link Submit
+Generated draft path: .maestro/listing-media-link-submit.yaml
 ```
 
 The draft should then carry the same product-action wording into the runnable skeleton:
 
 ```yaml
-# Flow: Offer Content URL Submit
-# Domain scenario: Offer Content URL Submit
-# Intent: Verify the changed "Content URL Submit" behavior inside Offer instead of stopping at a generic primary journey.
+# Flow: Listing Media Link Submit
+# Domain scenario: Listing Media Link Submit
+# Intent: Verify the changed "Media Link Submit" behavior inside Listing instead of stopping at a generic primary journey.
 appId: ${APP_ID}
 ---
 - launchApp
-- tapOn: { id: "offer-content-url-submit" }
+- tapOn: { id: "listing-media-link-submit" }
 ```
 
 ## API / Service Contract
 
-For backend changes such as `src/v1/offer/utils.ts`, QAMap should not invent a browser journey. It should infer the domain word and stay contract-focused:
+For backend changes such as `src/v1/listing/utils.ts`, QAMap should not invent a browser journey. It should infer the domain word and stay contract-focused:
 
 ```txt
 Project: API / service
 Recommended runner: Manual
 
-Flow: Offer API contract smoke checklist
+Flow: Listing API contract smoke checklist
 Actor: API consumer or upstream service
-Trigger: Call the endpoint, handler, or service path affected by src/v1/offer/utils.ts.
+Trigger: Call the endpoint, handler, or service path affected by src/v1/listing/utils.ts.
 Success signal: the changed contract returns the expected status, response shape, auth behavior, and failure handling
 ```
 
 The manual draft should stay actionable:
 
 ```md
-# Offer API contract
+# Listing API contract
 
 ## Steps
 
@@ -367,7 +367,7 @@ If reusable repo-local evidence already exists, the PR QA output should point at
 
 ```txt
 Missing evidence before trusting this PR
-- [recommended] fixture: Confirm fixture coverage - Reuse or extend existing fixture/mock evidence for this flow: src/services/devSeedService.ts, src/services/reportMockService.ts.
+- [recommended] fixture: Confirm fixture coverage - Reuse or extend existing fixture/mock evidence for this flow: src/services/demoSeedService.ts, src/services/metricsMockService.ts.
 ```
 
 ```ts
@@ -423,24 +423,24 @@ Expected root-level behavior:
 Changed App/Package Targets
 
 | Target | Package | Project | Runner | Scoped Command |
-| services/offer | offer | Web | Playwright | qamap e2e plan services/offer --workspace-root . --base main --head HEAD |
+| services/listing | listing | Web | Playwright | qamap e2e plan services/listing --workspace-root . --base main --head HEAD |
 | apps/mobile | @acme/mobile | Expo / React Native | Maestro | qamap e2e plan apps/mobile --workspace-root . --base main --head HEAD |
 ```
 
 For package scans, QAMap should use workspace policy without leaking workspace-root paths into package-local drafts:
 
 ```sh
-qamap e2e plan services/offer --workspace-root . --base main --head HEAD
+qamap e2e plan services/listing --workspace-root . --base main --head HEAD
 ```
 
 Expected behavior:
 
 ```txt
 Workspace root: .
-Package root: services/offer
-Matched core flow: Offer submit
-Changed files: src/features/offer/submit.ts
-Generated draft path: docs/e2e/offer-submit.md
+Package root: services/listing
+Matched core flow: Listing submit
+Changed files: src/features/listing/submit.ts
+Generated draft path: docs/e2e/listing-submit.md
 ```
 
 The draft should mention package-local files:
@@ -448,7 +448,7 @@ The draft should mention package-local files:
 ```md
 Related Changed Files
 
-- `src/features/offer/submit.ts`
+- `src/features/listing/submit.ts`
 ```
 
 ## What Good Output Feels Like

package/docs/eval.md

@@ -12,7 +12,7 @@ For a complete PR-facing report that also includes QAMap review findings and sug
 qamap verify . --base origin/main --head HEAD --pr-body-file pr-body.md
 qamap eval . --base origin/main --head HEAD --format markdown
 qamap eval . --base origin/main --head HEAD --pr-body-file pr-body.md
-qamap eval services/offer --workspace-root . --base origin/main --head HEAD --include-working-tree
+qamap eval services/listing --workspace-root . --base origin/main --head HEAD --include-working-tree
 ```
 
 The GitHub Action can append the same report to the PR comment. On pull request events it reads the PR body from `GITHUB_EVENT_PATH`.

package/docs/github-action.md

@@ -40,7 +40,7 @@ jobs:
 ```
 
 Use `fetch-depth: 0` so QAMap can compare the pull request branch with the base ref.
-For production workflows, pin to a version tag such as `IvoryCanvas/qamap@v0.3.0` after that tag is published. Use `@main` only when intentionally testing unreleased behavior.
+For production workflows, pin to a version tag such as `IvoryCanvas/qamap@v0.3.2` after that tag is published. Use `@main` only when intentionally testing unreleased behavior.
 
 ## Monorepo Package
 
@@ -48,7 +48,7 @@ For production workflows, pin to a version tag such as `IvoryCanvas/qamap@v0.3.0
 - uses: IvoryCanvas/qamap@main
   with:
     mode: review
-    path: services/offer
+    path: services/listing
     workspace-root: .
     base: ${{ github.event.pull_request.base.sha }}
     head: HEAD

package/docs/manifest.md

@@ -208,10 +208,10 @@ $schema: https://raw.githubusercontent.com/IvoryCanvas/qamap/main/schema/qamap-m
 version: 1
 
 domains:
-  - id: campaign
-    name: Campaign
+  - id: bundle
+    name: Bundle
     paths:
-      - src/pages/campaign/**
+      - src/pages/bundle/**
     criticality: medium
     source:
       kind: declared
@@ -220,28 +220,28 @@ domains:
         - product-qa
 
 flows:
-  - id: campaign-application-complete
-    domain: campaign
-    name: Campaign Application Complete
+  - id: bundle-submission-complete
+    domain: bundle
+    name: Bundle Submission Complete
     entry:
-      route: /campaign/official/applicationComplete
+      route: /bundle/official/submissionComplete
       source: declared
     runner: playwright
     anchors:
       - kind: route
-        path: src/pages/campaign/official/applicationComplete.tsx
-        route: /campaign/official/applicationComplete
+        path: src/pages/bundle/official/submissionComplete.tsx
+        route: /bundle/official/submissionComplete
         source: declared
         confidence: high
     checks:
       - id: happy-path
-        title: Submit content URL successfully
+        title: Submit media link successfully
         type: success
-        selector: "[data-testid=content-url-submit]"
+        selector: "[data-testid=media-link-submit]"
       - id: invalid-input
-        title: Show validation error for invalid content URL
+        title: Show validation error for invalid media link
         type: failure
-        selector: "[data-testid=content-url-error]"
+        selector: "[data-testid=media-link-error]"
     source:
       kind: declared
       confidence: high

package/docs/quickstart-demo.md

@@ -1,10 +1,6 @@
 # 30-Second Quick Start Demo
 
-This demo is the shortest way to show what QAMap does in a public README, blog post, or launch thread.
-
-![QAMap 30-second PR demo](assets/qamap-30s-demo.gif)
-
-The GIF shows a simulated local PR where a checkout form changed. QAMap does not report a real browser test pass during `--dry-run`. It reports the generated verification artifact: the affected flow, the planned Playwright draft path, static self-check status, and the remaining work before the draft can be trusted as PR evidence.
+This demo is the shortest way to show what QAMap does in a public README, blog post, or launch thread. It is text-first on purpose: record a GIF only from the current published package and current `.qamap/manifest.yaml` flow, so the public demo never drifts from the CLI.
 
 ## Story
 

package/docs/release-validation.md

@@ -1,4 +1,20 @@
-# 0.2.1 Patch Release Validation
+# Release Validation
+
+## 0.3.2 - 2026-07-04
+
+Validated before publishing `0.3.2` (reverse import graph, diff-anchored steps and names, workspace-member project detection, Python service classification, start-here CLI guide):
+
+| Gate | Result |
+| --- | --- |
+| `pnpm test` | 100/100 passing |
+| `pnpm scan` (self-scan) | 0 findings |
+| Coverage thresholds (lines/branches/functions >= 80) | Passing |
+| `pnpm bench` against four pinned local benchmark targets (web monorepo, Python API server, Expo app, legacy Vue app) | Runner choice 4/4, labeled must-reach recall 9/9, blank actions 0, no metric regressions vs the previous baseline |
+| README demo | Real recorded run; the generated starter spec passes against the demo app |
+
+Historical validation notes for earlier releases follow below.
+
+# 0.2.1 Patch Release Validation (historical)
 
 QAMap should not publish a patch or minor version only because the CLI commands work in fixtures. The `0.2.1` release should prove that the manifest-backed QA skill flow is useful across representative repositories without requiring an LLM call.
 
@@ -148,7 +164,7 @@ The public demo must prove the product shape, not only command execution. Before
 - Remaining gaps are specific, such as auth fixture, API mock, stable selector, runner config, or validation command.
 - The demo makes clear when output is `--dry-run`, `review-only`, `near-runnable`, or `runnable-candidate`.
 
-Avoid demos that only say broad phrases such as "fixture needed", "selector missing", or "Offer flow recommended" without showing why those gaps matter for the changed behavior.
+Avoid demos that only say broad phrases such as "fixture needed", "selector missing", or "Listing flow recommended" without showing why those gaps matter for the changed behavior.
 
 ## Current Fixture Evidence Matrix
 
@@ -160,8 +176,8 @@ The matrix below is public, fixture-backed evidence from the repository test sui
 | Packaged PR QA skill template | `package metadata includes the portable PR QA skill template` | npm package metadata includes `skills`, and `skills/qamap-pr-qa/SKILL.md` contains the local PR QA workflow, `qamap qa` command, and manifest repair guidance. |
 | Verification manifest loop | `manifest init creates a baseline verification manifest`; `manifest init keeps Expo app file domains specific`; `manifest init captures advisory instruction context`; `manifest bootstrap produces concrete PR E2E draft from repo QA memory`; `e2e draft can use an external verification manifest for read-only adoption preview`; `manifest matches explain e2e and verify recommendations`; `manifest validate reports missing and stale manifest policy` | Generated `.qamap/manifest.yaml` includes `$schema`, domains, flows, anchors, checks, runner, source, and confidence; context preview reports repo-local instruction sources, role summaries, validation commands, safety rules, and diagnostics; validator reports missing/stale/duplicate policy; explain output maps branch changes to manifest domains/flows/checks; E2E drafts prefer `verification-manifest` sources with manifest evidence, route entry, detected input/action selectors, required checks, and manifest repair paths; external manifests can be passed with `--manifest` for read-only adoption smoke tests. |
 | Web app with Playwright routes | `generateE2ePlan matches committed core flow definitions`; `generateE2eDraft uses web selectors in Playwright specs`; `generateE2eDraft dry run previews files without writing drafts`; `generateE2eDraft asserts changed HTML success copy in Playwright specs`; `generateE2ePlan captures Playwright execution profile and self-check blockers`; `generateE2ePlan infers Playwright base URLs from dev scripts`; `generateE2eDraft supports Next app router route groups and concrete route hints`; `generateE2ePlan reads React Router object route paths`; `generateE2eDraft fills dynamic route params from concrete route hints`; `generateE2eDraft emits runnable Playwright role and input actions` | `Web` project profile, `playwright` runner, core-flow names such as `Checkout purchase`, route-aware Playwright drafts, dry-run preview status without filesystem writes, stable selector hints, changed HTML success copy assertions, execution profile, dev-script base URL hints, opt-in Playwright setup proposal, Next App Router route groups, React Router object paths, dynamic route params, draft self-check status, action items, and validation gaps. |
-| Expo / React Native mobile app | `generateE2ePlan recommends mobile flows for Expo changes`; `generateE2ePlan detects Maestro app ids from app config files`; `generateE2eDraft scopes entrypoint hints to each domain scenario`; `generateE2eDraft names changed component actions before generic primary journeys` | `Expo / React Native` project profile, `maestro` runner, app id and launch command hints from `app.json` or `app.config.*`, Maestro YAML drafts, `testID`/`accessibilityLabel` selector hints, action-specific scenario names such as `Offer Content URL Submit`, and mobile setup actions. |
-| API or backend service | `generateE2ePlan detects API service projects and suggests contract checklists`; `generateE2ePlan detects Django service apps from a workspace root`; `generateE2ePlan names versioned API service paths with domain language`; `generateE2ePlan uses matched core flow names for API service contracts` | `API / service` project profile, manual contract checklist, Django/FastAPI-style service signals when present, domain-aware titles such as `Offer API contract`, API consumer actor, endpoint/handler/service-path trigger, service start/test command hints, and contract failure coverage. |
+| Expo / React Native mobile app | `generateE2ePlan recommends mobile flows for Expo changes`; `generateE2ePlan detects Maestro app ids from app config files`; `generateE2eDraft scopes entrypoint hints to each domain scenario`; `generateE2eDraft names changed component actions before generic primary journeys` | `Expo / React Native` project profile, `maestro` runner, app id and launch command hints from `app.json` or `app.config.*`, Maestro YAML drafts, `testID`/`accessibilityLabel` selector hints, action-specific scenario names such as `Listing Media Link Submit`, and mobile setup actions. |
+| API or backend service | `generateE2ePlan detects API service projects and suggests contract checklists`; `generateE2ePlan detects Django service apps from a workspace root`; `generateE2ePlan names versioned API service paths with domain language`; `generateE2ePlan uses matched core flow names for API service contracts` | `API / service` project profile, manual contract checklist, Django/FastAPI-style service signals when present, domain-aware titles such as `Listing API contract`, API consumer actor, endpoint/handler/service-path trigger, service start/test command hints, and contract failure coverage. |
 | CLI package | `generateE2ePlan detects CLI packages and suggests command verification checklists` | `CLI` project profile from `package.json` bin entries, manual command verification checklist, CLI user or maintainer actor language, command invocation trigger, stdout/stderr/generated-file/exit-code success signal, valid and invalid argument coverage, and no required API fixture action unless the changed command path explicitly exposes network or fixture evidence. |
 | Design tokens and data catalogs | `generateE2ePlan detects design token packages and suggests artifact validation`; `generateE2ePlan detects data catalog repositories and suggests catalog verification` | `Design tokens` and `Data catalog` project profiles, manual artifact/catalog checklist, token or catalog actor language, schema/generated output/consumer fixture coverage, fixture readiness marked not needed for API mocks, and validation matrix rows that do not require browser/device selectors. |
 | Monorepo root and package targeting | `generateE2ePlan surfaces package-scoped targets for monorepo root changes`; `generateE2ePlan matches workspace core flows for package scans`; `generateTestPlan scopes monorepo changes to the requested package` | Root plans list changed app/package targets with package names, project type, runner, and scoped commands; package scans keep package-local changed files, workspace-level `.qamap/flows.yml` matches, package-local generated drafts, and no leaked workspace path prefixes in package drafts. |
@@ -171,21 +187,18 @@ The matrix below is public, fixture-backed evidence from the repository test sui
 | Existing test evidence | `generateE2ePlan evaluates existing test suite coverage evidence`; `generateE2ePlan keeps generic test filenames from overmatching unrelated services` | Coverage evidence rows that distinguish covered, partial, and missing targets without matching unrelated generic test filenames. |
 | Evidence-only changes | `generateE2ePlan treats test-only changes as evidence verification, not product journeys`; `generateE2ePlan treats docs-only changes as documentation verification`; `generateE2ePlan treats generated-only changes as generated artifact verification` | Test-only, docs-only, and generated-output-only branches produce maintainer-oriented evidence checklists instead of product journeys inferred from filenames such as `admin-primary-journey.spec.ts` or generated API clients. |
 
-See [E2E output examples](e2e-output-examples.md) for the kind of plan and draft snippets users should see from the `0.2.1` release.
+See [E2E output examples](e2e-output-examples.md) for the kind of plan and draft snippets users should see from the current release.
 
 ## Latest PR Validation Snapshot
 
-Last verified on 2026-07-03 on PR #71 after adding the manifest-free `qamap qa` PR QA skill entrypoint, the packaged `qamap-pr-qa` skill template, README repositioning, agent handoff docs, repo-context manifest PoC path, ADR-derived flow naming, and manifest-backed selector/action draft shaping:
+Last verified on 2026-07-03 for the 0.3.1 README demo patch after removing the stale animated GIF from the README and npm tarball:
 
 | Check | Result |
 | --- | --- |
-| `pnpm test` | 90 tests passed. |
-| `pnpm scan` | 0 findings. |
+| `pnpm test` | 95 tests passed. |
 | `git diff --check` | Passed. |
-| `pnpm pack --dry-run` | Passed; tarball includes `dist`, `docs`, `docs/assets/qamap-30s-demo.gif`, `schema`, `skills/qamap-pr-qa/SKILL.md`, `README.md`, `CHANGELOG.md`, `LICENSE`, and `package.json`. |
-| Coverage threshold | Passed the 80% line, branch, and function gates; latest run reported 85.27% line, 81.59% branch, and 94.26% function coverage. |
-| `pnpm run release:check` | Passed as the single local release gate for this PR state, including `qamap qa` coverage, the packaged PR QA skill template, and `dist/qa.*` pack output. |
-| `npm publish --dry-run --access public` | Passed for `@ivorycanvas/qamap@0.3.0`; tarball includes 98 files, `schema/qamap-manifest.schema.json`, `docs/manifest.md`, `docs/quickstart-demo.md`, `skills/qamap-pr-qa/SKILL.md`, and the demo GIF. |
+| `pnpm pack --dry-run` | Passed; tarball includes 97 files and no committed demo GIF. |
+| `npm publish --dry-run --access public` | Passed for `@ivorycanvas/qamap@0.3.1`; package size is 289.1 kB and includes the manifest schema, quick-start docs, release docs, and `skills/qamap-pr-qa/SKILL.md`. |
 
 ## Real Repository Smoke Snapshot
 
@@ -197,7 +210,7 @@ The same follow-up also showed the next quality gap. External manifest previews
 
 | Target shape | Base/head mode | Result | Follow-up signal |
 | --- | --- | --- | --- |
-| Expo / React Native manifest baseline | `manifest init` wrote only to `/tmp/qamap-mood-note-manifest.yaml` | Generated 9 domains, 8 flows, 8 anchors, and 16 checks without changing the target repo. Direct `app/*.tsx` screens now produce specific paths such as `app/EmotionChatPage.tsx`; `+not-found.tsx` is not promoted as a product domain. | Good 0.2.x signal for baseline quality. Remaining work is richer screen/route semantics and selector-specific checks. |
+| Expo / React Native manifest baseline | `manifest init` wrote only to `/tmp/qamap-journal-note-manifest.yaml` | Generated 9 domains, 8 flows, 8 anchors, and 16 checks without changing the target repo. Direct `app/*.tsx` screens now produce specific paths such as `app/SentimentChatPage.tsx`; `+not-found.tsx` is not promoted as a product domain. | Good 0.2.x signal for baseline quality. Remaining work is richer screen/route semantics and selector-specific checks. |
 | Web monorepo package | Package scan with `--workspace-root`, feature branch compared with `main`, working tree included | Detected `web`, recommended Playwright, inferred a concrete route, produced changed-flow specs, and correctly blocked promotion because Playwright config, deterministic fixture/mock data, selector evidence, and validation evidence were missing. | Flow naming improved, but docs/design-only files can still create low-signal drafts that should be filtered or demoted. |
 | Expo / React Native app | Feature branch compared with `develop`, working tree included | Detected `expo-react-native`, recommended Maestro, found an existing Jest suite, produced multiple near-runnable YAML drafts, and gave useful blockers for missing Maestro directory plus missing stable mobile selectors. | Strongest current real-repo result; remaining gap is selector and app-specific setup quality. |
 | Nuxt / Vue web app with existing Playwright tests | `origin/develop` to `HEAD`, working tree included | Detected `web`, recommended Playwright, recognized existing test evidence, and blocked draft promotion because no Playwright config or runnable route/screen entrypoint was inferred. | Test-only or generated-test changes can still produce generic smoke draft names; QAMap should better distinguish changed tests from changed product behavior. |

package/docs/releasing.md

@@ -65,9 +65,9 @@ npm publish --access public
 After publish, verify the public package can be executed without a source checkout:
 
 ```sh
-pnpm dlx @ivorycanvas/qamap@0.3.0 scan .
-pnpm dlx @ivorycanvas/qamap@0.3.0 manifest validate .
-pnpm dlx @ivorycanvas/qamap@0.3.0 e2e draft . --base origin/main --head HEAD --dry-run
+pnpm dlx @ivorycanvas/qamap@0.3.1 scan .
+pnpm dlx @ivorycanvas/qamap@0.3.1 manifest validate .
+pnpm dlx @ivorycanvas/qamap@0.3.1 e2e draft . --base origin/main --head HEAD --dry-run
 ```
 
 Use a fresh shell or temporary directory for the smoke check when possible.
@@ -77,8 +77,8 @@ Use a fresh shell or temporary directory for the smoke check when possible.
 After npm publish succeeds:
 
 ```sh
-git tag v0.3.0
-git push origin v0.3.0
+git tag v0.3.1
+git push origin v0.3.1
 ```
 
 Create a GitHub Release for the tag with:
@@ -93,13 +93,13 @@ Create a GitHub Release for the tag with:
 After the tag and GitHub Release are visible, run:
 
 ```sh
-pnpm dlx @ivorycanvas/qamap@0.3.0 --version
-pnpm dlx @ivorycanvas/qamap@0.3.0 scan .
-pnpm dlx @ivorycanvas/qamap@0.3.0 manifest explain . --base origin/main --head HEAD
-pnpm dlx @ivorycanvas/qamap@0.3.0 verify . --base origin/main --head HEAD
+pnpm dlx @ivorycanvas/qamap@0.3.1 --version
+pnpm dlx @ivorycanvas/qamap@0.3.1 scan .
+pnpm dlx @ivorycanvas/qamap@0.3.1 manifest explain . --base origin/main --head HEAD
+pnpm dlx @ivorycanvas/qamap@0.3.1 verify . --base origin/main --head HEAD
 ```
 
-Then update any public setup examples that should pin to `v0.3.0`.
+Then update any public setup examples that should pin to `v0.3.1`.
 
 ## Rollback Notes
 

package/docs/roadmap.md

@@ -45,7 +45,6 @@ Before treating the next public release as ready, the golden demo must satisfy t
 - Improve `doctor` output with clearer scoring and remediation grouping.
 - Improve `review` output for changed-line locations.
 - Expand manifest support with richer anchors, symbol-level matching, and configurable taste rubrics.
-- Match changed files to flows through a reverse import graph, not only declared anchor paths, so shared component and hook changes map to the flows that depend on them.
 - Map changed symbols to manifest anchors after the path/route baseline is stable.
 - Keep the `--format agent` output a stable, versioned contract that skills and MCP wrappers can rely on.
 - Add language-specific domain patterns for backend services, CLIs, libraries, mobile apps, and infrastructure repositories.

package/docs/verify.md

@@ -24,7 +24,7 @@ For custom stacks or team-specific flows, add `validationCommands` to `qamap.con
 ```sh
 qamap verify . --base origin/main --head HEAD --format markdown
 qamap verify . --base origin/main --head HEAD --pr-body-file pr-body.md
-qamap verify services/offer --workspace-root . --base origin/main --head HEAD --include-working-tree
+qamap verify services/listing --workspace-root . --base origin/main --head HEAD --include-working-tree
 ```
 
 Use `--fail-on high` or `--fail-on medium` to fail on QAMap review findings at or above a severity threshold. Readiness and manifest recommendations stay advisory until the team decides to make them required PR evidence.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ivorycanvas/qamap",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Local-first QA skill that turns PR diffs into affected flows, missing evidence, and E2E drafts with no cloud or LLM token.",
   "type": "module",
   "packageManager": "pnpm@10.32.1",
@@ -24,7 +24,8 @@
     "coverage": "pnpm build && node --test --experimental-test-coverage --test-coverage-include=\"dist/**/*.js\" --test-coverage-lines=80 --test-coverage-branches=80 --test-coverage-functions=80 test/*.test.mjs",
     "scan": "pnpm build && node dist/cli.js scan .",
     "report": "pnpm build && node dist/cli.js report . --output QAMAP_REPORT.md",
-    "release:check": "pnpm test && pnpm scan && git diff --check && pnpm run coverage && pnpm pack --dry-run"
+    "release:check": "pnpm test && pnpm scan && git diff --check && pnpm run coverage && pnpm pack --dry-run",
+    "bench": "pnpm build && node scripts/bench.mjs"
   },
   "keywords": [
     "ai",