Regenerate generated output for the qa checkpoint wording

qa-only/sections/exploratory.md

@@ -69,7 +69,7 @@ How one probe works: (1) if bounded, check the clock and choose the next command
    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 `exploration-NNN.json` in the probe directory, beside its deadline if bounded, with exactly four top-level fields:
+   **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.
@@ -82,7 +82,7 @@ How one probe works: (1) if bounded, check the clock and choose the next command
    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: create the four-field file yourself.
+   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.

qa/sections/exploratory.md

@@ -57,7 +57,7 @@ How one probe works: (1) if bounded, check the clock and choose the next command
 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, not a checkpoint.
-   **Publish before probing.** Create `exploration-NNN.json` in the probe directory, beside its deadline if bounded, with exactly four top-level fields:
+   **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.
    hypothesis: why nextCommand. nextCommand: exact command/request, guarded if bounded.
@@ -65,7 +65,7 @@ How one probe works: (1) if bounded, check the clock and choose the next command
    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: create the four-field file yourself.
+   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.