@amg555/frameforge-mcp 2.7.6 → 2.7.7

package/.agent/skills/gstack-qa-only/SKILL.md.tmpl

@@ -1,214 +0,0 @@
----
-name: qa-only
-preamble-tier: 4
-version: 1.0.0
-description: |
-  Report browser/API/CLI/job/worker/webhook bugs. Produces a
-  structured report with contract evidence or browser scores and repro steps — but never
-  fixes anything. Use when asked to "just report bugs", "qa report only", or
-  "test but don't fix". For the full test-fix-verify loop, use /qa instead.
-  Proactively suggest when the user wants a bug report without any code changes. (gstack)
-voice-triggers:
-  - "bug report"
-  - "just check for bugs"
-allowed-tools:
-  - Bash
-  - Read
-  - Write
-  - AskUserQuestion
-  - WebSearch
-triggers:
-  - qa report only
-  - just report bugs
-  - test but dont fix
----
-
-{{PREAMBLE}}
-
-# /qa-only: Report-Only QA Testing
-
-Explore the selected surfaces and report reproducible behavior with evidence.
-**NEVER fix anything or change product tests.** Write only reports, evidence and
-owned temporary fixtures; the Additional Rules below define these limits.
-
-In shared sections, **caller** means this /qa-only workflow. The user sets its
-permissions; an invoking workflow may restrict them further. **Owned** means created
-for this run or explicitly assigned to it, not merely writable. Neither term permits repairs.
-
-{{SECTION_INDEX:qa-only}}
-
-Start at Request Parameters, then follow the sections below in order.
-
-## Request Parameters
-
-**Parse the user's request for these parameters:**
-
-| Parameter | Default | Override example |
-|-----------|---------|-----------------:|
-| Target | (infer from request/repository or ask) | Browser URL, API route, CLI command, job, worker or webhook |
-| Mode | full | `--quick`, `--regression <previous-report-or-baseline>` |
-| Output dir | `.gstack/qa-reports/` | `Output to /tmp/qa` |
-| Scope | Selected target (or diff-scoped) | `Focus on duplicate webhook delivery` |
-
-Use an isolated synthetic identity for functional probes. For browser sessions,
-follow Browser Setup; never request credentials in chat.
-
-Parsing records the request; it does not start browser setup. If both `--quick` and
-`--regression` are supplied, ask the user to choose one mode before setup or probes.
-
-**On a feature branch without an explicit scope:** Use diff-aware testing of changed
-and adjacent behavior. Do not discover a browser merely because no URL was supplied.
-
-## Test Plan Context
-
-Look for a test plan in this conversation. If this session already knows the
-project's state directory, also Read its newest `*-test-plan-*.md` when permitted.
-Do not create state or run bookkeeping helpers just to find optional context.
-Prefer the plan covering more requested contracts; break ties by recency.
-If neither exists, use git diff analysis.
-
-{{LEARNINGS_SEARCH}}
-
-## Select Surfaces and Isolation
-
-Load the shared preparation gate now (the exploratory STOP just below): complete its scope and selected-method Reads,
-await their results, and select the surfaces. Defer charters, clocks and probes to
-Run the Selected Checks; its §1 then reuses the REPORT_DIR resolved under Prepare Report Artifacts.
-
-{{SECTION:exploratory}}
-
-Each surface's method defines Full, Quick and Regression. A mode flag applies to all
-selected surfaces unless the request names one surface; the others default to Full.
-For mixed Regression, the argument is the prior combined report. Resolve its functional
-replay evidence and browser baseline links first, then give each method its own baseline.
-A missing baseline blocks that surface's regression coverage, not independent checks.
-In mixed runs, use the user's surface order, defaulting to functional then browser.
-Each surface's clock starts with its probes; finish one surface before starting the
-next. A supplied absolute deadline is shared; switching surfaces does not extend it.
-
-## Prepare Report Artifacts
-
-Resolve and preserve supplied prior report/baseline paths and their evidence links
-before writing. Select the requested output dir or `.gstack/qa-reports`; create it if absent.
-Use that directory as `REPORT_DIR` only when it is empty; otherwise choose a fresh owned run subdirectory.
-Use `run-YYYYMMDDTHHMMSSZ` in UTC, adding a suffix on collision.
-All local reports, baselines and evidence use this directory.
-Never overwrite artifacts from earlier runs. Preserve this run's baselines,
-screenshots and exploration notes when finalizing its report.
-
-A caller's fixed artifact paths and permissions take precedence. An existing empty
-directory already established as owned by the caller needs no new shell commands
-to revalidate it; use the caller's supported interface and fixed destinations.
-If safe preservation is impossible within those permissions, report an output blocker;
-do not expand write authority or silently redirect required artifacts.
-
-For `{target}`, use the browser hostname, CLI executable basename, or named
-API service/job/worker/webhook. Replace characters other than letters, digits and
-hyphens with hyphens. For mixed targets, use
-`mixed-{project-label}`, sanitizing the repository name the same way; use `mixed-target`
-when no repository name is available. List the individual targets in the report.
-
-Set `REPORT_FILE` to the caller's final report filename, otherwise
-`$REPORT_DIR/qa-report-{target}-{YYYY-MM-DD}.md`. Charters and final findings use this
-same file, not a sidecar.
-
-## Browser Setup (conditional)
-
-**Browser surface only:** load its setup; functional-only runs skip this section.
-
-{{QA_RESOURCE:browser-setup}}
-
----
-
-## Run the Selected Checks
-
-Use the shared section already loaded above; do not restart its preparation.
-With its required Reads complete and report ownership resolved, Write the charters
-into the owned report and wait for the successful
-Write result before starting any probe clock or baseline. Use `REPORT_FILE`. State each expected result,
-risk, entrypoint, isolation and exit condition before probing; never invent the plan later.
-A failed baseline contract stays failed. Before browser probes, source/diff reads only
-map changes to pages and flows; read `TODOS.md` if present to identify known bugs.
-During browser discovery, observe behavior without reading source to diagnose it.
-
----
-
-## Output
-
-### Assemble the report
-
-After probing stops, load the finalization procedure below. Order: exploratory §4 annotations and materialize, then this procedure, then the final report Write. Use retained evidence;
-this step does not authorize more probes or restart an expired clock.
-Do not preload reporting. To recover from an accidental early Read:
-If already read, issue another Read now and await its
-acknowledgement, even if the tool reports unchanged content.
-The no-repeat rule covers preparation Reads, not this finalization Read.
-
-{{SECTION:reporting}}
-
-Use templates from this host's installed QA directory. For mixed runs, use separate browser and functional sections in this same report.
-Keep common metadata once: date, branch/revision, caller/authority, mode, scope and timing/stop reason.
-Preserve the initial charters under **Charters** after that metadata, before findings.
-
-- **Browser:** `templates/qa-report-template.md`: targets, URL, framework,
-  page/screenshot counts, findings, health/category scores and regression comparison.
-- **Functional:** `templates/functional-report-template.md`: native tools/runtime,
-  fixture ownership, contracts, findings, discoveries/proposed tests and cleanup.
-
-Each proposed test carries a value card; propose it only when it passes this bar:
-
-{{TEST_VALUE_BAR:qa}}
-
-Nest remaining headings per surface, without duplicating the shared title or metadata.
-Preserve surface-specific scope, timing and coverage limits.
-Browser scores apply only to browser coverage; never combine them with functional
-outcomes. In each section link the current baseline or replay evidence and checkpoints;
-for functional regression the report plus replay evidence is the baseline. Regression
-also links the prior input baseline/report; missing required replay inputs block affected
-coverage. Prior baselines are not applicable to Full/Quick. Report-only
-repair/test fields contain proposals or not-run status, never claims of edits.
-
-### Write the checked report
-
-After the reporting procedure's consistency check, write `REPORT_FILE` and the
-project copy below. These are the default report destinations; a caller's narrower
-permissions or fixed paths override them. Do not create a forbidden second copy.
-
-Use this session's existing project slug and state directory for the project copy.
-If unknown or not writable within the supplied permissions, report that copy as
-blocked; still write the permitted local report. Do not run state-setup helpers.
-Write identical content to `$GSTACK_STATE_ROOT/projects/{slug}/{user}-{branch}-test-outcome-{datetime}.md` (the state root this session resolved).
-Get `{user}`/`{branch}` from `git config user.name`/`git branch --show-current`
-(fallbacks: `unknown-user`/`detached`); sanitize like `{target}`. Use UTC `YYYYMMDDTHHMMSSZ`.
-If that destination exists, choose a fresh suffixed filename; never replace a prior report.
-
-### Output Structure
-
-`REPORT_DIR` stays the report root throughout the run. For browser-only and mixed
-runs, keep screenshots in `$REPORT_DIR/screenshots/` and the browser baseline in
-`$REPORT_DIR/baseline.json`.
-The shared loop's mixed-surface split applies only to clocks and checkpoints:
-
-| Run | Clock/checkpoint directory |
-|-----|----------------------------|
-| One surface (browser or functional) | `$REPORT_DIR` |
-| Mixed: browser probes | `$REPORT_DIR/browser` |
-| Mixed: functional probes | `$REPORT_DIR/functional` |
-
-Each probe directory holds its own `exploration-NNN.json` sequence, `annotations.json`
-and materialize step, and, only when timed, `deadline.json`. Caller-fixed paths override this layout. Do not reassign
-`REPORT_DIR` to a surface directory or move the shared browser artifact paths.
-
-## Additional Rules (qa-only specific)
-
-1. **Never fix bugs or write product tests.** Find and document only. Necessary read-only
-    source discovery is allowed for functional targets, while browser discovery stays
-    black-box. Do not edit product code, tests, dependencies, config or tracked state
-    through any tool, including shell writes, renames, deletions and edit-then-restore.
-    Never commit, stash or bootstrap. Proposed regressions belong in report artifacts.
-2. **During preflight, check documented native commands and test infrastructure.** For browser targets, inspect documentation only for this framework check, before discovery. If absent,
-    report missing coverage and proposed cases without installing anything. An unavailable
-    command/service is not a product defect. Never invoke /qa or another skill from this report-only run.
-    When the browser app's repository is available and no framework is documented, say
-    "No test framework detected. Run `/qa` to bootstrap in a separate, user-authorized repair session."
-    Functional targets keep the gap without a new framework.

package/.agent/skills/gstack-qa-only/sections/exploratory.md

@@ -1,107 +0,0 @@
-<!-- AUTO-GENERATED from exploratory.md.tmpl — do not edit directly -->
-<!-- Regenerate: bun run gen:skill-docs -->
-# Shared exploratory QA
-
-The **caller** (/qa, /qa-only, /review or /ship) owns decisions, tests, fixes and publication. Discovery writes only reports/evidence
-and owned fixture state; no workflows, framework installs or publication.
-
-## 0. Preparation gate
-
-Complete these Reads in order before writing charters or probing:
-1. Read `sections/scope.md` relative to the installed `qa`/`gstack-qa` SKILL.md directory in full and select the surfaces.
-2. Read the selected surface methods below in full.
-
-Use this host's installed `qa`/`gstack-qa` SKILL.md directory for these reads:
-
-**Functional surfaces:**
-Read `sections/system-functional.md` in full.
-
-**Browser surfaces only:**
-Read `sections/qa-patterns.md` in full.
-
-Await each successful Read result before continuing. A supplied target, isolation
-description, section index or remembered method is not a completed instruction Read.
-Do not repeat a Read already completed in this invocation; reuse only its acknowledged
-full contents. If either required Read is missing, complete it now before Charter and preflight.
-Missing or unreadable assets, prerequisites or permission block affected probes, not independent safe checks. Report QA setup blockers.
-
-## 1. Charter and preflight
-
-Reuse resolved REPORT_DIR; otherwise own a fresh `.gstack/qa-reports` subdirectory.
-Write a **charter** per behavior: contract, risk, entrypoint, isolation, exit condition, source, commands and inputs. Save charters as Markdown in the report.
-
-
-For /qa and /qa-only:
-- Browser Quick: SECONDS=180. Browser Full/Regression: SECONDS=900.
-- Functional Full, Quick and Regression have no default total timer.
-Set SECONDS to the shorter mode/caller limit; an unlimited mode uses the caller's bound.
-Without a total time limit, do not create DEADLINE_FILE; announce finite command timeouts.
-Stop when scoped contracts are tested or blocked.
-Clocks/checkpoints use REPORT_DIR; mixed standalone runs use REPORT_DIR/browser and REPORT_DIR/functional, with one final report at REPORT_DIR. Caller paths win.
-Names used below (quote every path):
-- PROBE_DIR: this surface's owned probe directory per the line above. DEADLINE_FILE: `PROBE_DIR/deadline.json`, which exists only for a bounded run.
-- SECONDS: the total probe budget set above. NNN: a fresh three-digit ID (001, 002, ...) for each capture or checkpoint; never reuse one.
-- DEADLINE_TOOL = `$HOME/.claude/skills/gstack/bin/gstack-qa-deadline`, the deadline guard: `start` creates DEADLINE_FILE, `status` prints `remainingMs` and `expired`, and `run` executes one command, stopping it at the deadline.
-- EVIDENCE_TOOL = `$HOME/.claude/skills/gstack/bin/gstack-qa-evidence`, the functional evidence recorder: `capture` runs one command, stores its exit code, stdout and stderr under `PROBE_DIR/.qa-evidence/NNN/`, and prints status `complete`, `incomplete` or `sensitive`.
-
-Start once before baseline: `bun DEADLINE_TOOL start DEADLINE_FILE SECONDS [EARLIER_UTC]` if bounded.
-EARLIER_UTC = caller's absolute deadline, if set.
-Functional: `bun EVIDENCE_TOOL capture PROBE_DIR NNN [--public] --deadline DEADLINE_FILE -- COMMAND ARGS`.
-Unbounded: use `--timeout-ms MS` instead of `--deadline DEADLINE_FILE`.
---public requires approved public/synthetic output; EVIDENCE_TOOL screens credentials. For complete private captures, await a safe Read of `PROBE_DIR/.qa-evidence/NNN/observation.json` (the decoded stdout). Sensitive/incomplete captures cannot anchor checkpoints.
-Bounded browsers: `bun DEADLINE_TOOL run DEADLINE_FILE -- COMMAND ARGS`. No detached probes.
-Never reset DEADLINE_FILE/bypass DEADLINE_TOOL. Expiry or an invalid/missing DEADLINE_FILE stops probes; report unfinished coverage. QA_DEADLINE receipts are not observations.
-
-## 2. Probe loop
-
-Each probe is one native command/interaction plus checks, excluding bookkeeping.
-Never batch probes.
-
-1. First demonstrate success: output AND durable effects. Guard if bounded; await completion.
-2. **Decide whether another probe is needed.** If bounded, run `bun DEADLINE_TOOL status DEADLINE_FILE`.
-   If expired or no safe next probe remains, STOP exploration; write the report (§4), not a checkpoint.
-   **Classify the last result before copying it.** For public or synthetic observations,
-   retain the entire result unchanged, including owned fixture paths, IDs, hashes and
-   existing credential placeholders. An absolute state path is not itself a secret.
-   For actual secrets/private payloads, withhold those values and disclose the redaction
-   and replay limits in the report. If no safe exact observation can be retained,
-   stop the affected probe chain; never invent a substitute path, identity or state.
-   **Publish before probing.** Create (browser) or compose (functional) `exploration-NNN.json` in the probe directory, beside its deadline if bounded, with exactly four top-level fields:
-   observationCommand: last completed probe's full outer command, including guard.
-   observed: its exact decoded child JSON (no wrapper/extra keys), or its full non-JSON text.
-   For guarded text, copy the complete span between the guard's started and finished receipt lines.
-   Keep its whitespace and content fences verbatim. Do not summarize, relabel or add timing text.
-   The guard adds one newline before its finished receipt; that separator is not child text.
-   For unguarded text, copy the complete result instead.
-   If capture is incomplete, report that limit instead of reconstructing it.
-   hypothesis: why nextCommand. nextCommand: exact command/request, guarded if bounded.
-   Preserve every safe program-JSON key/value and identity hash unchanged.
-   Withhold unsafe values, disclose limits and stop that chain.
-   Check fields before publication. No drafts/placeholders or invented safe-path redactions; corrections cannot repair published notes.
-   Functional: do not write this file; the next capture publishes it: `bun EVIDENCE_TOOL capture PROBE_DIR NNN --deadline DEADLINE_FILE --after PREV --hypothesis 'why' -- CMD` (PREV: the last complete capture's ID). EVIDENCE_TOOL supplies observed; never transcribe it.
-   Browser checkpoints use Write.
-   Wait for successful checkpoint publication before dispatch.
-   Never backfill or overwrite notes.
-3. Run that exact probe; DEADLINE_TOOL enforces the deadline when bounded.
-   Report refusals as not-run; retain initial state/inputs/results. Repeat from step 2.
-4. Replay the exact failing command/request from the same initial fixture state via steps 2–3 (same native command, fresh capture ID)
-   to confirm it, then minimize via those gates. Expiry leaves confirmation/minimization incomplete.
-   Another input or a regression test is not that replay.
-5. If the user or another process changes source, commands or fixtures, review the affected
-   contracts and return to step 2 for each affected revalidation (unproven=affected). Do not make product changes yourself.
-   Keep the original limits/notes; update outcomes only from fresh evidence.
-
-## 3. Parent handoff
-
-Never change product code, tests, configuration, dependencies or Git through any tool,
-including shell, rename, deletion, commit, stash or edit-then-restore. Return test_stub proposals
-with their failing contract and expected assertion; never create tests or freeze buggy output.
-
-## 4. Final report
-
-Use the surface report template; link each checkpoint. Separate browser scores, functional outcomes and proposed/executed tests.
-Write PROBE_DIR/annotations.json {evidence: [{capture, command, contract, expected, classification}], limits: ["checkpoint 001"]} (limits: non-empty string array, not an object; browser-only: evidence []); before Markdown `bun EVIDENCE_TOOL materialize PROBE_DIR annotations.json` (fills observed/metadata; prints reportLinks; runs once per PROBE_DIR); you classify. Annotate every safe capture, including failures/replays: an omitted capture is withheld and keeps the verdict inconclusive. Classify a capture taken before an input change `superseded`; it closes when the same command reran on current inputs. Disclose withheld/incomplete evidence.
-Evidence is invocation-local.
-Missing prerequisites/expectations/observations, timeouts and refusal never pass.
-Pass requires all required current-input contracts to pass with no required remainder.
-Report blocked, inconclusive and not-run coverage without claiming success.

package/.agent/skills/gstack-qa-only/sections/exploratory.md.tmpl

@@ -1 +0,0 @@
-{{QA_EXPLORATORY}}

package/.agent/skills/gstack-qa-only/sections/manifest.json

@@ -1,19 +0,0 @@
-{
-  "$schema": "https://gstack.dev/schemas/section-manifest.json",
-  "skill": "qa-only",
-  "version": 1,
-  "sections": [
-    {
-      "id": "exploratory",
-      "file": "exploratory.md",
-      "title": "Report-only exploratory QA",
-      "trigger": "selecting surfaces, then running report-only probes (one Read covers both)"
-    },
-    {
-      "id": "reporting",
-      "file": "reporting.md",
-      "title": "Evidence-grounded report finalization",
-      "trigger": "finalizing the report after probing stops"
-    }
-  ]
-}

package/.agent/skills/gstack-qa-only/sections/reporting.md

@@ -1,78 +0,0 @@
-<!-- AUTO-GENERATED from reporting.md.tmpl — do not edit directly -->
-<!-- Regenerate: bun run gen:skill-docs -->
-# Finalize a report from retained evidence
-
-Complete these steps before the final report Write. They use retained results, not
-new probes. Missing evidence stays unknown; an expired clock stays expired.
-The caller's write boundary includes reports, learning notes and automatic memory.
-Keep all of them in authorized destinations; a memory feature grants no extra path.
-
-## 1. Establish each finding once
-
-Ground the report and learnings in retained observations. For every finding, distinguish
-the observed result, the expected contract and any untested causal hypothesis. Link the
-supporting command/result or screenshot; unknown impact remains unknown. A console error
-message does not establish an uncaught exception, failed payload or missing UI. Missing
-text in a page-text extract does not establish an absent attribute or inaccessible element.
-Verify those claims with an appropriate probe, or leave them unconfirmed when time expires.
-
-Give each finding one ID and write its Observed, Expected, Evidence and Confirmation
-fields first. A logged exception-shaped string proves a logged message, not that the
-named operation executed. Keep possible causes in a separate Hypothesis field; omit
-speculation that does not help the next investigation. Observed-once is not replay-confirmed.
-
-## 2. Fill timing fields from their actual boundaries
-
-Report **Probe budget** (configured limit) and **Guarded command time** (sum of measured
-child spans). Measure guard start to child launch as pre-launch elapsed time, and child
-start to finish as command duration, not a component's latency without its own measurement.
-A deadline window is not total run time. Gaps between receipts do not measure
-status/Write overhead or prove how many probes fit; if late, say only that this run
-dispatched its follow-up after the deadline.
-
-Use **Total session elapsed**: `unmeasured` for the invocation whose report is being written.
-Its final report Write, acknowledgement and cleanup are not finished yet. Do not fetch
-a clock merely to fill that field. An optional **Measured interval** must cite its actual
-start/end receipts and name the work outside those boundaries, including later report
-Writes and cleanup; it is never a completed-session measurement.
-
-## 3. Assemble and check every repetition before writing
-
-Use the caller's selected surface templates and assembly rules. Build headlines,
-Top 3, summaries and completion text from each finding's Observed and Confirmation
-fields, not its Hypothesis. Choose one conservative factual sentence per finding and
-reuse it verbatim in those locations; do not introduce a new causal paraphrase.
-A disclaimer in the detail does not qualify a stronger claim elsewhere.
-
-Proposed regression assertions must detect the original observation on its actual
-channel. For a logged console error, capture console errors; exception-only hooks
-do not detect a console-only message. Additional causal tests remain separate proposals.
-Apply these evidence limits to proposed tests and learnings too.
-
-Before the final Write, check every mention of each finding against its evidence
-fields, every proposed test against the observed channel, and each timing claim against
-its named boundaries. Remove unsupported claims from all sections, not only the detail.
-Keep refused/unstarted probes and untested categories explicit. Write the report only
-after this consistency check; do not repair an evidence gap with invented facts.
-Check claims about frequency and executed checks against the actual commands/results:
-one observation proves neither recurrence nor an unexecuted check. Apply the same
-evidence limits to the final response and any caller-authorized learning note.
-
-## 4. Capture permitted notes, then write the report
-
-Run the learning step below only if its destination is caller-authorized:
-the user or invoking workflow explicitly permitted that learning-store path.
-Invoking /qa-only alone does not grant this permission. Otherwise
-keep notes in `REPORT_FILE`; do not write learning stores or automatic memory.
-
-**No explicit permission:** skip learning-store writes and continue to the report.
-
-**Explicit permission:** Read the named store first. Preserve its existing contents
-and use the permitted write tool to append a verified note in that store's format.
-If the format or write interface is unavailable, keep the note in the report instead.
-Do not run logging helpers: they may write caches or enqueue synchronization outside
-the permitted path. This branch never changes configuration or enables synchronization.
-
-Write the checked report to the entrypoint's permitted destinations.
-After the final Write, respond briefly with its path and verified coverage/limits;
-do not append new findings or timing explanations.

package/.agent/skills/gstack-qa-only/sections/reporting.md.tmpl

@@ -1,76 +0,0 @@
-# Finalize a report from retained evidence
-
-Complete these steps before the final report Write. They use retained results, not
-new probes. Missing evidence stays unknown; an expired clock stays expired.
-The caller's write boundary includes reports, learning notes and automatic memory.
-Keep all of them in authorized destinations; a memory feature grants no extra path.
-
-## 1. Establish each finding once
-
-Ground the report and learnings in retained observations. For every finding, distinguish
-the observed result, the expected contract and any untested causal hypothesis. Link the
-supporting command/result or screenshot; unknown impact remains unknown. A console error
-message does not establish an uncaught exception, failed payload or missing UI. Missing
-text in a page-text extract does not establish an absent attribute or inaccessible element.
-Verify those claims with an appropriate probe, or leave them unconfirmed when time expires.
-
-Give each finding one ID and write its Observed, Expected, Evidence and Confirmation
-fields first. A logged exception-shaped string proves a logged message, not that the
-named operation executed. Keep possible causes in a separate Hypothesis field; omit
-speculation that does not help the next investigation. Observed-once is not replay-confirmed.
-
-## 2. Fill timing fields from their actual boundaries
-
-Report **Probe budget** (configured limit) and **Guarded command time** (sum of measured
-child spans). Measure guard start to child launch as pre-launch elapsed time, and child
-start to finish as command duration, not a component's latency without its own measurement.
-A deadline window is not total run time. Gaps between receipts do not measure
-status/Write overhead or prove how many probes fit; if late, say only that this run
-dispatched its follow-up after the deadline.
-
-Use **Total session elapsed**: `unmeasured` for the invocation whose report is being written.
-Its final report Write, acknowledgement and cleanup are not finished yet. Do not fetch
-a clock merely to fill that field. An optional **Measured interval** must cite its actual
-start/end receipts and name the work outside those boundaries, including later report
-Writes and cleanup; it is never a completed-session measurement.
-
-## 3. Assemble and check every repetition before writing
-
-Use the caller's selected surface templates and assembly rules. Build headlines,
-Top 3, summaries and completion text from each finding's Observed and Confirmation
-fields, not its Hypothesis. Choose one conservative factual sentence per finding and
-reuse it verbatim in those locations; do not introduce a new causal paraphrase.
-A disclaimer in the detail does not qualify a stronger claim elsewhere.
-
-Proposed regression assertions must detect the original observation on its actual
-channel. For a logged console error, capture console errors; exception-only hooks
-do not detect a console-only message. Additional causal tests remain separate proposals.
-Apply these evidence limits to proposed tests and learnings too.
-
-Before the final Write, check every mention of each finding against its evidence
-fields, every proposed test against the observed channel, and each timing claim against
-its named boundaries. Remove unsupported claims from all sections, not only the detail.
-Keep refused/unstarted probes and untested categories explicit. Write the report only
-after this consistency check; do not repair an evidence gap with invented facts.
-Check claims about frequency and executed checks against the actual commands/results:
-one observation proves neither recurrence nor an unexecuted check. Apply the same
-evidence limits to the final response and any caller-authorized learning note.
-
-## 4. Capture permitted notes, then write the report
-
-Run the learning step below only if its destination is caller-authorized:
-the user or invoking workflow explicitly permitted that learning-store path.
-Invoking /qa-only alone does not grant this permission. Otherwise
-keep notes in `REPORT_FILE`; do not write learning stores or automatic memory.
-
-**No explicit permission:** skip learning-store writes and continue to the report.
-
-**Explicit permission:** Read the named store first. Preserve its existing contents
-and use the permitted write tool to append a verified note in that store's format.
-If the format or write interface is unavailable, keep the note in the report instead.
-Do not run logging helpers: they may write caches or enqueue synchronization outside
-the permitted path. This branch never changes configuration or enables synchronization.
-
-Write the checked report to the entrypoint's permitted destinations.
-After the final Write, respond briefly with its path and verified coverage/limits;
-do not append new findings or timing explanations.