You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Keep all pi-durable work out of scope. Design approval is recorded; no qualification/implementation/activation enters this mainline-adoption track.
Require passing AUTH-01–08 evidence from Qualify provider login, refresh and logout for Pi 1.0.3 #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.
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.
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.
Require passing AUTH-01–08 evidence from Qualify provider login, refresh and logout for Pi 1.0.3 #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.
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.
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 nowazure; 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
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
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:
958ac185255840ee4f800becc5f7e3111ef9acdaonfeat/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.Summary
Collect final offline, UI and authorised server receipts for the exact combined candidate before any production cutover.
Parent: #1442
MCP contract: #1444
Dependencies
Acceptance Criteria
Consume fresh 1.0.0 admission/current-loop migration Admit exact Pi 1.0.0 and migrate current-loop removed import boundaries #1492 and auth/MCP deltas Qualify Pi 1.0.2 provider, MCP and Delegate integration deltas #1495. Historical Admit exact Earendil 0.99.1 packages and public SDK contracts #1443–Preserve MCP lazy lifecycle, deadlines, abort and disposal #1448/Refresh stable Harness and streaming-fork evidence for Earendil 0.99.1 #1452/Assess Earendil 0.99.1 Pico3 deltas without production adoption #1453 passes are baseline evidence only.
Qualify the approved selectable-engine scope without requiring adapter removal Assess conditional adapter removal after Pi 1.0.2 native MCP parity #1454. Unavailable native capabilities remain explicit and fail closed; no acceptance waiver inferred.
Keep all pi-durable work out of scope. Design approval is recorded; no qualification/implementation/activation enters this mainline-adoption track.
Require passing AUTH-01–08 evidence from Qualify provider login, refresh and logout for Pi 1.0.3 #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:
MakefileSource 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
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.3 #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 for Pi 1.0.3 and the selected MCP engine 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.3 #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:
MakefileSource anchors: Piclaw baseline, upstream release, MCP guide, public extension options.
Test Plan
Definition of Done
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.