pi-daddy 0.28.0 → 0.32.0

package/PRODUCT-GUIDE.md

@@ -1,155 +0,0 @@
-# Work and learning in Pi
-
-This guide targets **pi-daddy 0.28.0** with **skill-harness 0.17.0**. Completed ledger history now has
-visible hidden counts and an h + Enter toggle. Existing installed-skill discovery remains unchanged.
-Release qualification and publication are recorded in the release PR; version metadata alone is not proof.
-The [current requirement register](./REQUIREMENTS.md) separates implementation from release evidence.
-From an installed shell command, `pi-daddy guide` prints this guide; `pi-daddy current` prints the register.
-
-## Start once
-
-After the patch is published, install it with Pi's normal package manager:
-`pi install npm:pi-daddy@0.28.0` and `pi install npm:skill-harness@0.17.0`.
-Do not treat these planned version commands as evidence the packages are already available.
-Start a **fresh Pi session** after upgrading the harness: its existing immutable bridge survives `/reload`.
-The extension starts with local governance, observation and the timeline on; `/grants init` remains an optional way to save an explicit project ceiling, not a bootstrap requirement. Run `/grants` to see the root's observed tool ceiling and usable definitions.
-Enabled installed runtime skills are used in place, using Pi's package filters and config directory.
-No `.pi/skills/` copies are created for them. Existing local overrides and `.pi/grants.env` are preserved;
-review old copies before removing one to follow installed package updates. Unregistered npm packages retain
-legacy copy scaffolding. This works for any runtime skill package; there is no Principal-specific policy.
-A definition without `allowed-tools` remains unavailable until its author declares a ceiling.
-Select an available authenticated Pi model; this product never copies credentials or chooses a fallback.
-
-## Declare, run, inspect
-
-1. **`/grants work new`** asks for an overall outcome, then one to eight tasks. Each task has its own
-   outcome/instructions, agent definition (or **No tools**), explicit model and requested effort.
-2. Choose which earlier tasks each task depends on, then the maximum parallel agents (one to eight).
-   No dependencies means independent work; a chain expresses sequential work. Review and save.
-   **Saving does not run anything.** Text is retained in owner-only local files, not governance ledgers.
-3. In Herdr, **`/grants host`**, then **`/grants dashboard`**, connects the existing owner to a right panel
-   without moving focus. The plugin/install handshake and actual Pi pane ownership still apply.
-4. **`/grants work run`** shows the exact setup and bounds, then asks before launching. Every child goes
-   through the original delegation/grant/approval/executor path. Failed predecessors block only their
-   dependent branch. Complete predecessor output is handed over only within the 32 KiB bound; it is
-   never silently truncated. Child deadlines/output limits and the subtree budget remain enforced.
-5. **`/grants work results`** opens retained output. Editor changes are discarded; control characters are
-   escaped. A digest mismatch is an error, not permission to substitute another artifact.
-
-The run is finite, with no automatic retry or restart recovery. Esc requests cancellation and waits for
-original children to settle. Ordinary model work has **no universal dollar/token cap**; provider usage is
-not invented from output size. Effort is an observed/requested launch setting, not measured internal thought.
-
-## Activity timeline
-
-When the extension runs, pi-daddy records a local activity timeline by default at
-`.pi/pi-daddy/activity.jsonl`. It shows separate parent turns, governed child lifecycles, observed
-skill-file availability/reads, and declared runtime-skill lifecycle. A compatible Herdr plugin opens one
-right-side panel per parent tab without taking focus; `/grants dashboard` remains the visible Pi fallback
-when Herdr/panel setup is unavailable. `PI_DADDY_GOVERNANCE=off` is the visible governance opt-out;
-`PI_DADDY_ACTIVITY_TIMELINE=off` stops observation; and
-`PI_DADDY_ACTIVITY_CONTENT=metadata-only` stores only digest/size metadata for new prompts/final answers.
-Those choices do not silently add grants, tools or child authority.
-
-The dashboard's Everything / Agents / Skills / Needs-you filters and `h` history toggle are keyboard
-controls. Press `d`, then use `p <root-id:task-id>` or `f <root-id:task-id>` exactly as shown on the row
-to load the exact local finalized user message or final response after path, size and digest checks. A bare
-task id is refused so simultaneous roots cannot select each other's private content. Pi exposes the finalized user message, not a separate
-pre-transform editor buffer, so entered-text provenance is explicitly unavailable rather than guessed. A skill being available, read, or declaring itself active
-are distinct facts; none proves compliance. Runtime skills can honestly report declared state with
-a generic `activity_lifecycle` call; it adds no authority.
-
-## Inspect the read-only execution ledger
-
-The ledger dashboard (`pi-daddy-dashboard --ledger <path>`, without a connected host or daily inputs)
-shows the latest three quiet roots per workflow and in the ungrouped tree, plus the latest two quiet
-children per parent. Hidden roots have a visible count; hidden child subtrees retain their count.
-Type `h`, then Enter, to expand all completed history; repeat to collapse. Active, failed, refused
-and incomplete branches and their ancestors always stay visible. `d`, then Enter, toggles governance
-details independently. These controls only change the display, and reset when the dashboard restarts.
-
-## Read and steer the panel
-
-The outcome comes first, followed by **Running**, **Waiting**, **Needs you** or **Finished**. Active rows
-show observed model/effort; unknown observations stay unknown. Completed attempts are collapsed.
-**Finished is not accepted.** In this connected daily panel, `d` opens diagnostics and attempt history. There are no guessed percentages or ETAs.
-
-Enter a displayed **number** for its action. A repaint never gives an old number a new meaning; stale
-choices refuse. Feedback distinguishes acknowledgement, applied control, pending and unknown results.
-Pause stops new admission, not active children. Pending bounded tasks wait for resume. Stop-agent targets
-one original active handle and does not cancel siblings. A pause racing an approval can still refuse that
-attempt at the original boundary; it is not automatically retried. Reads/redraws never request work.
-
-**`/grants work`** also selects saved setups or the task for ordinary `delegate`, changes priorities,
-and records scope revisions or alternatives. Live changes use the existing owner's validation/CAS.
-Topology changes require new work; active runs are never rebound. A selected-scope change prevents the
-old bounded order's remaining children from starting. **`/grants host stop` refuses while paused: choose
-Resume new work in the original dashboard first.** Busy/pending controls must finish or be explicitly
-reconciled first. Unknown acknowledgements keep the host for readback; stop never silently releases them.
-Ending the whole Pi session disconnects the host, but does not reconcile unknown effects. A successful
-stop preserves evidence, not a recoverable controller, and cancels no child. **Disconnected** means live
-actions are unavailable, not that children stopped.
-
-For shell inspection only: `pi-daddy work list` and `pi-daddy work show` (`--dir` is optional).
-The existing `pi-daddy work add --id … --outcome …` single-obligation entry point remains supported.
-
-## Learn deliberately; earn interruptions separately
-
-1. **`/grants learning`** creates or explicitly connects a local learning workspace for this exact work
-   snapshot, archive, population and author. Scope changes require a new explicit connection, not reuse.
-2. Start the daily host, then choose **Retain current work for learning**. This captures actual P01
-   observations and binds the real resulting case batch. An empty batch remains empty.
-3. Open the guided learning review. Review retained cases; connect qualified retained comparisons;
-   inspect **all** comparison artifacts. Record an explicit durable quality choice **before** revealing
-   model/cost. Artifact contents themselves may reveal identity; prior excerpt feedback remains prior
-   feedback, never a full-artifact or fresh-blind judgment.
-4. Record **adopt / reject / defer** separately. Quality preference is neither adoption authority nor
-   activation. Missing evidence, unresolved cases and unavailable artifacts have explicit defer reasons.
-5. The harness's **Trust / independent labels** forms freeze a scoped population/policy and separately
-   obtain independent case and unflagged-sample labels. A nomination, success exit or human click is not
-   calibration. Unconfigured/insufficient/stale trust remains silent or deferred; attention is not reset.
-
-Deliberate review does **not** reserve earned automatic exposure. For an automatic closing request use
-`/grants host closing`, pause new work and settle/cancel active children. The panel offers retained case
-cards only under the original presence/quiescence/trust/attention rules. A visible acknowledgement is
-separate from preparation. If trust changes, explicitly resume new work, then stop/start the host to bind
-the original configured trust store; its retained attention is reused, never refilled.
-
-## Adopt settings for later orders
-
-Under **`/grants learning` → Adoption / rollback for next orders**, create the scoped registry and prepare a named
-model/effort profile. This records candidate bytes, **not evidence that they are better**. A qualified
-comparison must bind that exact candidate digest to real outputs and its actual original hypothesis/case.
-Use the guided review to link those retained origins; missing qualifying data remains a scoped defer.
-
-**Activate adopted comparison** configures that binding, separately asks for independent current
-eligibility and exact activation consent, then applies the original registry and links its real receipt.
-Only model/effort for the same task IDs and definition names can vary. Task instructions, topology,
-capabilities and assessment meaning cannot expand through this profile. Normal definition-digest/approval
-checks still run; this does not freeze definition files or the project tree. Fixed-policy contracts are unchanged.
-Subsequent bounded `/grants work` runs ask for fresh eligibility and pin the profile; active/old runs never
-migrate. Ordinary direct `delegate` calls keep their explicit caller configuration. After selecting different work,
-this menu explicitly reconnects that scope's saved settings or creates a fresh baseline; old stores remain.
-
-**Roll back active adoption** shows the immutable restore digest and each task's exact retained model/effort
-before separate consent for next orders. With nested adoptions, this is the previous profile, not necessarily
-baseline. Missing or inconsistent registry lineage refuses instead of substituting a named profile.
-If effect and learning linkage separate on failure, **Recover learning link** reconnects the original
-registry observation without replaying activation/rollback.
-
-After actual adopted work, **Link observed result from latest adopted order** shows real retained bytes,
-asks for an independent outcome/note, previews its scoped classification and confirms the link.
-**Unknown** is valid. Acceptance stays absent; runtime completion is not confirmed quality, calibrated
-improvement or automatic rollback. More extensive independent observation entry is available in the harness.
-
-## Boundaries and local state
-
-`.pi/work-setups/` holds private setup history; `.pi/work-current.json` selects work;
-`.pi/learning-workspace.json` and `.pi/work-policy-registry.json` are navigation/binding records, not authority.
-`.pi/work-registry-bindings/` preserves settings-store bindings per work scope.
-Original bounded run/control stores live under the operator's local state directory; `.pi/work-last-run.json`
-locates the most recent result. Do not hand-edit these records. Invalid/aliased/mismatched bytes refuse.
-
-This governs **Pi's tool surface**, not a hostile process or same-UID actor. `bash` can escape governance;
-workspace routing is not OS containment. Human authority, genuine labels, calibration and later outcomes
-must actually exist. The UI cannot manufacture them, and this guide does not claim they have been obtained.

package/REQUIREMENTS.md

@@ -1,41 +0,0 @@
-# Current producer requirement register
-
-**Release candidate:** pi-daddy **0.28.0**, paired with planned skill-harness **0.17.0**, implementing the
-2026-09-14 proposal. This is current product scope, not an npm/release receipt or a replacement for dated
-evidence. Read [PRODUCT-GUIDE.md](./PRODUCT-GUIDE.md).
-
-| Requirement | Supported entry point / implementation | Boundary / remaining evidence |
-| --- | --- | --- |
-| Outcome-first side panel; Running/Waiting/Needs you/Finished/Disconnected | `/grants host`, `/grants dashboard`; `daily-panel`, existing host/socket | Actual owner/observations only. Unknown model/effort stays unknown. Full diagnostics/history under Details. |
-| Real available steering and acknowledgement | Numbered exact-frame choices; pause/resume, original-child cancellation, explicit capture and closing | Repaint cannot remap a number. Stop refuses outstanding pause/pending/unknown control; resume first. No action on reads; no recovered controller; pending/unknown is not applied. |
-| Normal multi-task authoring/selection | `/grants work new`, `/grants work`; `work-setup` P01 builders and private retained text | 1–8 tasks, explicit dependencies/model/effort/concurrency. No ledger JSON authoring. Legacy single-work and ordinary delegate/all/chain remain. |
-| Scope/alternative/priority changes | Work menu → existing daily intent owner/CAS; selected-task binding for direct delegate | Topology changes need new work. Instructions/configuration may be deliberately revised; permission semantics do not widen. Active orders never rebind. |
-| Bounded parallel/dependent work and results | `/grants work run`, `/grants work results`; `work-run`, original `runOneDelegation` | Subtree budget, 1–8 concurrency, original child timeout/output/approval/grant guards. Failed dependencies block their branch. Pause waits; no retry/relaunch, no ordinary dollar/token cap. |
-| Public retained learning and scope-bound trust | `/grants learning` → existing harness workspace/wizard via original bridge | Raw selected snapshot digest + archive/population/author pinned. Deliberate review is not earned exposure. Actual labels/calibration may be absent. |
-| Full quality choice before model/cost reveal | Harness full-artifact editor, durable quality choice, separate reveal | Prior excerpts/previously exposed content remain limited evidence. Human full review/preference has not been fabricated by implementation. |
-| Distinct adopt/reject/defer; next-order settings | Learning → Adoption / rollback; `ordinary-work-policy-v1` and original adoption predicates/control journals | Exact model/effort candidate only; unchanged definition names/task IDs/scope/assessment; not a definition-file/tree pin. Current confirmed cases/origin/choice/adopt intent plus independent eligibility/activation required. No false fixed-policy profile. |
-| Rollback, pinning and later observations | Next-order registry → actual receipt linkage/recovery; latest adopted-order output observation | Rollback consent shows the retained restore digest and every task model/effort. Activation/recovery preserve exact original request/adoption proof. Old runs keep original pins. Real confirmed outcomes require independent consent; unknown is valid. No inferred acceptance, calibration, automatic rollback or efficacy. |
-| Installed guide/public contracts | `pi-daddy guide` / `current`, package root/subpath exports and Pi extension | Existing frozen governance/retention/fixed-policy contracts and historical fixtures are preserved. No new runtime dependency or Principal-specific policy. |
-
-## Evidence status and release gates
-
-Implementation is present in source. Focused regression files accompany setup, scheduler, panel/action
-binding, original late-admission guard, learning composition and additive registry. Legacy diagnostic view
-fixtures remain checked through `renderDailyDetails`; ordinary `renderDailyView` is the concise panel.
-
-**Producer runtime is Sol-approved; feature PR #52 merged with green CI at
-`b974963a7d0ba5a74fdafe331356c348a1fba565`. Release PR CI/merge, installed cross-package/Herdr
-qualification and publication remain pending coordinator gates.** A narrow type/build/unit or
-bridge check is not evidence of live model quality, calibrated trust, actual adoption/rollback or later
-production improvement. Exact candidate/check receipts belong with the delivery evidence, not invented
-inside this portable register.
-
-No model experiments, nested review agents, mutation programme, global install, release or historical
-evidence rewrite is required by this implementation step. Existing CI/ordinary behavioral checks remain.
-
-## Data that must be real
-
-A comparison without qualified retained outputs/original linked evidence is deferred. A trust policy
-without sufficient independent scoped labels stays silent/deferred. A setting without independent current
-eligibility/approval does not activate. A later outcome without an actual adopted run and retained bytes
-stays unavailable/unknown. These are explicit operational states, not invitations to supply fake data.

package/contracts/daily-view/v1/README.md

@@ -1,114 +0,0 @@
-# P04 daily read-model v1 — input for P07/P08
-
-Implemented candidate, local only. Independent overall review and formal acceptance remain pending.
-This is an actual read-only path through the existing `pi-daddy-dashboard` CLI/Herdr plugin, not a control
-API or an accepted-work counter derived from archive exits. P05 targeted control remains unavailable here.
-
-The authority snapshot has its OWN identity namespace, distinct from the selected work snapshot.
-Current/stale applicability derives from actual P01 claim/selection/matched-receipt validation, not equality
-of those IDs/digests. Missing authority and superseded/mismatched receipts cannot carry acceptance forward.
-The real walking P01 fixture with distinct identities is covered; P01 validation itself is unchanged.
-
-## Pinned P03 input, independent P01 authority
-
-`p03/` vendors exact immutable Git blobs from skill-harness
-`a311df8c991108ada7b6f4b901332232a78e9a44`. `p03/provenance.json` records paths/SHA256. Those schema/fixture
-bytes are unchanged. Input version is exactly `execution-archive-projection-v1`; the reader rejects other
-versions, duplicate JSON members/execution identities, contradictory terminal shapes and lossy numeric
-forms. It supports the adapter's emitted integer-token subset. P03 is always partial/not-assessed.
-
-Work intent is rebuilt with existing `projectWorkLedger` from separately configured strict work-v4 bytes.
-Exact selected scope/obligation revisions and occurrence bindings attach attempts by **executionId**, not
-child names, output labels, file tails, sessions or timestamps. Claimed P03 runtime and P01 runtime remain
-separate; disagreements are diagnostic. P03 conflicts neither grant nor revoke independently supplied P01
-acceptance. All active branches remain null, even if P01 labels or P03 reported sessions contain other hints.
-
-Only a genuine host supplies `workContext` to `readDailyView`/`dashboardFrame`. The reader detaches it before
-I/O and invokes P01 validation; it never manufactures decisions/availability from claims or loads authority
-from a file/environment variable. Missing authority or authority for another selection means unresolved
-acceptance, not zero completed work. Accepted results are explicitly **under supplied snapshot authority**,
-not fresh native approval. The host must independently establish availability/authority when resupplying it.
-
-## Existing view path
-
-The existing plugin command still calls `runDashboard`. Operator-only read settings are forwarded by its
-existing open/reuse seam (no new plugin, worker hook or installation flow):
-
-- `PI_DADDY_ARCHIVE_PROJECTION`: exact P03 snapshot file.
-- `PI_DADDY_WORK_LEDGER`: exact separate work-v4 file.
-- `PI_DADDY_WORK_SNAPSHOT`: JSON containing P01's exact `{snapshot:{id,digest},event:{eventId,digest}}` selection.
-  This is selection **only**, never authority. Pane reuse keys include these settings and their CWD.
-
-CLI equivalents are `--archive-projection`, `--work-ledger`, `--work-snapshot`, plus `--once --no-color` or
-`--once --daily-json`. No new files are discovered, installed or written by a status read. Legacy dashboard
-behavior is unchanged when no daily input is configured. Existing core/plugin protocol validation remains.
-Without a programmatic host-authority context the CLI intentionally cannot show authoritative acceptance.
-
-```ts
-import { readDailyView, createDailyViewReader } from 'pi-daddy/daily-view';
-const read = createDailyViewReader(); // session-local gap metadata, not an authority store
-const view = await read({ archiveProjectionPath, workLedgerPath, workContext: independentlyVerifiedP01Context,
-  sourceManifestFiles: policyAuthorizedManifestPathsBySha256 });
-// renderDailyView(view) is exported from the package root; dashboardFrame({cwd, dailyView: options})
-// invokes the same reader/render path. Rendering an arbitrary caller object is not validation.
-```
-
-## Output contract
-
-`version: "pi-daddy-daily-view-v1"`, `readOnly:true`, `freshness:"snapshot-unknown"`, `coverage:"partial"`.
-Public TypeScript types: `DailyView`, `DailyObligation`, `DailyAttempt`, `DailyViewOptions` in `src/daily-view.ts`.
-The deterministic `fixtures/view.json` and `fixtures/view.txt` are emitted by the actual reader/renderer.
-
-- `scope` is an exact P01 revision or null; `selectedSnapshot` retains the exact selection references.
-- `scopeState`, `authority`, and nullable `progress` are independent of runtime counts. Authority is
-  unavailable, stale-for-selection, or supplied-host-context. Obligations include intent/policy revisions,
-  acceptance, unstarted/attached activity, artifact/evidence coverage, matched receipt IDs, claim sources
-  and obstacle codes. IDs are shown because work-v4 has no verified human description text here.
-- `attempts` preserves exact execution identity, P01 logical child/runtime and separate validated P03 row
-  (parents/public calls/archive IDs/reported sessions/outcome/issues). Reused child names stay separate.
-  `activeBranch` is always null. An archive exit0, including failed-control exit0, is never acceptance.
-- `sourceAvailability` requires actual caller-authorized bytes matching each SHA256. No projection-supplied
-  path/URL is read. Missing mappings/deleted files are missing; mismatches/errors are not recovered facts.
-  Raw-manifest availability does not independently revalidate native transcript/check blobs or provenance.
-- Check/evidence detail comes from P01's authority-aware coverage/receipt matching. P03 v1 has no named-check
-  receipt byte payload; that gap is printed, not inferred from a terminal result or an absent issue string.
-- `sources` reports read/missing/error/unconfigured and exact file hashes. `issues` and `narrative` carry
-  deterministic coverage/obstacle explanations. No raw invalid input/error excerpts are rendered.
-
-Reads are bounded regular non-symlink descriptor snapshots (4 MiB P03, 16 MiB work; at most 128 explicitly
-mapped 64 KiB source manifests). Descriptor/path changes during read become errors. Every refresh rereads
-rather than extending a cached execution history. Missing/error frames do not retain old runtime rows.
-Reconnect produces a resnapshot and sticky gap label, never invented continuity. A new process starts with
-an initial snapshot, not recovered history. Mtime is only a consistency check, never freshness or branch
-proof. Rendering strips terminal control characters and caps lines/columns with visible omissions.
-
-## Supported and BLOCKED scope
-
-Supported: deterministic file-backed read-only view, real CLI and freshly isolated compiled plugin-command
-execution, plus fixture transport wiring through the existing plugin open seam. No worker/model/native-gate
-call is needed. Repeated reads preserve session/control bytes and message counts; disconnected/unavailable
-models do not prevent useful status. Model connectivity itself remains unknown, not falsely "connected".
-
-**BLOCKED live qualification:** no deployed P03 live archive policy/subscription or actual passive live
-transport freshness was supplied. No live Herdr pane/worker observation is claimed; no terminal read,
-scroll, monitoring prompt or control message was used. Installed smoke is separate from isolated compiled
-checks. Full native session/active-branch gaps from P02 and P06's arbitrary-shell/shared-write/aggregate
-CPU-memory-PID-money limitations remain. No accepted packet, fresh source, steering, dispatch or recovery
-can be inferred from the daily view. P07/P08 must preserve these distinctions.
-
-## Fixtures and reproduction
-
-The fixture combines three fixed P01 obligations, two independently reconstructed fixture decisions and
-one exited-but-unaccepted obligation with the exact six-row P03 fixture. P01's known branch labels are
-explicit **test-world declarations**, not authentication of P03's unknown live branches. No authority is
-constructed from incoming wire claims. Separate tests cover unstarted work, missing evidence, changed
-scope/stale authority, unavailable sources, reconnect gaps and read-only repeated operation.
-
-```sh
-node --test packages/pi-daddy/test/daily-view.test.ts
-node packages/pi-daddy/scripts/generate-daily-view-fixture.ts --check packages/pi-daddy/contracts/daily-view/v1/fixtures /absolute/owned/scratch-parent
-```
-
-The generator is repository fixture tooling, imports read-only and writes only explicit owned scratch/new
-targets. Check does not change published fixtures; scratch is retained for inspection. No install, model
-call, per-task review loop, mutation machinery or automatic authority/store update is involved.