Repository navigation
Refresh stable Harness and streaming-fork evidence for Earendil 0.99.1 #1452
Description
Activity
Independent source/evidence execution starts in isolated worktree /workspace/piclaw-worktrees/1452-harness-evidence at e27f640. Dependencies #1443/#1445 are merged. Add a distinct exact0.99.1 public declaration/runtime and streaming-fork receipt; preserve historical0.87.0/0.87.1 evidence, retain partial/unsupported HC limits and keep production Harness/Pico3 activation false. Source-only while UX owns the heavy test window; no credentials/provider calls/deploy/restart.
Correcting premature closure: #1452 has no commit/PR or passing execution receipt yet. Source/test preparation is in progress, validation waits for the reserved heavy-slot handoff. Keep open until exact0.99.1 declaration/runtime, semantic and streaming-fork receipts are verified and merged.
Verified complete and merged: PR #1467 at8bee1696892925bf8c454e47b61728acb319d510, GitHub full5872/7skip/0+25feature+9web plus browser/install smoke; final128/2096 focused, Node/Bun15unique/30each, historical digest preservation, inert authority unchanged. No production Harness activation.
Pi 1.0.0 reassessment — 1 October 2026
Pi 1.0.0 reassessment: this completed exact-0.99.1 assessment stays CLOSED and its receipts remain unchanged. 1.0.0 removes the old public Harness/session/storage/testing paths; old HC results cannot transfer. New architecture/HC-PC crosswalk: #1493; new Bun storage/fork/semantic evidence: #1494. New Memory watch is measured only for one configure frame/stop, not full parity.
Rui selected exact Pi 1.0.0 for remaining work after stabilisation checkpoint 958ac18. This completed issue and its exact-0.99.1 receipts remain unchanged historical evidence. New current-loop admission/migration is #1492; target-specific MCP/provider/Delegate deltas #1495; removed Harness/Pico3 successor design/qualification #1493/#1494. No result is relabelled, no reopening or deployment/activation waiver.
Summary
Measure exact-target compatibility without activating the experimental/stable upstream Harness in production.
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
Acceptance Criteria
Implementation Notes
Use existing runtime/src/service-effects/earendil-harness-v3-compatibility manifest/preparation boundary and docs/design/earendil-agent-harness-integration-adr/evidence. Historical PRs #1383/#1385 and their 28/340 + streaming fixtures are baseline receipts, not new validation.
Estimate: M · Risk: medium · Source file:
runtime/src/service-effects/earendil-harness-v3-compatibility/manifest.tsSource anchors: Piclaw baseline, upstream release, MCP guide, public extension options.
Test Plan
Definition of Done