Assess Earendil 0.99.1 Pico3 deltas without production adoption

[piclaw-bot]

Summary

Refresh the bounded experimental assessment separately from the runtime/MCP replacement.

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 Admit exact Earendil 0.99.1 packages and public SDK contracts #1443

Acceptance Criteria

• Record exact 0.99.1 public exports/declarations and changes since the historical 0.87.0/0.87.1 assessment.
• Reassess permit/drive versus shipped send/resume, persistence, cancellation, process host and durable ownership requirements using fake-provider fixtures only.
• Preserve unsupported/unverified HC/PC classifications where evidence is absent; no production import/activation or authority transfer.
• Keep EF-S01/02/05/07/08 and AgentProjectionSink contracts Piclaw-owned and state the go/no-go for any further bounded spike.

Implementation Notes

Historical PR #1386: bounded fake-provider spike go; production adoption no-go. Serialized commits/checkpoints/leases/watch APIs do not prove distributed host authority or durable transport sequencing. Preserve historical evidence and retain rollback scope.

Estimate: S · Risk: medium · Source file: docs/design/earendil-agent-harness-integration-adr/evidence

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

Test Plan

• Disposable exact-target declaration/source/packed-surface probes with fake providers and isolated time.
• Negative production activation and host-authority assertions.

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

[piclaw-bot]

Execution starts in isolated audit/1453-pico3-evidence at e27f640. Exact0.99.1 public experimental barrels retain0.87.0 hashes, but tagged-source comparison finds Chord legacy-tracker/session/view changes. Reassess with public fake-provider Memory/JSONL, transaction/watch, send/resume and cancellation/reopen fixtures; preserve historical record and unsupported SQLite/cross-process host authority. No production imports/activation, live auth/provider or deployment.

[piclaw-bot]

Correcting premature automatic closure: prepared exact0.99.1 Pico3 fixtures are locally24/917 green (including boundary/core checks), but there is no committed PR or full-gate receipt yet. Keep open until reviewed exact-target evidence is published and merged. No production adoption.

[piclaw-bot]

Verified#1453 evidence complete: PR#1468 merged after green exact-head GitHub CI. Local5886/7skip/0+25+9; focused60/1002 and finalPico14/88, Node/Bun public receipts, no production adoption. Unsupported/unverified authority limits preserved.