Qualify Pi 1.0.4 core, shipped MCP wrapper and plain Delegate subprocess

Current target — Pi 1.0.4 and the shipping subprocess

Use exact released Pi1.0.4 (7c10bd4337495ee613f2224843ecdf349b80d1df) and the MCP wrapper already shipped by Piclaw. Delegate stays the existing plain subprocess. Native replacement, pi-durable, parent-provider proxy, resource-domain and confinement frameworks are outside this work.

Core Pi1.0.4 qualification is merged in #1574 at dc697b2; shipping Delegate0.2.18 thinking inheritance is merged in rcarmo/piclaw-addons#179 at69301a9. Source merge is not installation, restart, live-account acceptance or activation.

Current checklist

Exact eight-package archive/payload admission, public contracts and core source migration: PR1574.
Fresh synthetic MCP/tool-selection, auth/CLI, private Anthropic UI and shipping Delegate runner checks recorded in PR1574.
Reconcile the applicable MCP-01–15 acceptance rows with exact1.0.4 evidence; unsupported Native seams remain explicit.
Complete any remaining supported-wrapper/child tool exposure and security checks without claiming process groups are an OS sandbox.
Complete separately approved operational acceptance before deployment/activation.

Superseded framework requirements below are historical, not current shipping dependencies. Unfinished security/auth/operational work is not marked delivered.

Previous issue scope and evidence — retained history

Current integration target — released Pi 1.0.3

Rui authorised the retarget on 5 October 2026 after the unified timeline/meters/audit integration. Exact upstream release: d78dc83d633229d12f8b79631384c4c2717c399f. The shipped MCP wrapper remains selected; Native replacement/parity and pi-durable are outside this integration.

Core source is merged through PR1558, 6ceaeaed1: eight exact archives and payload admission, fresh public SDK/provider/CLI/device/browser/private-UI evidence, frozen full 6,516 passed/eight existing skips/zero failed, and postmerge17tests/485assertions. No installation or restart. Azure's built-in provider is now azure; the Responses API identifier and Piclaw optional custom provider IDs are unchanged. Retired Azure selections fail closed with manual migration guidance; live auth/config files are not rewritten by source qualification. The released cancelled-refresh persistence fix is tested, but raw provider/auth settlement and account-generation contracts are still absent. Production Delegate remains inactive.

Earlier 1.0.2 and prior-version bodies and receipts are preserved below as history. Source merge authority does not permit deployment/restart, live account/server calls or provider spend. Those operations, canary/soak and operational rollback need separate approval.

Current checklist

Fresh released1.0.3 source/full/types/build and scoped auth/SDK/MCP compatibility qualification published in PR1558.
Historical1.0.2 evidence is unchanged; wrapper is retained and Native-only rows remain future scope.
Finish production Delegate settlement/account authority and immutable artifact/policy/credential/owner/orphan gates.
Complete deeper automatic-GC, real scheduler claim-loop and concurrent family/write performance coverage; measured1.0.2 audit is historical scoped evidence.
Record separately approved live tests, matching core/add-on rollout, soak and operational/token rollback.

Earlier target criteria and receipts — preserved historical record

Current integration target — Pi 1.0.2

Rui authorised retargeting to released Pi 1.0.2 on 5 October 2026, upstream commit cd32f7725fdbddbaecdff5b1e68491563394e0ca. This work integrates Pi with the standard MCP wrapper already shipped by Piclaw. Wrapper replacement, Native MCP parity and adapter removal are future work, not prerequisites for this integration. Keep one wrapper owner; reject unsupported Native selection without fallback. This scope decision does not weaken the shipped wrapper's credential, policy or cleanup requirements.

Preserve 0.99.1, 1.0.0 and 1.0.1 receipts as historical evidence. New 1.0.2 qualification is separate. Unreleased upstream OAuth cancellation changes after the 1.0.2 tag are excluded. Source updates, isolated tests, review and verified merges are authorised; installation, restart and real-account/provider tests still need separate approval. Pi-durable remains out of scope.

Integration checklist and completed slices

Current exact-target acceptance inventory published (PR Document remaining Pi 1.0.1 acceptance gates #1548); historical results are labelled.
Wrapper retention and pi-durable exclusion are explicit scope decisions.
Fresh immutable retained-wrapper/core source qualification complete: final checkpoint full6456/8skip0fail, types/build, both-skin browser14/590, source-bound core100/405 and wrapper316, synthetic auth144 and measured-profile inventory (PR Record released Pi 1.0.2 retained-wrapper acceptance and remaining gates #1552).
Complete production Delegate/account/raw-settlement, immutable artifact/exposure/family/secret/owner/orphan gates and unmeasured mixed/background/large-history/GC resource coverage; source passes do not qualify those paths.
Current MCP-01–15/AUTH-01–08 checkpoint records scoped passes, partial Delegate evidence and unfinished live/rollout gates in PR Record released Pi 1.0.2 retained-wrapper acceptance and remaining gates #1552. Native-only replacement rows are future scope.
Disposable stopped-writer SQLite WAL/FULL, public JSONL/session and reference-only config snapshot restore passed1.0.1→1.0.2→restored1.0.1; bytes verified and post-cutover writes quarantined without automatic replay. No live token or core/add-on operational rollback.
Record separate live-test/rollout/rollback approval and outcome.

Previous target criteria and receipts — preserved historical record

Active target — Pi 1.0.1 (3 October 2026)

Rui authorised retargeting and implementation to exact Pi 1.0.1, upstream git head a7229ddc21810d6245105978033b7df645ecc2f7. This supersedes the earlier 1.0.0 execution target below. Preserve all 0.99.1 and 1.0.0 receipts as historical evidence; they are not 1.0.1 qualification.

Source migration, exact-package admission and isolated Bun-only synthetic qualification are authorised. Keep Adapter/Auto as the default, reject unsupported native combinations, retain failed-teardown/Apply security gates, and exclude pi-durable. Live accounts, deployment, production installation, restart and canary remain separately authorised. Do not waive unresolved native, provider or Delegate acceptance gates.

Earlier target and requirements (retained)

Checkpoint: 958ac185255840ee4f800becc5f7e3111ef9acda on feat/mcp-settings-host; stable 0.99.1 source baseline, not 1.0.0 admission.

Shared target and MCP policy

Selected target: Pi 1.0.0, gitHead a13d35a742c6ef8462812a28fbe1d8c8b7431c32. Rui explicitly authorised retargeting all remaining work on 1 October 2026: stabilise and commit current work → update relevant issues/dependencies → resume the 1.0.0 upgrade on that checkpoint. Source changes, isolated dependency installs and offline qualification are authorised; runtime admission remains an acceptance gate, not an assumed result. All new execution is Bun-only. Live accounts/MCP/provider calls, production installation, deployment/restart and experimental pi-durable activation still require separate approval. Preserve completed 0.99.1 receipts and closed issue states as historical evidence; do not relabel them as 1.0.0 results.

Preserve the approved consolidated instance MCP settings: adapter/native selector, adapter default, exactly one active owner, codemode Auto/On/Off default Auto.
Engine switching aborts active turns and reloads all extensions through supported public APIs, retaining chats/history; no service restart. Unsupported combinations reject with explicit reasons; no silent fallback or dropped settings.
Ten native public-API gap diagnostics persist in the 1.0.0 assessment. Target selection is not a capability/security waiver.
Old Harness/Pico3 exports are removed. Design the pi-durable 1.0.0 Harness successor and HC/PC crosswalk #1493 owns the pi-durable semantic/authority design and Qualify pi-durable 1.0.0 storage and Harness semantics on Bun without activation #1494 its isolated qualification. Do not add pi-durable to production merely to repair imports.

Summary

Collect final offline, UI and authorised server receipts for the exact combined candidate before any production cutover.

Parent: #1442

MCP contract: #1444

Dependencies

Blocked by Admit exact Pi 1.0.0 and migrate current-loop removed import boundaries #1492
Blocked by Qualify Pi 1.0.2 provider, MCP and Delegate integration deltas #1495
Blocked by Preserve MCP prompts, Apps, resources and bounded results on Pi 1.0.2 #1449
Blocked by Provide keychain-backed MCP OAuth and web/headless sign-in on Pi 1.0.2 #1450
Blocked by Implement instance MCP settings, engine switching and codemode on Pi 1.0.2 #1451
Blocked by Qualify provider login, refresh and logout for Pi 1.0.4 #1458
Blocked by Qualify Delegate plain subprocesses for Pi 1.0.4 piclaw-addons#160
Scope decision, 3 October: Design the pi-durable 1.0.0 Harness successor and HC/PC crosswalk #1493 design is approved/merged via Document Pi 1.0.0 durable architecture and HC/PC crosswalk #1514; all pi-durable work (Qualify pi-durable 1.0.0 storage and Harness semantics on Bun without activation #1494 qualification and implementation included) is OUT OF SCOPE and is not a current-track dependency.

Acceptance Criteria

Implementation Notes

Evidence classes remain distinct: source inspection, tagged-source tests, packed imports, synthetic runtime fixtures, live server qualification, production canary. Do not hardcode prior 10/3/1 capability counts as success. Full-plan independent source review completed; implementation requires its own review.

Estimate: M · Risk: high · Source file: Makefile

Source anchors: Piclaw baseline, upstream release, MCP guide, public extension options.

Test Plan

Gather test-time profiling data as required by Rui on 3 October: CPU hotspots and event-loop delay, database query/transaction counts and durations, lock/busy/retry waits, parsing/config reads/serialization/history traversal, and memory/GC where relevant. Include the actual child processes doing work.
Use fixed-version, representative synthetic/disposable workloads (including disk-backed SQLite), repeated cold/warm baseline versus candidate runs, and record instrumentation overhead. Retain machine-readable profiles and a ranked hotspot report with measured deltas; do not infer end-to-end speed from handler times alone (lesson from perf: avoid repeated config I/O and event-loop stalls in context projection #1517).
Keep profiling runs distinct from unchanged correctness gates. No relaxed safety/timeout assertions, live DB/credentials or raw bind values/prompts/tokens in artifacts. Review profiling artifacts before publication; no deployment/restart implied.
MCP-01–15 matrix plus fresh core/session/provider/security regressions, historical Harness/Pico3 isolation and the Design the pi-durable 1.0.0 Harness successor and HC/PC crosswalk #1493/Qualify pi-durable 1.0.0 storage and Harness semantics on Bun without activation #1494 successor disposition.
Immutable prerelease UX/E2E and rollback drill using disposable state.
Separate authorised live compatibility run with bounded read-only calls.

Definition of Done

Acceptance criteria satisfied with exact-version evidence
Required tests/typechecks pass (documentation-only changes use structural/link review)
Docs and migration guidance updated
Operational impact and rollback assessed
Update history and parent/dependency status reflect evidence

Provider-login coverage — 29 September 2026

Blocked by #1458 in addition to the existing dependencies. Verify the provider/method matrix independently of MCP-10: login, refresh/revocation, cancellation, logout, external credentials and activation. Real login/refresh/revocation requires separate permission; never log out the user or spend inference to test without approval.

Pre-retarget issue body — historical record, not current target authority

Summary

Collect final offline, UI and authorised server receipts for the exact combined candidate before any production cutover.

Planning record only. This issue does not authorise package installation, live credentials/MCP/provider calls, production activation, deployment or restart. Target exactly Earendil 0.99.1 (gitHead d86654abb8862e201933517d6f1fce9f88dd117f), starting from 0.87.1 / Delegate 0.2.13. A later upstream fix needs an explicit target decision and its own receipt. Preserve completed 0.87.1 history.

Parent: #1442

MCP contract: #1444

Dependencies

Blocked by Qualify provider login, refresh and logout for Pi 1.0.4 #1458 — provider-login qualification
Blocked by Migrate core SDK, tools and providers to Earendil 0.99.1 #1445
Blocked by Assess conditional adapter removal after Pi 1.0.2 native MCP parity #1454
Blocked by Qualify Delegate plain subprocesses for Pi 1.0.4 piclaw-addons#160
Blocked by Refresh stable Harness and streaming-fork evidence for Earendil 0.99.1 #1452
Blocked by Assess Earendil 0.99.1 Pico3 deltas without production adoption #1453

Acceptance Criteria

Require passing AUTH-01–08 evidence from Qualify provider login, refresh and logout for Pi 1.0.4 #1458, including built-artifact OpenAI/OpenAI Codex login and full provider lifecycle/UI tests; any required live-login skip needs an explicit waiver.
All MCP-01–15 requirements have passing receipts or an explicit user-approved target/scope change; none inferred from source inspection or the 0.99.0 discovery probe.
Run final typecheck/build/focused regressions and make ci-fast through controlled launchers with isolated state, then UX prerelease gates on the immutable candidate SHA.
With separate live-call approval, test exact-target Memento auth/discovery, one approved read-only tool, approved resource/prompt calls, denial, abort and disposal; no unapproved mutations.
Verify Delegate immutable artifact with core, exposure and family policy, credential scans, no orphan processes and exactly one MCP owner.
Rehearse consistent DB/session/config/core/add-on snapshot restore and handle post-cutover writes without silent loss or duplicate side effects.
Report go/no-go and unresolved blockers; no install/restart automatically follows successful tests.

Implementation Notes

Evidence classes remain distinct: source inspection, tagged-source tests, packed imports, synthetic runtime fixtures, live server qualification, production canary. Do not hardcode prior 10/3/1 capability counts as success. Full-plan independent source review completed; implementation requires its own review.

Estimate: M · Risk: high · Source file: Makefile

Source anchors: Piclaw baseline, upstream release, MCP guide, public extension options.

Test Plan

MCP-01–15 matrix plus core session/provider/security regressions and stable Harness/Pico3 boundary receipts.
Immutable prerelease UX/E2E and rollback drill using disposable state.
Separate authorised live compatibility run with bounded read-only calls.

Definition of Done

Acceptance criteria satisfied with exact-version evidence
Required tests/typechecks pass (documentation-only changes use structural/link review)
Docs and migration guidance updated
Operational impact and rollback assessed
Update history and parent/dependency status reflect evidence

Provider-login coverage — 29 September 2026

Blocked by #1458 in addition to the existing dependencies. Verify the provider/method matrix independently of MCP-10: login, refresh/revocation, cancellation, logout, external credentials and activation. Real login/refresh/revocation requires separate permission; never log out the user or spend inference to test without approval.

Legacy-auth contention follow-up PR #1533 fixes stale repair results: full observed-state CAS + canonical reread after token/login-ID writes. Fifteen deterministic real-WAL-writer baseline observations and fifteen corrected cases; strict baseline delete control fails. Corrected twelve identity/revocation cases deny, three legitimate concurrent repairs pass. Final auth118/588; combined1530+1532+fix26/110; full6030/8skip0+25feature9web+separatehistory468/8720;types/lint/pack/two reviews pass. Normalread path unchanged, no timeout/durability/schema change. ExactnullIDABA and post-final-readrevocation not claimed. No live/deploy/restart; maintenanceworker remains separate.

Pi 1.0.1 implementation review — 4 October 2026

Exact target: 1.0.1, upstream a7229ddc21810d6245105978033b7df645ecc2f7. Core #1537 merged at 98eb5ff4d after exact-head hosted CI and local full qualification: 6,095 passed / 8 skipped / 0 failed, 39,748 assertions, plus 25 feature and 9 web tests. Postmerge 55 tests / 1,380 assertions passed.

Rui authorised the Smith install/restart. The restarted instance reports Piclaw 3.2.5 / Pi 1.0.1, canonical Bun, HTTP200, eight exact package payloads and import resolutions, unchanged configuration/database identity, recovered restart handoff and persisted chat. This local operational check does not complete provider-login or native-engine canary criteria.

Delegate #166 merged at 12f35b5, published through the public tarball path, and 0.2.15 is installed. Global and workspace CLI both report1.0.1; manifest resolver and isolated synthetic catalogue checks passed with zero guarded network/child-process attempts. No model/provider approval or billing route changed.

Original0.99.1/1.0.0 receipts are unchanged. The repository historical folder/replay hook was removed at Rui's explicit request; Git retains source history.

Disposition

Keep OPEN. The exact1.0.1 migration gate and separate profiled SDK/DB slices passed; #1536 retention optimization is now merged at9792cee4ac. These scoped results do not replace the complete MCP-01–15/security/UX/Delegate/resource/rollback acceptance matrix. Required unexecuted rows remain unqualified.

Exact-target evidence

No missing acceptance row is marked passing.

Fresh 1.0.1 synthetic seam evidence — 4 October 2026

Add-on PR #172 merged cc8a67c46b3281d00704bee5502bce4bf652d1b4 after all three exact-head checks passed (run 37205906599, head fb833179dc9177dc6e853345aa050dd48b60f186). Merged-tree parity and postmerge saved-receipt validator 1/11 plus catalogue check passed.

Fresh target 1.0.1 / upstream a7229ddc21810d6245105978033b7df645ecc2f7:

Guarded synthetic public-provider/private-pipe matrix 1 test / 580 assertions / 6.80s, six cases: refresh rotation, API-key scoped environment, logout, denied auth, disconnect and forced child termination.
Exact archive integrity and 561 installed JS/JSON byte comparisons; exact-1.0.1 fixture types passed.
Checked non-root, zero effective/permitted/bounding/ambient capabilities, NoNewPrivs=1, separate loopback-only network namespace. Fetch instrumentation zero; namespace supplies external-egress isolation, not full socket-attempt accounting or filesystem sandboxing.
Repository compatibility 272 pass / 13 opt-in skips / 0 fail, 1,607 assertions; five type projects passed. Integration evidence is separate from ordinary-suite opt-in skips.
Independent direct auditor review cleared source, public APIs, artifact provenance, guard, safe raw log and limits. Historical 1.0.0 files/receipts remain unchanged.

Receipt · Reproduction and limits

Keep parent acceptance open. This is not production Delegate credential/profile/environment implementation, cooperative cancellation, atomic logout-to-dispatch, custom/ambient-provider parity, selected MCP engine, budget/live-account/canary acceptance or deployment. No installation/restart or live credential/provider action occurred in this qualification. Source merge does not change installed Delegate 0.2.15.

The current Pi 1.0.1 acceptance matrix is merged in PR1548 (62a71d139).

Remaining MCP/auth acceptance lists all15MCP and8AUTH requirements, current source/synthetic evidence and missing gates. Corrected fullgate6311pass/8skip/0fail plus25feature/9web; exactheadCI37248552703SUCCESS; postmerge8tests158assertions. Historical versioned receipts are unchanged.

The exact public1.0.1 probe still reports tenNativeAPIgaps; the separate close-failure regression still records an unclosed old transport despite reload success. Adapter/Auto retained, unsupportedNative admission denied.
Ledger1544, inactivehost1546 and sharedrequest1547 foundations are merged. Actualproductionprovider/authcleanup/accountauthority and Delegate/sharedactivation are unqualified; upstreamPi10461auto-close was contributorpolicy, not a fix.
Adapter server Settings controller/API/forms are a separate implementation lane; currentcorepin2400aec does not yet contain publicpreviewPR10.
Combined1455 and separatelyauthorisedcanary/rollout/soak/rollback1456 remain outstanding. Source gates do not extend the initial installedmigration receipt. Pi-durable stays excluded.

This records evidence and blockers; no unmet acceptance criterion is waived and parent acceptance remains open. No new installation, restart, live account, credential lookup or provider expenditure was performed.

Released Pi1.0.2 retained-wrapper source reconciliation: #1552. Exact Settings CI37286187765, final full6456/8skip0fail, source-bound core100/405/wrapper316 and auth144 with explicit test-only correction are recorded. Historical criteria retained unchanged. This issue stays open for its production/live/rollout or wider resource gates. No installation/restart/live account/provider expenditure occurred.

Pi 1.0.3 deeper workload checkpoint

The source-only candidate adds captured-authority asynchronous family HTTP admission and isolated scheduler, concurrent family and public SessionManager natural-retention fixtures. Documentation distinguishes successful measured runs from retained fixture/telemetry failures, exploratory comparisons without execution-time source binding, and contention-batch completion from isolated ACK latency.

PR #1560 merged at f8f2eb55cdb2cba2c55387e37308a228dbf8f1b8 (14:58:51 UTC). Frozen d8a95676a7e0ad70e34255902e71d2945b901bb7 passed 77 focused tests / 841 assertions, types/scoped lint/diff checks, and the full local gate: 6,527 pass / 8 existing skips / 0 fail / 42,737 assertions, plus 25 feature and nine web tests. Documentation-only publication 2b1e08a47fd96e622dd90cbfa2c7cbaaa2dfeaa9 retained exact runtime/test/script/dependency parity; merge tree parity verified. Postmerge: 27 pass / 205 assertions. Independent runtime and evidence reviews cleared the bounded source slice after correcting provenance/metric labels.

Receipts: pi-103-deeper-performance.md and pi-103-deeper-qualification.json. No automatic hosted result was available at the first observation; no hosted success is implied.

No dependency/schema change, installation, restart, live account/provider spending or production Delegate activation. Natural finalization is observational; scheduler agent/restoration/outbound are synthetic. Broader workload/platform and retention-soak gates remain open.

The public raw auth/provider settlement and account-generation contracts remain unavailable for production Delegate. Upstream pi#10461 is CLOSED by automated new-contributor policy, with no implementation evidence; it must not be interpreted as contract delivery. Add-ons #160 and core acceptance/rollout gates remain open. Real-account/server canary, soak, protected Azure migration and operational rollback require a separately approved scope.

Publication metadata correction

Automatic hosted run 37329109522 failed before tests: PR1560's final documentation receipt introduced a PICLAW_DB_IN_MEMORY reference missing from generated environment observations. The earlier local gate passed before that documentation-only overlay; it did not test the generated catalog after publication. The hosted failure is retained, not counted as success.

PR1561 merged the one-line generated catalog correction at 80ec14fff50b01708892880c7309ccfb544b9929. No runtime/test/script/dependency changes. Independent review verified exact regeneration, unchanged reader/statistic counts and qualification reuse for unchanged runtime. Fresh environment/dependency/diff checks and focused16tests/2397assertions pass; postmerge16/2397pass and exact tree parity verified. No new hosted success was available at first corrected-head observation. Production Delegate and live deployment/canary/soak/rollback approval stay open.

Corrected synthetic VM900 canary completed

PR1563 fixes the config-mode defect found by the first synthetic canary; PR1564 publishes the reviewed receipt and bounded acceptance scope.

Corrected package SHA256 023d2541265cafa259bebe91ed41afbc3660816a7b98f5de0b719197a3516ddc, source 34e4bda1a6c35aebd22b9dd2a127854b2438d9cc, tree 66192a17691b6ddd36f47d4db175360b8187f43f. Frozen lock overlay installed on VM900 with Bun1.4.2; 785 package runtime/extension/manifest files verified against source and deployment. Source full6533/8existing skips/0fail42756 plus25feature/nineweb, exacthosted37346512175SUCCESS and config postmerge25/195. Receipt publication2ecb89364 merged78c49e26c, exacttreeparity, env/doc validation plus focused16/2388 and finalpostmerge5/69 pass; no unchanged full-suite repeat.

Approved deterministic Classic service window ran17:13:30.017→17:43:30.036UTC: 1,800,019ms,59ordered prompt/reply cycles, samePID and exactly one terminal/plainreply each. Bothskin correlated visible prompt/reply/Settings checks, exact cancellation/SSE reconnect, actualrunningservice scheduler, packagedrealAgentPool leaf/source/recurrence, familyowner/CSRF/idempotency/500msrelease+revocation and actualruntimeMCPproxy syntheticloopback call passed within their stated scopes. Config modes stay0600 across observedstartup/restart/finalchecks. Watchdog32samples covers latterhalf only; Visualrestarts duringMCP qualification are not a second30minsoak. No outside-attempt markers; no universalpacket/rawauthsettlement claim.

Allfivecanaryunits stopped; two freshprofiles quarantined withoutreplay; 48,755candidatefilehashes and65originalDB/sidecarhashes verified. OS/SSH/guestagentpreserved, approvedBunreplacementremains, Smithunchanged. Originalpackage8fc…failedafter21cycles becauseordinaryconfigwriterwidened0600→0644; failedrun/harnesscorrections/reviewtimeoutsretained and excluded. ConfigfixretainsstrictMCPcheck/privatewriteatomicrename.

Evidence: canary document and receipt.

Overall acceptance remains incomplete. Public rawauth/provider settlement/account-generation contracts and productionDelegate remain gated; required immutablecore/addon/policy/credential/soleowner/orphangates stayopen. Liveaccount/server/Memento checks, protectedAzurecredentialmigration, productionSmithdeployment/restart and token-aware rollback need separateapproval. Workspacegoaladdon typebox resolutionwarning is retained, not fixed by this slice. No parent issue closure or production activation follows from the synthetic pass.

Current Pi 1.0.3 source/synthetic checkpoint

PR1565, merge ad2b298f10c10d81cb6d277620aa464da4c53dd4, fixes the fresh offline core add-on seed's missing host peers. Declared allowlisted peers link to the creating runtime instance; no duplicate Pi/package-manager/network startup install. Existing workspace/update/removal state is untouched, dangling targets fail closed, concurrent normal seed publishers are serialised. Absolute host links require a separate migration if the creating runtime moves; no native Windows execution or adversarial filesystem guarantee is asserted.

Frozen 09a7597b1bb8073f78dcbfc7321486dbbf28286f, tree d1c2470b45d2a7656c098acbd4638699fcc89c9b: 6,537 pass / 8 existing skips / 0 fail / 42,781 assertions, plus25feature/nineweb; unchanged source binding. Sevenregressions/32assertions, guarded imports of seven actual pinned entry points with exact hostpeeridentity and0network/process attempts, publication22/2362 and postmerge7/32 pass. The import probe qualifies entry loading only, nottool/UI/paidDelegate execution. PR hosted37357905234/main37357910171 still in progress at18:48:52; no success inferred.

PR1566, merge a446de1e0b72ed408bdcd6156f379faee3c4f8fa, records the current23-row MCP/auth checkpoint, hashes sevencurrentreceipts and retains older wrapper/auth/rollback executions as historical. Documentation-only parity, matrix/hash/link validation, env/diff and focused18/2394 plus postmerge10/96 pass; no unchanged full-suite rerun. Unsupported unbound postmerge counts were removed during independent review.

Evidence: current acceptance matrix, checkpoint receipt, host-peer correction.

Source/synthetic scopes are complete; overall production acceptance is not. Production Delegate still lacks public raw provider/auth settlement and account-generation authority contracts. Upstream10461 remains auto-closed by contributor policy with no delivered contract. Required immutable core/add-on/policy/credential/sole-owner/orphan checks and live account/server/Azure/Smith-rollout decisions remain open. No new installation/restart/live/account/paid request/production activation. No issue closing keywords or criterion waivers. User scope decision requested separately in card62795; generic goal continuation does not grant it. Original synthetic canary warning/failures are preserved, not retrospectively relabelled as new artifact passes.

Smith upgraded; current Delegate qualification merged

Rui explicitly ordered core upgrade first, then Delegate. Smith upgrade verification passed19:34:42UTC: Pi1.0.1→1.0.3 across all8SDKpackages, canonicalBun1.4.2/newPID3025469/HTTP200, installedsourcea446de1e0/tree06d929eb verified, config/credentialbytesunchanged/config600, SQLiteDBidentity/quickcheck/chatmonotonicpreserved. Workingprivatebackup restored78,143file/symlinkentries, restoredSQLite healthy andold1.0.1SDKexecutionsmoke passed. Activewriter multi-fileJSONL snapshot is explicitly not a stopped-writer atomic snapshot. NoDelegateactivation/liveprovidertest follows automatically.

Add-ons PR174 merged fbb7e02194336d3cf1280ee4b3d137d017a09a54. Current exactpublished1.0.3 CLI:76matchedselectedfiles/equalinventories, publicbin.pi offlineversion,1test94assertions; currentpublicprovider/privatepipeauth:564matchedselectedfiles/equalinventories,6casesrotation/scopedenvironment/logout/denied/disconnect/terminate,1test587assertions. Nonroot loopback-onlynamespace/capabilitieszero/noNewPrivs/minimalenv/no livecredentials ornetwork. Strictfixturetypesagainstexact103pass; compat281/15opt-in skips0fail1681 plus5typeprojects/catalog/standalone1/1 pass; postmerge3pass/2opt-skip0fail39. Tenhistorical1.0.0/1.0.1files preserved. This isqualificationtest/docs only; addonimplementation/version0.2.17unchanged andnotinstalled. Earliercatalogtimestampgate/incorrectintegrity/config/receiptcounterfailuresretained, notpasses.

A fresh actualpublicPi1.0.3ModelRuntime syntheticheld-tail reproduction also passed in thecapzero/loopback-onlynamespace: cancelledauthdelivery rejects while rawresolverheld; terminal/result resolves whileprovider rawtailheld; bothrawtails laterreleased/drained. Zero network/emptycredentialstore. It confirms that publicresult()/auth delivery cannotimplementrawsettled/close acknowledgement. Upstream10461autoclosed status is notdelivery. No privateSDK/provider substitution/credentialcopy workaround isaccepted.

InstalledSmithDelegate remains0.2.15, while publishedsource0.2.17hasCLI/authfailclosed fixes. Currentproductionchildlaunch inheritsparentenv; credential-freeparentproxy remainsunregistered and budget/MCP/account-generation/rawsettlement gatesopen. Newcurrent syntheticpipe doesnotclaimatomiclogoutdispatch/ambientcustomauth/realproviderbudgetparity. ProductionDelegate completion needs a qualified public raw-task/account-authority path or an explicitly narrowed reviewed execution plan and separate rollout/live validation authority. Keep #160 and core acceptance gatesopen; upgrade-order approval doesnotwaive those safetyrequirements.

v3.3.0 Modern Times is now published at e4c2b9a with Pi1.0.4. UX37509195565, main CI37509183176 and publish/integration37509955937 completed successfully after retained retries; release artifacts and GHCR architectures are verified. The release removes the old source-upgrade prerequisite, but does not satisfy the remaining acceptance in this issue: live account/provider coverage, outstanding supported-wrapper/security reconciliation or an explicitly approved installed canary/rollback must not be inferred from source/UX publication. Keeping this issue open; no Smith install/restart has occurred.

Qualify Pi 1.0.4 core, shipped MCP wrapper and plain Delegate subprocess #1455

Description

Current target — Pi 1.0.4 and the shipping subprocess

Current checklist

Current integration target — released Pi 1.0.3

Current checklist

Current integration target — Pi 1.0.2

Integration checklist and completed slices

Active target — Pi 1.0.1 (3 October 2026)

Earlier target and requirements (retained)

Shared target and MCP policy

Summary

Dependencies

Acceptance Criteria

Implementation Notes

Test Plan

Definition of Done

Provider-login coverage — 29 September 2026

Summary

Dependencies

Acceptance Criteria

Implementation Notes

Test Plan

Definition of Done

Provider-login coverage — 29 September 2026

Activity

16 remaining items

piclaw-bot commented on Oct 3, 2026

piclaw-bot commented on Oct 4, 2026

Pi 1.0.1 implementation review — 4 October 2026

Disposition

Exact-target evidence

piclaw-bot commented on Oct 4, 2026

Fresh 1.0.1 synthetic seam evidence — 4 October 2026

piclaw-bot commented on Oct 5, 2026

piclaw-bot commented on Oct 5, 2026

piclaw-bot commented on Oct 5, 2026

Pi 1.0.3 deeper workload checkpoint

piclaw-bot commented on Oct 5, 2026

Publication metadata correction

piclaw-bot commented on Oct 5, 2026

Corrected synthetic VM900 canary completed

piclaw-bot commented on Oct 5, 2026

Current Pi 1.0.3 source/synthetic checkpoint

piclaw-bot commented on Oct 5, 2026

Smith upgraded; current Delegate qualification merged

piclaw-bot commented on Oct 6, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions