M2-08: Add Monad live smoke and provenance record

Type: Live Integration Test
Priority: P0
Initial status: Blocked
Owner: Moss Integration + QA
Depends on: M2-03 through M2-07
Blocks: M2-13, Gate A
Writable: adapter live tests, scripts/smoke/**, docs/live-smoke.md,
          secret-safe artifact metadata

唯一目标

在 Monad chain ID 143 证明至少一个真实 quote -> action -> simulate 链路，并准确报告成功、Warning、UNPROVABLE 或 STOP。

协议 fallback

#138 upstream merge 是加分项，不是依赖
未合并时可携带 reviewed exact patch 到 integration fork
Kuru Receipt 不稳定时，PancakeSwap V2 成为 P0 live happy path
Kuru 可作为 secondary Quote/Warning/STOP evidence
第二协议是第一 Scope Cut

验收

[ ] network=eip155:143
[ ] Moss build info/patch digest 输出，无 RPC secret
[ ] 至少一个真实 Quote 成功
[ ] Capability 存在且 kind/shape assertion 通过
[ ] simulation result count >= 1
[ ] Warning count 显式
[ ] exact block number/hash 及调用 block 参数被证明
[ ] unprovable context 进入 explicit failed evidence/STOP
[ ] live failure 非零退出或显式失败，不切 Fixture
[ ] offline suite 不依赖网络
[ ] 仅真实 live artifact 标 LIVE_SOURCE

验证

MOSS_RPC_URL=https://rpc.monad.xyz pnpm --filter @moss-mini-demo/moss-adapter test:live
pnpm check

PR 附日期、head SHA、Moss build info、patch digest、RPC host、block number/hash、Quote/Warning count 和结果。

Codex 指令

运行一次 secret-safe Monad live smoke。失败也要保留真实证据并准确分类；
不允许自动 Fixture fallback。没有可靠 Kuru happy path 时按合同切换 PancakeSwap V2。

DEPENDENCY_GATE_CLEARED

Issue #29 depends on M2-03 through M2-07. Every required dependency is now Closed / Project Done and its squash commit is contained in current main@95c4aac532cdc2231054c431f3a175f9c223e1f5:

M2-03: Pin reproducible Moss dependency #24 / PR chore: pin reproducible Moss dependency #70: 93235e5c3ef531075c860beadc6ad2ce6b3dc8a0; merged-main quality-gate SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30975163159; audit: M2-03: Pin reproducible Moss dependency #24 (comment)
M2-04: Create moss-adapter package and public ports #25 / PR feat: add Moss adapter ports #72: a0f3a3e8605812c9f0997059b4a30ea7a736022c; merged-main quality-gate SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31070657110
M2-05: Implement quote collection and deterministic selection #26 / PR feat: collect and deterministically select quotes #73: 65753ada85156716e263b660eeab72c42d293431; merged-main quality-gate SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31106530067; audit: M2-05: Implement quote collection and deterministic selection #26 (comment)
M2-06: Implement capability construction, amount conversion and integrity #27 / PR feat: construct synthetic Capability integrity evidence #74: b3ba1411ce521d0d8526ae5805a162f5167f1e3c; merged-main quality-gate SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31142962224
M2-07: Implement simulation and lossless evidence mapping #28 / PR M2-07: map lossless Moss simulation evidence #75: e468c6c035c3c35e12a0c1d7795d76d5306045eb; merged-main quality-gate SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31235869098; audit: M2-07: Implement simulation and lossless evidence mapping #28 (comment)

The dependency gate is therefore cleared. Issue #29 may enter planning from this exact main baseline.

Ready/In Progress means planning authority only. It is not SCOPE_CONFIRMED, implementation authorization, SINGLE_OPERATOR_QA PASS, Maintainer Review, READY_TO_MERGE, Merge Gate, or merge authorization. A closed path-specific Work Plan and a separate Maintainer Scope Gate remain mandatory before any implementation branch, worktree, file change, commit, push, or PR.

M2_EXECUTION_SLOT_ASSIGNED

Builder: pillowtalk-Qy

Planning baseline: origin/main@95c4aac532cdc2231054c431f3a175f9c223e1f5

Dependency gate: #29 (comment)

Issue #29 is now the single active Builder slot and moves to Project In Progress for planning.

Planned branch after scope confirmation: codex/issue-29-monad-live-smoke

Planned isolated worktree after authorization: /Users/qy/Documents/moss-mini-demo-issue-29

The first required artifact is a closed Work Plan covering the exact writable paths, pinned Moss build and patch identity, public-RPC secret boundary, real quote/action/simulation sequence, exact block provenance, explicit warning and UNPROVABLE/STOP behavior, nonzero failure behavior, offline test isolation, and the prohibition on Fixture evidence or transaction submission.

In Progress starts planning only. It is not SCOPE_CONFIRMED, implementation authorization, SINGLE_OPERATOR_QA PASS, Review, READY_TO_MERGE, Merge Gate, or merge authorization. No branch, worktree, code change, commit, push, or PR may be created before the separate Scope Gate.

Final Implementation Work Plan - M2-08 Monad Live Smoke and Provenance Record

0. Status and frozen baseline

This is a planning artifact for Issue #29 only. It requests a separate Maintainer Scope Gate and does not itself authorize implementation.

baseline: origin/main@95c4aac532cdc2231054c431f3a175f9c223e1f5
dependency gate: M2-08: Add Monad live smoke and provenance record #29 (comment)
proposed branch after authorization: codex/issue-29-monad-live-smoke
proposed isolated worktree after authorization: /Users/qy/Documents/moss-mini-demo-issue-29
pinned Moss gitlink: vendor/moss@1ae6b6322d51fae9104f047efb94e601050b967f

No branch, worktree, file change, commit, push, PR, live call, or artifact is authorized until an explicit SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED record accepts this exact plan.

1. Goal and authority boundary

Add one explicitly invoked Monad mainnet smoke that proves a real pinned-Moss PancakeSwap V2 quote -> action -> simulate sequence on eip155:143, and emits a small secret-safe provenance artifact. The smoke never submits, signs, broadcasts, approves, or persists a transaction and never claims that successful simulation is safety or execution authorization.

The P0 path is PancakeSwap V2, as allowed by Issue #29's protocol fallback. Kuru and a second protocol are scope-cut. The already merged upstream PR #138 behavior is present in the exact pinned Moss commit; no patch or Moss source change is needed.

2. Exact writable paths

The implementation may modify exactly these five paths:

packages/moss-adapter/package.json
packages/moss-adapter/test/live/artifact.mjs
packages/moss-adapter/test/live/artifact.test.mjs
packages/moss-adapter/test/live/live-smoke.mjs
docs/live-smoke.md

No other path may change. In particular there is no root package.json, lockfile, workflow, .gitmodules, vendor gitlink/source, adapter source/public export, Web/API, fixture, governance, permission, branch-protection, or deployment change. No dependency is added.

3. Invocation and isolation

packages/moss-adapter/package.json adds only:

test:live = pnpm build && node --conditions=react-server test/live/live-smoke.mjs

The command remains excluded from pnpm check, ordinary tests, package-import smoke, and CI. Offline tests import only artifact.mjs; they do not import vendor Moss, read MOSS_RPC_URL, perform DNS, open sockets, or use chain fixtures.

The live command requires the exact submodule to be initialized, dependencies installed inside it, and the pinned vendor packages built. Missing/deinitialized/wrong-commit/unbuilt vendor state fails explicitly and nonzero without changing the checkout.

4. Pinned Moss composition

The runner imports built package entry files only from the exact checked-out vendor/moss tree:

@themoss/core for createRuntime, Registry, and NATIVE;
@themoss/protocol-pancakeswap for the registered PancakeSwap V2 protocol;
@themoss/simulator for createTraceSimulator;
@themoss/system for the pinned USDC address.

It also imports the built @moss-mini-demo/moss-adapter entry and creates createProductionMossPort bindings around those pinned Moss values. It verifies the gitlink/head and MOSS_BUILD_INFO identity before a successful artifact can be emitted.

5. Fixed live sequence

The smoke uses a fixed non-secret synthetic caller address and no private key. It performs:

create a runtime from MOSS_RPC_URL and require chain ID 143;
register the pinned PancakeSwap module;
load the pancakeswap-v2.quote and pancakeswap-v2.swap Stub contracts;
call the adapter's production quote with NATIVE -> USDC and a fixed amount;
call the adapter's production action with the same intent and bounded slippage;
require a Capability-shaped result with at least one transaction node;
pass the exact action-return object to the adapter's simulate method;
run the pinned trace simulator through the adapter-supplied recording RPC client so exact block parameters and block hashes are observed by the merged M2-07: Implement simulation and lossless evidence mapping #28 evidence mapper.

The simulation binding forwards only the supplied recording client's request method. It does not bypass the adapter's block observation, capability integrity, coverage, ordering, or continuity mapping.

6. Artifact contract and provenance

Exactly one final JSON artifact is written to stdout. It contains only allowlisted metadata:

schema version and UTC observation time;
result classification and mandatory STOP boolean;
network: eip155:143;
current Mini-Demo head;
exact MOSS_BUILD_INFO, including integration commit and patchset digest;
RPC scheme and host only;
fixed protocol/method names;
quote success count;
Capability kind, capability-node count, and transaction-node count;
simulation result count, warning count, halted/reverted indicators;
the mapped verification statuses;
exact observed block number/hash when PROVEN;
exact debug_traceCall / eth_estimateGas block parameters;
explicit block failure reasons when UNPROVABLE.

The raw RPC URL, username/password, path, query, fragment, headers, cookies, environment values, Quote body, Capability params/transactions, receipt/change bodies, raw warning messages, exception message, and stack are never emitted.

provenance: LIVE_SOURCE is permitted only after chain ID 143 and the real quote, action, and simulation calls have all returned and the artifact has at least one simulation result. Failures before that use NOT_ESTABLISHED, never Fixture or LIVE_SOURCE.

7. Result and STOP semantics

SUCCESS: quote succeeded, Capability is structurally present, result count is at least one, no warnings/halt/revert exist, block provenance is PROVEN, and integrity/coverage/ordering/continuity are not failed or unprovable; exit 0 and stop: false.
WARNING_STOP: one or more mapped warnings, halt, or revert exist; exit nonzero and stop: true.
UNPROVABLE_STOP: exact block provenance or another required verification is UNPROVABLE; include reason codes, exit nonzero, and stop: true.
FAILED_STOP: configuration, pin, chain, quote, action, Capability, simulation, timeout, or artifact validation failed; include only a stable allowlisted stage/code, use NOT_ESTABLISHED, exit nonzero, and stop: true.

No classification means approved, safe, executable, signable, or authorized.

8. Secret boundary

artifact.mjs owns URL reduction, classification, success/failure artifact construction, and recursive output validation. URL parsing accepts only HTTP(S), rejects credentials, and returns only normalized scheme/host. Artifact validation rejects secret-bearing keys, forbidden provenance, non-allowlisted failure detail, and any occurrence of the full configured RPC URL.

The runner catches every failure and maps it to a stable stage/code. It never serializes a source exception. The documentation requires users to treat MOSS_RPC_URL as a secret even when using the public endpoint and prohibits pasting raw request/response logs.

9. Offline tests

artifact.test.mjs is discovered by the existing root Vitest run and covers, without network:

public and credential-bearing URLs reduce to scheme/host only;
path/query/fragment/userinfo and secret sentinels never survive serialization;
invalid schemes, credentials, malformed URLs, forbidden keys, Fixture provenance, and raw-URL leakage fail closed;
the four result classifications and exit semantics;
SUCCESS requires LIVE_SOURCE, chain 143, quote success, Capability/transaction presence, result count, no warning/halt/revert, and PROVEN block evidence;
warnings, halt/revert, UNPROVABLE statuses, and zero results force STOP;
failure artifacts contain only stable stage/code and never exception text;
exact block number/hash and recorded call block parameters are preserved in allowed metadata.

10. Documentation

docs/live-smoke.md records Node/pnpm versions, exact pin/build prerequisites, the explicit command, artifact fields, classifications, evidence limitations, secret handling, nonzero STOP behavior, and the prohibition on treating the smoke as signing/transaction authorization. It names PancakeSwap V2 as the sole P0 live path and Kuru as out of scope.

11. Verification after authorization

Use Node 22.23.1 and pnpm 11.16.0:

git submodule update --init --recursive vendor/moss
test "$(git -C vendor/moss rev-parse HEAD)" = "1ae6b6322d51fae9104f047efb94e601050b967f"
pnpm -C vendor/moss install --frozen-lockfile
pnpm -C vendor/moss build
pnpm install --frozen-lockfile
pnpm exec vitest run packages/moss-adapter/test/live/artifact.test.mjs
MOSS_RPC_URL=https://rpc.monad.xyz pnpm --filter @moss-mini-demo/moss-adapter test:live
pnpm check
git diff --check origin/main...HEAD
git diff --name-only origin/main...HEAD
git status --short

The retained PR evidence must name date/time, exact head, Moss commit, patchset digest, RPC host only, exact block number/hash, quote/capability/result/warning counts, verification statuses, and classification. A live failure is retained accurately as nonzero STOP and is not relabelled as success.

12. QA, acceptance, and rollback

After implementation, freeze the exact head. A clean isolated SINGLE_OPERATOR_QA worktree must repeat the frozen install, vendor pin/build, offline tests, live command, full pnpm check, path/diff checks, secret scan, and artifact review. CI quality-gate must pass on the exact frozen head; the live command is manual evidence and is not added to CI.

Acceptance requires the exact five-path diff, all offline/full gates passing, a real quote/action/simulation artifact meeting the Issue acceptance criteria, no secret leakage, no Fixture claim, and no transaction submission surface.

Rollback is a single revert of the #29 squash commit or deletion of only the unmerged #29 branch/PR. It has no database, deployment, wallet, signing, or chain-state rollback.

13. Stop conditions

Stop and request a replacement Scope Gate if implementation needs a sixth path, dependency/lockfile/workflow/root-script change, Moss gitlink/source patch, a second protocol, private key/wallet, transaction submission, raw RPC logging, fixture fallback, weakened nonzero failure behavior, or a safety/authorization claim.

14. Requested decision

Record either:

SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED accepting this exact baseline, five-path set, pinned-Moss composition, secret boundary, classifications, verification, and stop conditions; or
SCOPE_CHANGES_REQUESTED naming the exact change required.

Until confirmed: WORK_PLAN_SUBMITTED / AWAITING_MAINTAINER_SCOPE_CONFIRMATION.

SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED

Frozen authorization object:

Work Plan: M2-08: Add Monad live smoke and provenance record #29 (comment)
comment ID: 5225013110
comment updated_at: 2026-08-08T06:55:02Z
exact body SHA-256: da8a3c41d8141ea299920e7797526c84ec0f7240d4c9f8184b9f448dd5cdec60
authorized baseline: origin/main@95c4aac532cdc2231054c431f3a175f9c223e1f5

Maintainer confirms the complete #29 Work Plan.

Authorized writable paths, exactly:

packages/moss-adapter/package.json
packages/moss-adapter/test/live/artifact.mjs
packages/moss-adapter/test/live/artifact.test.mjs
packages/moss-adapter/test/live/live-smoke.mjs
docs/live-smoke.md

Frozen requirements:

no dependency, lockfile, workflow, root-script, adapter-source/public-export, vendor gitlink/source, Web/API, fixture, governance, permission, protection, or deployment change;
sole P0 protocol is pinned PancakeSwap V2; Kuru and a second protocol remain out of scope;
exact pinned Moss commit is 1ae6b6322d51fae9104f047efb94e601050b967f, with the existing empty-patch digest and fixed MOSS_BUILD_INFO;
the actual live path is adapter-wrapped quote -> action -> simulate on chain ID 143, with exact action object forwarded to simulation and RPC calls passing through the adapter recording client;
output is one allowlisted JSON artifact containing only RPC scheme/host, exact build/pin/block provenance, counts, statuses, and stable classification;
only a completed real sequence with at least one result may use LIVE_SOURCE; no Fixture provenance is permitted;
any warning, halt, revert, UNPROVABLE requirement, zero result, or execution failure is explicit STOP and exits nonzero;
no raw URL/path/query/credentials/header/environment/Quote/Capability/receipt/change/warning/exception/stack output;
offline tests perform no network access and the live command remains excluded from pnpm check and CI;
the runner never signs, submits, broadcasts, or claims safety/authorization.

Builder is authorized to create only:

branch: codex/issue-29-monad-live-smoke
isolated implementation worktree: /Users/qy/Documents/moss-mini-demo-issue-29

Both must start from the exact authorized baseline. Any sixth path or change to the frozen dependency, protocol, provenance, secret, STOP, offline, or no-submission boundary invalidates this authorization and requires a replacement Scope Gate.

This authorizes implementation scope only. It is not SINGLE_OPERATOR_QA PASS, Review approval, READY_TO_MERGE, Merge Gate, or merge authorization. Implementation must be delivered as a Draft PR closing #29, pass exact-head quality-gate, freeze its head, and receive clean isolated QA and review on that exact object.

SCOPE_AMENDMENT_1_REQUEST

During implementation verification on the authorized baseline, a clean checkout with no generated packages/report-schema/dist failed the planned package-local first step:

pnpm --filter @moss-mini-demo/moss-adapter build
TS2307: Cannot find module '@moss-mini-demo/report-schema'

Cause: the adapter's existing TypeScript build consumes the report-schema package entry, whose declaration output must exist first. The root quality gate already enforces this ordering, but Issue #29's required standalone command is pnpm --filter @moss-mini-demo/moss-adapter test:live; therefore test:live must be clean-checkout complete by itself.

Requested amendment is limited to already authorized path packages/moss-adapter/package.json:

test:live = pnpm --filter @moss-mini-demo/report-schema build && pnpm build && node --conditions=react-server test/live/live-smoke.mjs

No sixth path, root-script, lockfile, dependency, workflow, adapter source/public export, vendor, protocol, live behavior, artifact, secret, STOP, QA, or no-submission boundary changes. All other terms of the frozen Work Plan and authorization remain unchanged.

Until separately authorized, this amendment is requested only and the package script remains at the original authorized form.

SCOPE_AMENDMENT_1_CONFIRMED / IMPLEMENTATION_AUTHORIZED

Reviewed amendment: #29 (comment)

comment ID: 5225063407
exact body SHA-256: 17ebbd91fa79830247f522fd5d72b4e0f632437ff5e1fe10386b4e02f4236197
reproduced failure: clean checkout lacks report-schema declaration output before adapter build
accepted correction: the already authorized packages/moss-adapter/package.json test:live script first runs pnpm --filter @moss-mini-demo/report-schema build, then the adapter-local build, then the live runner

The correction makes Issue #29's required single package command independently runnable from a frozen install. It does not add or modify any path beyond the existing five-path authorization and does not change dependencies, lockfile, root scripts, workflow, adapter source/public exports, vendor, protocol, RPC/artifact/STOP behavior, QA, or no-submission boundaries.

All unchanged terms of the Work Plan and original Scope Gate remain frozen. Builder may apply exactly this one script-order correction and continue implementation. This amendment is implementation authorization only, not SINGLE_OPERATOR_QA PASS, Review, READY_TO_MERGE, Merge Gate, or merge authorization.

SCOPE_AMENDMENT_2_REQUEST

The exact pinned vendor declares pnpm 11.10.0 in devEngines, while this project and the frozen #29 verification use pnpm 11.16.0. With pnpm 11.16.0, the documented vendor install command stops before installation with the package-manager version gate. This was reproduced before any vendor file changed.

Requested correction is limited to the already authorized docs/live-smoke.md prerequisite commands:

pnpm --pm-on-fail=ignore -C vendor/moss install --frozen-lockfile
pnpm --pm-on-fail=ignore -C vendor/moss build

This uses pnpm's invocation-only version-gate override while retaining pnpm 11.16.0 and frozen lockfile behavior. It creates no repository or vendor source change and adds no path, dependency, lockfile, workflow, script, permission, protocol, RPC, artifact, STOP, QA, or submission-surface change. All other Work Plan and authorization terms remain unchanged.

SCOPE_AMENDMENT_2_CONFIRMED / IMPLEMENTATION_AUTHORIZED

Reviewed amendment: #29 (comment)

comment ID: 5225079457
exact body SHA-256: 6505f4f400748b7e6ba77c69445df125a638cab919fe18319f280dd05ebda74c
reproduced condition: pinned vendor pnpm 11.10 devEngines stops project-standard pnpm 11.16 before frozen install
accepted correction: add pnpm's invocation-only --pm-on-fail=ignore flag to the two already authorized vendor prerequisite commands in docs/live-smoke.md

This retains Node 22.23.1, pnpm 11.16.0, frozen lockfile behavior, the exact pinned vendor tree, and the original five-path scope. It authorizes no vendor/repository change and no dependency, lockfile, workflow, script, permission, protocol, RPC, artifact, STOP, QA, or submission-surface change.

All other Work Plan, original Scope Gate, and Amendment 1 terms remain frozen. This is implementation authorization only, not SINGLE_OPERATOR_QA PASS, Review, READY_TO_MERGE, Merge Gate, or merge authorization.

IMPLEMENTATION_FROZEN

Draft PR #79 is frozen at accepted head ef2843b7bff32bc654a98af8fa78ac1a368019e3, tree b5f3e466c3e2fc9d5c339bbd39e0b712c746d4dc, base 95c4aac532cdc2231054c431f3a175f9c223e1f5.

exact-head quality-gate: SUCCESS, run 31245911474 / job 93074350153
exact-head live: SUCCESS on eip155:143, block 0x59c8869, hash 0xce5f74621c641b60e31052fde3570e4e27e8709db8cbbd6f27ae7bb94f509dec
quote 1; Capability/transaction nodes 1/1; results/warnings/reverted 1/0/0; not halted
block, capability integrity, receipt coverage and ordering PROVEN; state continuity NOT_APPLICABLE
Implementation Report: test: add Monad live smoke provenance #79 (comment)
reviewed scope including Amendments 1 and 2: exactly five paths, 997 additions / 0 deletions
exact-head pnpm check: 34 files / 1,117 tests; coverage 100%; implementation worktree clean

The earlier uncommitted UNPROVABLE diagnostic is retained transparently in the report and is not accepted. The current head leaves IMPLEMENT and enters clean same-operator QA. No independent reviewer is claimed.

IMPLEMENTATION_FROZEN / CLEAN_SINGLE_OPERATOR_QA_PENDING

SINGLE_OPERATOR_QA_HANDOFF

This is same-operator QA, not an independent reviewer claim.

PR test: add Monad live smoke provenance #79
base 95c4aac532cdc2231054c431f3a175f9c223e1f5
frozen head ef2843b7bff32bc654a98af8fa78ac1a368019e3
frozen tree b5f3e466c3e2fc9d5c339bbd39e0b712c746d4dc
exact-head CI run 31245911474 / job 93074350153 succeeded
detached clean QA path: /Users/qy/Documents/moss-mini-demo-issue-29-qa
Implementation Report: test: add Monad live smoke provenance #79 (comment)

QA started from a detached clean checkout with no node_modules, package dist, Web build, or initialized vendor tree. It performs a frozen root install, exact pinned vendor install/build, real live smoke, vendor deinitialization, credential-bearing negative smoke, complete root gate, exact five-path/parent/tree/gitlink audit, and PR/protection recheck. Any head movement invalidates this handoff.

SINGLE_OPERATOR_QA_HANDOFF / CLEAN_QA_START

SINGLE_OPERATOR_QA_PASS

This is same-operator QA from a separate clean detached worktree; no independent reviewer is claimed.

Accepted/frozen head ef2843b7bff32bc654a98af8fa78ac1a368019e3, tree b5f3e466c3e2fc9d5c339bbd39e0b712c746d4dc passed:

exact-head CI run 31245911474 / job 93074350153
frozen install on Node 22.23.1 / pnpm 11.16.0
clean pinned-Moss live SUCCESS / LIVE_SOURCE at block 0x59c8a1c, hash 0x78df871a6a8e62ee3c99ea3c2cff9f5a4571812ac878f7f88c81e68bbf58f2d5
quote 1, Capability/transaction nodes 1/1, results/warnings/reverted 1/0/0, no halt
exact call block parameters; block/integrity/coverage/ordering PROVEN, continuity NOT_APPLICABLE
credential-bearing negative test: exit 1, explicit FAILED_STOP, no secret sentinel
root pnpm check: 34 files / 1,117 tests plus all build/import/browser/production gates
preflight-core 200-test coverage at 100% statements/branches/functions/lines
exact five-path scope, parent/tree/gitlink, offline/no-Fixture, secret, no-submission, and clean-worktree audits

The unchanged 6 pre-existing Web audit advisories are recorded in the QA report and were not introduced by #29. Full QA record: #79 (comment)

PASS. Any head movement invalidates this result.

SINGLE_OPERATOR_QA_PASS / READY_FOR_MERGE_GATE_ASSESSMENT

READY_TO_MERGE

PR #79 is ready at immutable head ef2843b7bff32bc654a98af8fa78ac1a368019e3, tree b5f3e466c3e2fc9d5c339bbd39e0b712c746d4dc.

Work Plan/Scope Gate/Amendments, Implementation Report, separate clean SINGLE_OPERATOR_QA_PASS, exact-head quality-gate run 31245911474/job 93074350153, two successful exact-head live reproductions, 0 unresolved threads, MERGEABLE/CLEAN status, exact five-path scope, and protected-main/squash-only policy have all been rechecked with no head movement.

PR merge-gate record: #79 (comment)

Authorized next state: leave Draft and use protected squash merge only. No independent reviewer or pre-merge completion claim.

READY_TO_MERGE / PROTECTED_SQUASH_ONLY

test: add Monad live smoke provenance (#79)

POST_MERGE_AUDIT_PASS

Issue #29 delivery is complete on the exact reviewed object.

PR: test: add Monad live smoke provenance #79
READY_TO_MERGE: test: add Monad live smoke provenance #79 (comment)
accepted head: ef2843b7bff32bc654a98af8fa78ac1a368019e3
accepted base: 95c4aac532cdc2231054c431f3a175f9c223e1f5
accepted/merged tree: b5f3e466c3e2fc9d5c339bbd39e0b712c746d4dc
squash/main commit: a09c2a7b989b67264e8078857127a5dd96df1643
merged at: 2026-08-08T07:29:09Z
exact-head quality-gate: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31245911474/job/93074350153
merged-main quality-gate: SUCCESS, https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/31246268957/job/93075280079
PR audit: test: add Monad live smoke provenance #79 (comment)

Post-merge audit confirms PR MERGED; squash commit has one parent; merge tree equals the clean-QA tree; Issue is Closed/Completed and Project Done; remote/local feature branches and isolated worktrees are removed; main is synchronized and clean; strict protection and the Moss pin remain unchanged; no auto-merge or admin bypass was used.

This completes M2-08 and permits a fresh dependency-gate evaluation for #34. It does not itself authorize #34 implementation; that Issue requires its own dependency record, Work Plan, and Scope Gate.

POST_MERGE_AUDIT_PASS / M2_08_DONE

Navigation Menu

Repository navigation

M2-08: Add Monad live smoke and provenance record #29

DEPENDENCY_GATE_CLEARED

2 remaining items

M2_EXECUTION_SLOT_ASSIGNED

Final Implementation Work Plan - M2-08 Monad Live Smoke and Provenance Record

0. Status and frozen baseline

1. Goal and authority boundary

2. Exact writable paths

3. Invocation and isolation

4. Pinned Moss composition

5. Fixed live sequence

6. Artifact contract and provenance

7. Result and STOP semantics

8. Secret boundary

9. Offline tests

10. Documentation

11. Verification after authorization

12. QA, acceptance, and rollback

13. Stop conditions

14. Requested decision

SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED

SCOPE_AMENDMENT_1_REQUEST

SCOPE_AMENDMENT_1_CONFIRMED / IMPLEMENTATION_AUTHORIZED

SCOPE_AMENDMENT_2_REQUEST

SCOPE_AMENDMENT_2_CONFIRMED / IMPLEMENTATION_AUTHORIZED

IMPLEMENTATION_FROZEN

SINGLE_OPERATOR_QA_HANDOFF

SINGLE_OPERATOR_QA_PASS

READY_TO_MERGE

POST_MERGE_AUDIT_PASS

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

M2-08: Add Monad live smoke and provenance record #29

Description

Activity

pillowtalk-Qy commented on Aug 8, 2026

DEPENDENCY_GATE_CLEARED

2 remaining items

pillowtalk-Qy commented on Aug 8, 2026

M2_EXECUTION_SLOT_ASSIGNED

pillowtalk-Qy commented on Aug 8, 2026

Final Implementation Work Plan - M2-08 Monad Live Smoke and Provenance Record

0. Status and frozen baseline

1. Goal and authority boundary

2. Exact writable paths

3. Invocation and isolation

4. Pinned Moss composition

5. Fixed live sequence

6. Artifact contract and provenance

7. Result and STOP semantics

8. Secret boundary

9. Offline tests

10. Documentation

11. Verification after authorization

12. QA, acceptance, and rollback

13. Stop conditions

14. Requested decision

pillowtalk-Qy commented on Aug 8, 2026

SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED

pillowtalk-Qy commented on Aug 8, 2026

SCOPE_AMENDMENT_1_REQUEST

pillowtalk-Qy commented on Aug 8, 2026

SCOPE_AMENDMENT_1_CONFIRMED / IMPLEMENTATION_AUTHORIZED

pillowtalk-Qy commented on Aug 8, 2026

SCOPE_AMENDMENT_2_REQUEST

pillowtalk-Qy commented on Aug 8, 2026

SCOPE_AMENDMENT_2_CONFIRMED / IMPLEMENTATION_AUTHORIZED

pillowtalk-Qy commented on Aug 8, 2026

IMPLEMENTATION_FROZEN

pillowtalk-Qy commented on Aug 8, 2026

SINGLE_OPERATOR_QA_HANDOFF

pillowtalk-Qy commented on Aug 8, 2026

SINGLE_OPERATOR_QA_PASS

pillowtalk-Qy commented on Aug 8, 2026

READY_TO_MERGE

pillowtalk-Qy commented on Aug 8, 2026

POST_MERGE_AUDIT_PASS

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions