pi-daddy 0.49.5 → 0.51.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (160) hide show
  1. package/CHANGELOG.md +57 -1
  2. package/README.md +231 -27
  3. package/dist/governance/initiative-coordinator.d.ts +63 -0
  4. package/dist/governance/initiative-coordinator.d.ts.map +1 -0
  5. package/dist/governance/initiative-coordinator.js +364 -0
  6. package/dist/governance/initiative-coordinator.js.map +1 -0
  7. package/dist/governance/initiative-effects.d.ts +20 -0
  8. package/dist/governance/initiative-effects.d.ts.map +1 -0
  9. package/dist/governance/initiative-effects.js +108 -0
  10. package/dist/governance/initiative-effects.js.map +1 -0
  11. package/dist/governance/initiative-state.d.ts +13 -0
  12. package/dist/governance/initiative-state.d.ts.map +1 -0
  13. package/dist/governance/initiative-state.js +122 -0
  14. package/dist/governance/initiative-state.js.map +1 -0
  15. package/dist/governance/operation-artifact-io.d.ts +8 -0
  16. package/dist/governance/operation-artifact-io.d.ts.map +1 -0
  17. package/dist/governance/operation-artifact-io.js +95 -0
  18. package/dist/governance/operation-artifact-io.js.map +1 -0
  19. package/dist/governance/operation-artifact-scan.d.ts +13 -0
  20. package/dist/governance/operation-artifact-scan.d.ts.map +1 -0
  21. package/dist/governance/operation-artifact-scan.js +71 -0
  22. package/dist/governance/operation-artifact-scan.js.map +1 -0
  23. package/dist/governance/operation-artifacts.d.ts +53 -0
  24. package/dist/governance/operation-artifacts.d.ts.map +1 -0
  25. package/dist/governance/operation-artifacts.js +309 -0
  26. package/dist/governance/operation-artifacts.js.map +1 -0
  27. package/dist/governance/runtime-settlement.d.ts +2 -0
  28. package/dist/governance/runtime-settlement.d.ts.map +1 -1
  29. package/dist/governance/runtime-settlement.js +26 -0
  30. package/dist/governance/runtime-settlement.js.map +1 -1
  31. package/dist/governance/workspace-acceptance.d.ts +5 -0
  32. package/dist/governance/workspace-acceptance.d.ts.map +1 -1
  33. package/dist/governance/workspace-acceptance.js +16 -0
  34. package/dist/governance/workspace-acceptance.js.map +1 -1
  35. package/dist/index.d.ts +8 -0
  36. package/dist/index.d.ts.map +1 -1
  37. package/dist/index.js +8 -0
  38. package/dist/index.js.map +1 -1
  39. package/dist/kernel/dashboard-observation.d.ts +76 -0
  40. package/dist/kernel/dashboard-observation.d.ts.map +1 -0
  41. package/dist/kernel/dashboard-observation.js +49 -0
  42. package/dist/kernel/dashboard-observation.js.map +1 -0
  43. package/dist/kernel/dispatch-operation.d.ts +2 -0
  44. package/dist/kernel/dispatch-operation.d.ts.map +1 -1
  45. package/dist/kernel/dispatch-operation.js.map +1 -1
  46. package/dist/kernel/initiative.d.ts +94 -0
  47. package/dist/kernel/initiative.d.ts.map +1 -0
  48. package/dist/kernel/initiative.js +38 -0
  49. package/dist/kernel/initiative.js.map +1 -0
  50. package/dist/kernel/operation-artifact.d.ts +49 -0
  51. package/dist/kernel/operation-artifact.d.ts.map +1 -0
  52. package/dist/kernel/operation-artifact.js +4 -0
  53. package/dist/kernel/operation-artifact.js.map +1 -0
  54. package/dist/kernel/principal-binding.d.ts +4 -0
  55. package/dist/kernel/principal-binding.d.ts.map +1 -0
  56. package/dist/kernel/principal-binding.js +94 -0
  57. package/dist/kernel/principal-binding.js.map +1 -0
  58. package/dist/kernel/project-paths.d.ts +6 -0
  59. package/dist/kernel/project-paths.d.ts.map +1 -1
  60. package/dist/kernel/project-paths.js +12 -0
  61. package/dist/kernel/project-paths.js.map +1 -1
  62. package/dist/kernel/selected-definitions.d.ts.map +1 -1
  63. package/dist/kernel/selected-definitions.js +5 -91
  64. package/dist/kernel/selected-definitions.js.map +1 -1
  65. package/dist/kernel/workspace-diagnostics.d.ts +24 -0
  66. package/dist/kernel/workspace-diagnostics.d.ts.map +1 -0
  67. package/dist/kernel/workspace-diagnostics.js +81 -0
  68. package/dist/kernel/workspace-diagnostics.js.map +1 -0
  69. package/dist/products/activity-storage.d.ts +2 -0
  70. package/dist/products/activity-storage.d.ts.map +1 -0
  71. package/dist/products/activity-storage.js +119 -0
  72. package/dist/products/activity-storage.js.map +1 -0
  73. package/dist/products/activity-timeline.d.ts +4 -0
  74. package/dist/products/activity-timeline.d.ts.map +1 -1
  75. package/dist/products/activity-timeline.js +12 -0
  76. package/dist/products/activity-timeline.js.map +1 -1
  77. package/dist/products/dashboard-cli.d.ts +2 -0
  78. package/dist/products/dashboard-cli.d.ts.map +1 -1
  79. package/dist/products/dashboard-cli.js +50 -10
  80. package/dist/products/dashboard-cli.js.map +1 -1
  81. package/dist/products/dashboard-display-controls.d.ts.map +1 -1
  82. package/dist/products/dashboard-display-controls.js +72 -2
  83. package/dist/products/dashboard-display-controls.js.map +1 -1
  84. package/dist/products/dashboard-file-cache.d.ts +10 -0
  85. package/dist/products/dashboard-file-cache.d.ts.map +1 -0
  86. package/dist/products/dashboard-file-cache.js +38 -0
  87. package/dist/products/dashboard-file-cache.js.map +1 -0
  88. package/dist/products/dashboard-layout.d.ts +6 -0
  89. package/dist/products/dashboard-layout.d.ts.map +1 -0
  90. package/dist/products/dashboard-layout.js +45 -0
  91. package/dist/products/dashboard-layout.js.map +1 -0
  92. package/dist/products/dashboard-panels.d.ts +10 -0
  93. package/dist/products/dashboard-panels.d.ts.map +1 -0
  94. package/dist/products/dashboard-panels.js +319 -0
  95. package/dist/products/dashboard-panels.js.map +1 -0
  96. package/dist/products/dashboard-recap.d.ts +4 -0
  97. package/dist/products/dashboard-recap.d.ts.map +1 -0
  98. package/dist/products/dashboard-recap.js +47 -0
  99. package/dist/products/dashboard-recap.js.map +1 -0
  100. package/dist/products/dashboard-screen.d.ts +14 -1
  101. package/dist/products/dashboard-screen.d.ts.map +1 -1
  102. package/dist/products/dashboard-screen.js +217 -40
  103. package/dist/products/dashboard-screen.js.map +1 -1
  104. package/dist/products/dashboard-session-client.d.ts +16 -2
  105. package/dist/products/dashboard-session-client.d.ts.map +1 -1
  106. package/dist/products/dashboard-session-client.js +64 -11
  107. package/dist/products/dashboard-session-client.js.map +1 -1
  108. package/dist/products/dashboard-settings.d.ts.map +1 -1
  109. package/dist/products/dashboard-settings.js +4 -6
  110. package/dist/products/dashboard-settings.js.map +1 -1
  111. package/dist/products/ecosystem-versions.d.ts +1 -1
  112. package/dist/products/ecosystem-versions.d.ts.map +1 -1
  113. package/extensions/activity-timeline.ts +3 -1
  114. package/extensions/artifact-bridge.ts +130 -0
  115. package/extensions/dashboard-live.ts +63 -0
  116. package/extensions/dashboard-observation.ts +39 -0
  117. package/extensions/dashboard-session-server.ts +45 -3
  118. package/extensions/dashboard-sources.ts +124 -0
  119. package/extensions/delegation-artifacts.ts +133 -0
  120. package/extensions/delegation-operations.ts +42 -13
  121. package/extensions/ecosystem-versions.ts +12 -5
  122. package/extensions/grants-command.ts +34 -6
  123. package/extensions/grants.ts +9 -20
  124. package/extensions/initiative-dashboard.ts +143 -0
  125. package/extensions/initiative-handoff.ts +59 -0
  126. package/extensions/initiative-runtime.ts +444 -0
  127. package/extensions/runtime-snapshot.ts +118 -2
  128. package/extensions/session-environment.ts +13 -1
  129. package/extensions/session.ts +28 -10
  130. package/extensions/workspace-diagnostics.ts +90 -0
  131. package/package.json +1 -1
  132. package/src/governance/initiative-coordinator.ts +416 -0
  133. package/src/governance/initiative-effects.ts +146 -0
  134. package/src/governance/initiative-state.ts +144 -0
  135. package/src/governance/operation-artifact-io.ts +103 -0
  136. package/src/governance/operation-artifact-scan.ts +77 -0
  137. package/src/governance/operation-artifacts.ts +363 -0
  138. package/src/governance/runtime-settlement.ts +28 -0
  139. package/src/governance/workspace-acceptance.ts +18 -0
  140. package/src/index.ts +13 -0
  141. package/src/kernel/dashboard-observation.ts +109 -0
  142. package/src/kernel/dispatch-operation.ts +2 -0
  143. package/src/kernel/initiative.ts +126 -0
  144. package/src/kernel/operation-artifact.ts +46 -0
  145. package/src/kernel/principal-binding.ts +104 -0
  146. package/src/kernel/project-paths.ts +16 -0
  147. package/src/kernel/selected-definitions.ts +5 -100
  148. package/src/kernel/workspace-diagnostics.ts +110 -0
  149. package/src/products/activity-storage.ts +128 -0
  150. package/src/products/activity-timeline.ts +11 -0
  151. package/src/products/dashboard-cli.ts +53 -10
  152. package/src/products/dashboard-display-controls.ts +63 -2
  153. package/src/products/dashboard-file-cache.ts +38 -0
  154. package/src/products/dashboard-layout.ts +50 -0
  155. package/src/products/dashboard-panels.ts +379 -0
  156. package/src/products/dashboard-recap.ts +48 -0
  157. package/src/products/dashboard-screen.ts +266 -43
  158. package/src/products/dashboard-session-client.ts +78 -14
  159. package/src/products/dashboard-settings.ts +4 -6
  160. package/src/products/ecosystem-versions.ts +2 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,62 @@
1
1
  # Changelog — pi-daddy
2
2
 
3
+ ## 0.51.0 — 2026-11-09
4
+
5
+ - The dashboard groups navigation, status and work waiting for a decision. Move between tasks to preview the selected one when space permits. In smaller panes, press **Enter** to open its details.
6
+ - Open a Bookie handoff from **Now**, **Work** or **Reviews** to see the parent Pi command and which output to choose. The review reference identifies the exact saved output for the settled task.
7
+ - Press **r** for a session recap or **x** in a Bookie review to inspect its source. Press **Esc** to return to the same item.
8
+
9
+ ## 0.50.0 — Unreleased
10
+
11
+ - Recognize the public `pi-bookie` package and retain legacy Bookie names in version observations.
12
+ Reload Pi after updating Daddy; suggested npm pin commands keep the selected package name.
13
+
14
+ - Keep private lifecycle state out of dashboard owner replies by emitting only the public session and
15
+ directory identity. Restart Pi after updating; circular internal state no longer breaks serialization.
16
+
17
+ - Inspect routing with `/grants workspace <id>`: distinguish saved acceptance, current grant/pin,
18
+ pending activation, moved/removed destinations and invalid worktrees. The dashboard retains a bounded
19
+ last-observed result; candidate, approvals and execution checks remain at dispatch.
20
+ - Use Pi's selected working directory for existing root grants and runtime defaults at startup/reload.
21
+ Explicit grants keep precedence; descendants with missing inherited grants no longer fall back to a
22
+ local root store. Acceptance still requires a new root session to establish a new pin; reload never repins.
23
+
24
+
25
+ - Prepare default activity storage during awaited session startup so later log/content writes do not
26
+ alter a product snapshot taken before `/grants init`. Preserve existing ignore rules, settings and
27
+ unrelated files; tracked or insufficiently excluded runtime paths report observation unavailable.
28
+ Custom locations retain their policy, and marker-free non-Git use does not require Git.
29
+
30
+ - Report settled prior-generation tasks as unclaimed after safe exclusive takeover, without changing retained attempt provenance or bypassing explicit claim and admission checks. Recovery-only, running and uncertain ownership remain non-free.
31
+
32
+
33
+ - Avoid repeating full selected-work-map scans for exact read-only owner observations when a trusted client supplies a separate current read-authority guard; all execution and mutation guards remain full.
34
+
35
+
36
+ - Keep initiative dashboard refresh display-only with bounded last-observed facts and unchanged timestamps.
37
+ Remove a duplicate selection callback while retaining the coordinator's bound authority/generation checks.
38
+ Optional display no longer repeats work-map validation during selection or execution controls.
39
+
40
+ - Retain optional exact neutral effect targets/outcomes with explicit operator-attested or owner-verified provenance.
41
+ Unknown outcomes do not reconcile effects; current target observations stay separate from historical targets
42
+ after goal/plan changes. Recovery returns the original attempt's exact receipt outcome, without registry inference
43
+ or task acceptance. Old outcome-less receipts remain readable without invented upgrade status.
44
+
45
+ - Add optional one-host initiative ownership for trusted selected work maps. Exact task association feeds the
46
+ existing durable operation admission; current grants and workspace leases remain required. Interrupted or
47
+ external-effect-unknown work blocks takeover rather than becoming a silent retry. Add recovery-only selection
48
+ and exact owner-verified receipt reconciliation without treating process settlement as external success.
49
+ - Show bounded initiative observations and improve narrow dashboard word wrapping, attention summaries and
50
+ visible page scrolling. These observations never approve work or grant authority.
51
+
52
+ - Add six bounded current-session dashboard views, shared compact/expanded selection, live metadata with capture off, and optional owner-bound producer status contributions. Stale/disconnected data stays explicitly historical; exact evidence identities do not load payloads, and review observations confer no execution authority. Models/Versions shortcuts and old-owner compatibility remain.
53
+ - Show pending/applied/refused/unconfirmed control effects, reject stale owner snapshots, and recheck the owner across awaited settings reads. Display metadata caching is bounded; redraws create no durable records or provider calls. Add safe typed artifact-read failure codes without changing legacy reasons.
54
+
55
+ - Add an optional trusted retained-artifact hint/list/read bridge and bounded current-owner enumeration. Missed notifications are recoverable without dispatch; consumer failures cannot alter a published result. Historical reads require independently rechecked consumer authority.
56
+
57
+ - Retain stable-ID attempt admission and exact visible results in private producer manifests, independently of optional diagnostics. Same-session restart resolves historical evidence without redispatching an interrupted or completed attempt; changed requests remain conflicts. Historical reads are bounded and identity checked, and never grant live authority or task approval. Partial and failed outcomes remain explicitly distinct.
58
+ - Add root-exported artifact readers, owner-bound `pi-daddy:operation-history:v1`, optional live `operation.artifact` references and small Pi custom entries for downstream consumers. Principal retains its engineering policy; its existing binding is isolated without changing ordinary inline roles.
59
+
3
60
  ## 0.49.5 — 2026-11-03
4
61
 
5
62
  - Retain native `not-started` operation evidence for non-approval admission-preview refusals, including missing workspace authority. Previously these refusals could leave a prepared coordinator attempt without a native operation record. The original typed refusal still throws; duplicate and conflicting IDs never overwrite an existing execution. After correcting authority, use the coordinator's explicit retry rather than redispatching the terminal ID. No permission or Auto setting changes.
@@ -165,7 +222,6 @@ Release candidate for review, not a stable or npm publication. Use the immutable
165
222
  usage remain. Pi 1.0.4 argument preparation validates active arguments after removing the retired cost override.
166
223
  - Live complete episode cost is explicitly unavailable in the session dashboard; historical usage remains in reports.
167
224
 
168
-
169
225
  ### Passive cost coverage
170
226
 
171
227
  - **Breaking — report JSON change:** row/group/total cost and episode-cost percentiles may be null when coverage is incomplete.
package/README.md CHANGED
@@ -19,6 +19,88 @@ request under the same ID refuses. An intentional retry needs a new attempt afte
19
19
  previous operation is proven settled or never started; uncertainty stays blocked.
20
20
  Principal 4.12.0 introduced automatic operation IDs and exact candidate/report references for this contract.
21
21
 
22
+ Stable-ID attempts also retain private producer evidence under
23
+ `<PI_CODING_AGENT_DIR>/pi-daddy/operation-results` (default agent directory: `~/.pi/agent`).
24
+ Admission is synchronized before dispatch; a restart with no published result leaves the attempt uncertain,
25
+ not safe to rerun. Exact visible finals and available visible partial output remain distinct from native
26
+ cleanup, successful work, review approval and current applicability. Diagnostics settings do not control this
27
+ required result store. No raw session, reasoning, environment or task request is captured here.
28
+
29
+ `OperationArtifactRef`, `openOperationArtifacts` and `readOperationArtifact` are available from the package
30
+ root without loading the extension, Principal or Bookie. Immutable references bind the original owner,
31
+ operation, execution, manifest hash and authored bytes. Historical reads require the selected agent directory,
32
+ check identity and confinement, and refuse missing, altered or oversized evidence. Authored content is bounded
33
+ at 4 MiB per result; manifests at 64 KiB. There is no automatic lifetime quota or deletion: the operator owns
34
+ retention and backup. Deleting evidence does not establish that an interrupted execution never started.
35
+
36
+ The live `pi-daddy:operation-status:v1` reply retains its original meaning and may add
37
+ `operation.artifact`. `pi-daddy:operation-history:v1` accepts `{version:1, requestId, sessionId, cwd,
38
+ operationId, reply}` for the currently bound session/canonical cwd only, returning `history:true`, the
39
+ historical `operation`, optional `artifact` and exact `final` or explicitly `partial` content. It never claims
40
+ live qualification or approval. Pi custom entries contain only `pi-daddy:operation-artifact:v1` references.
41
+ Bookie can register a reference afterward; a registration retry never dispatches the child again.
42
+
43
+ ## Current-session dashboard
44
+
45
+ The connected terminal dashboard has six destinations: **1 Now, 2 Work, 3 Reviews, 4 Activity,
46
+ 5 Evidence, 6 Settings**. Now shows a session-wide priority above work grouped by what needs attention.
47
+ The **>** marker follows your selection. On Now, Work and Reviews, a terminal at least 110 columns wide
48
+ also previews that item on the right. In a smaller pane, press **Enter** for the same item.
49
+ `x` opens more information and enables the preview from 96 columns. Arrow keys select, PageUp/PageDown scroll, Enter opens details,
50
+ Esc returns, and `m` Models / `v` Versions / `s` Settings remain available. Old owners and standalone
51
+ ledger views keep their compatible legacy display.
52
+
53
+ When a permission request is pending, **Now** directs you to the parent Pi session. A ready
54
+ handoff points to **3 Reviews**. Select the result and press **Enter** for the next action.
55
+ In a Bookie review, **x** reveals the source and exact reference. In **Now**, **x** reveals
56
+ component and memory details. A recorded result still needs a separate review decision.
57
+
58
+ Press **r** for a local session recap. It shows up to five recent parent events and current reported
59
+ review or permission counts when available. **Esc** returns to the same item. The recap uses
60
+ recorded session data and works without a model, JEV or network connection. A disconnected
61
+ session is marked as last observed.
62
+
63
+ Now combines an explicitly reported goal/next-step recommendation with actual parent and child
64
+ observations. Recommendations do not authorize work. Reviews show producer judgments in their stated
65
+ scope; retained output, a successful process, and an overall approved task are different facts. Evidence
66
+ shows exact technical references, never automatically restores output into context. References may contain
67
+ local names or paths. Explicit `p`/`f` reads retain one checked display snapshot until another selection.
68
+
69
+ Optional Bookie, Scout, Principal and Harness status adapters publish only bounded terminal metadata.
70
+ Absent adapters show unavailable; closed adapters, disconnected owners and observations older than two
71
+ minutes show last observed/stale. Silence is not a hang. Ordinary parent tool-name activity works with
72
+ transcripts/diagnostics disabled; no arguments, results, prompts or reasoning are captured for this view.
73
+ The small resource sample is the parent Pi process's RSS, not host health or total child memory. Native
74
+ children use the current owner's existing ledger/timeline; unrelated sessions are excluded.
75
+
76
+ Controls remain the existing authenticated owner controls. Changes show pending, applied, refused or
77
+ unconfirmed status. Unconfirmed mutations need owner inspection before retry. Auto changes current
78
+ permission handling, JEV still requires its separate paid-call/storage choices, and model/wall/idle edits
79
+ apply to future children. Running children keep captured settings. The dashboard does not implement a
80
+ new pause/cancel/stop route: use the owning Pi control, and treat a reported request as unconfirmed until
81
+ its owner reports settlement. Existing Herdr child panes stay view-only and parent controlled.
82
+
83
+ Display storage is bounded and memory-only: at most eight source updates of 4 KiB, 32 parent activity
84
+ observations, 16 recent producer-reference identities, and four metadata files of at most 2 MiB. Unchanged
85
+ metadata is cached with a one-second file-check interval; package version inventory is cached for five seconds
86
+ per owner. Versions includes optional Scout/Bookie observations and separates installed bytes from loaded
87
+ generations; a local 0.0.0 Bookie manifest is not evidence of npm publication. The view does not scan historical artifact stores,
88
+ make provider calls, or write durable records on redraw. Larger ledger files are reported unavailable in
89
+ this view rather than silently truncated into a false complete history.
90
+
91
+ The optional event `pi-daddy:dashboard-source:v1` takes a trusted
92
+ `{version:1, sessionId, cwd, producer, producerVersion, reply}` registration for the actual current native
93
+ owner and canonical cwd. A successful reply supplies `{version:1, ok:true, generation, publish, close}`.
94
+ `publish({sequence, items})` accepts strictly increasing nonnegative sequence values, no more than eight
95
+ items and 4 KiB total. Each item has `id`, `kind` (`goal`, `next`, `work`, `review`, `evidence`, `status`),
96
+ `label`, `state` (`observed`, `running`, `dependency-wait`, `approval-wait`, `cancel-requested`, `settled`,
97
+ `failed`, `unknown`, `unavailable`), optional bounded `details`, and an optional opaque display `reference`.
98
+ IDs are bounded to 160 characters, labels to 240, details to six strings of 240, and references to 512.
99
+ Replacing a producer invalidates its prior publisher even at the same version; session/lifecycle changes
100
+ invalidate all publishers. Registered extensions own refresh/closure; no callback conveys permission,
101
+ review approval, a content resolver, or executable actions. The exported TypeScript interfaces document
102
+ this seam without making other ecosystem packages mandatory.
103
+
22
104
  The dashboard shows the selected task's last observed tool event and time since that event.
23
105
  Details include the actual recorded working directory and phase where available. Silence is
24
106
  not proof of a hang, and a finished process is not an approved task. Tool observations retain
@@ -135,13 +217,13 @@ delegate({ agent: "build", task: "Implement it.",
135
217
  context: { mode: "files", files: ["src/kernel/resolve.ts"] } })
136
218
  ```
137
219
 
138
- | Mode | What crosses |
139
- | :--- | :--- |
140
- | `none` | nothing beyond the definition and the task; the default |
141
- | `files` | the contents of paths the parent names, confined to the working directory |
142
- | `pruned` | the last few turns of the parent's session, plus older turns naming those files |
143
- | `summary` | what the parent writes in its own words |
144
- | `fork` | the parent's whole session, as a fork; **gated**, so a human answers first |
220
+ | Mode | What crosses |
221
+ | :-------- | :------------------------------------------------------------------------------ |
222
+ | `none` | nothing beyond the definition and the task; the default |
223
+ | `files` | the contents of paths the parent names, confined to the working directory |
224
+ | `pruned` | the last few turns of the parent's session, plus older turns naming those files |
225
+ | `summary` | what the parent writes in its own words |
226
+ | `fork` | the parent's whole session, as a fork; **gated**, so a human answers first |
145
227
 
146
228
  A `delegate_chain` step takes the same parameter, and because a chain is planned as one unit, a gate any step
147
229
  raises is answered before the first step runs.
@@ -223,6 +305,13 @@ The timeline is enabled by default. It may store private prompt and final conten
223
305
  `PI_DADDY_ACTIVITY_CONTENT=metadata-only` (or `off`) to keep only digests, or
224
306
  `PI_DADDY_ACTIVITY_TIMELINE=off` to disable observation.
225
307
 
308
+ The default location is prepared during session startup, before product snapshots. Fresh ignore rules
309
+ cover activity/content and grants-ledger runtime files only; settings and unrelated files stay reviewable.
310
+ Existing ignore rules are preserved. Already tracked runtime data, unsafe storage paths or insufficient
311
+ exclusions report observation unavailable rather than silently changing repository policy. Custom and
312
+ transported timeline locations keep their existing policy. Non-Git roles can still record without Git;
313
+ an existing repository whose policy cannot be checked remains unavailable.
314
+
226
315
  `pi-daddy outcomes` reads Git history, optional GitHub Actions results from `gh`, and narrowly recognized corrections
227
316
  in the next recorded operator turn, then appends only changed `episode_outcome` signals. Only commits carrying a
228
317
  `Pi-Episode: <episode-id>` trailer is considered; `pi-daddy report` can display attribution only when matching episode
@@ -231,6 +320,20 @@ is `packages/pi-daddy/contracts/ledger-record/v1`.
231
320
 
232
321
  ## Workspaces and leases
233
322
 
323
+ `/grants workspace <id>` inspects one workspace without changing grants, acceptance or destination pins.
324
+ It distinguishes saved acceptance, the current routing capability, pending activation, a moved or removed
325
+ destination, and invalid worktrees. It names the selected grant directory and its source. An active route
326
+ is only a current observation: candidate, selected task/input scope, approvals, writer lease and native
327
+ settlement remain dispatch-time checks. The dashboard retains the last explicit inspection with its time
328
+ and freshness; redraw does not scan repositories or refresh authority.
329
+
330
+ Startup uses the actual Pi working directory's existing root grant and runtime defaults, even when an
331
+ embedding process started elsewhere. Explicit environment grants still win; descendants never adopt a
332
+ target directory's broader root grant. Stored directory identity remains exact: an alias does not silently
333
+ borrow or migrate another spelling's saved grant or approvals. Canonical aliases of registered workspace
334
+ destinations continue to resolve through the existing Git/worktree validator.
335
+
336
+
234
337
  A registered worktree is named `workspace:<id>` and routing a child there is a capability that attenuates like any
235
338
  other. Acceptance is trust on first use: the first session accepts and announces every id already in the registry.
236
339
  Later additions are refused until `/grants workspaces` accepts the current id set, effective next session. Each session
@@ -319,6 +422,8 @@ Same-user hostile filesystem or co-loaded-extension authenticity is outside this
319
422
 
320
423
  `pi-daddy-dashboard` shows current work and actual pending approvals first; completed history is collapsed by default.
321
424
  `/grants dashboard` opens it beside the session in a Herdr pane. The header shows Auto ON/OFF and connection state.
425
+ For a selected Bookie work map, **Now** shows a current review request. Press **3** for **Reviews** and **Enter** on the output for instructions. In the parent Pi session, `/bookie-work review` opens the saved answer. The project owns the review decision.
426
+
322
427
  Use **a** to switch Auto, arrow keys to select a row, **Enter** for details, **m** for session models, **h** for history,
323
428
  and **?** for help. The view fits the terminal and follows resize events. A disconnected control displays its state
324
429
  as unavailable until the owning session acknowledges a fresh snapshot.
@@ -357,18 +462,17 @@ replace a pin, then deliberately reload. There are no background registry checks
357
462
  **:** opens command mode, **Tab** changes the task filter, **p/f** shows retained prompt/final content,
358
463
  **Esc** returns to the previous view and **q** closes the dashboard.
359
464
 
360
-
361
465
  ## Bounds and configuration
362
466
 
363
467
  Every variable is `PI_DADDY_*`. Operator-facing controls are grouped below; the environment overrides stored
364
468
  configuration where both exist.
365
469
 
366
- | Area | Variables |
367
- | :--- | :--- |
368
- | Governance | `PI_DADDY_GOVERNANCE`, `PI_DADDY_GRANT`, `PI_DADDY_GATED`, `PI_DADDY_MAX_DEPTH`, `PI_DADDY_FANOUT`, `PI_DADDY_LEDGER`, `PI_DADDY_APPROVAL_TIMEOUT`, `PI_DADDY_AUTO_MODE` |
369
- | Child execution | `PI_DADDY_HERDR`, `PI_DADDY_HERDR_WORKSPACE`, `PI_DADDY_HERDR_KEEP_PANE`, `PI_DADDY_CHILD_IDLE_TIMEOUT`, `PI_DADDY_CHILD_TIMEOUT`, `PI_DADDY_ALLOW_UNRESOLVED_MODELS` |
370
- | Workspaces and retention | `PI_DADDY_WORKSPACE_REGISTRY`, `PI_DADDY_WORKSPACE_LEASE_DIR`, `PI_DADDY_EXECUTION_ARCHIVE`, `PI_DADDY_RETAIN_NATIVE_SESSIONS`, `PI_DADDY_NATIVE_SESSION_ROOT` |
371
- | Activity | `PI_DADDY_ACTIVITY_TIMELINE`, `PI_DADDY_ACTIVITY_CONTENT` |
470
+ | Area | Variables |
471
+ | :----------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
472
+ | Governance | `PI_DADDY_GOVERNANCE`, `PI_DADDY_GRANT`, `PI_DADDY_GATED`, `PI_DADDY_MAX_DEPTH`, `PI_DADDY_FANOUT`, `PI_DADDY_LEDGER`, `PI_DADDY_APPROVAL_TIMEOUT`, `PI_DADDY_AUTO_MODE` |
473
+ | Child execution | `PI_DADDY_HERDR`, `PI_DADDY_HERDR_WORKSPACE`, `PI_DADDY_HERDR_KEEP_PANE`, `PI_DADDY_CHILD_IDLE_TIMEOUT`, `PI_DADDY_CHILD_TIMEOUT`, `PI_DADDY_ALLOW_UNRESOLVED_MODELS` |
474
+ | Workspaces and retention | `PI_DADDY_WORKSPACE_REGISTRY`, `PI_DADDY_WORKSPACE_LEASE_DIR`, `PI_DADDY_EXECUTION_ARCHIVE`, `PI_DADDY_RETAIN_NATIVE_SESSIONS`, `PI_DADDY_NATIVE_SESSION_ROOT` |
475
+ | Activity | `PI_DADDY_ACTIVITY_TIMELINE`, `PI_DADDY_ACTIVITY_CONTENT` |
372
476
 
373
477
  `PI_DADDY_FANOUT` bounds active cooperating descendant sessions. Its default remains 8; literal 0 means exhausted,
374
478
  and malformed values refuse. A reservation includes the child and its disjoint descendant allowance, so concurrent
@@ -505,10 +609,10 @@ The command never uploads, calls a model, grants training rights, or changes LoR
505
609
  External advisors, monetary cost gates and the first-delegation model chooser were removed. These recognized old
506
610
  inputs are inert, including malformed values; the package does not rewrite existing configuration or history:
507
611
 
508
- | Input | Compatibility behavior |
509
- |---|---|
510
- | Tool argument `episodeCostCeiling` on single/all/chain | Removed before Pi validates the remaining arguments |
511
- | Settings `episodeCostCeiling`, `advisor`, `sessionModelPrompt` | Ignored; active model and authority fields still validate |
612
+ | Input | Compatibility behavior |
613
+ | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
614
+ | Tool argument `episodeCostCeiling` on single/all/chain | Removed before Pi validates the remaining arguments |
615
+ | Settings `episodeCostCeiling`, `advisor`, `sessionModelPrompt` | Ignored; active model and authority fields still validate |
512
616
  | `PI_DADDY_EPISODE_COST_CEILING`, `PI_DADDY_ADVISOR`, `PI_DADDY_ADVISOR_KEY`, `PI_DADDY_ADVISOR_MODEL`, `PI_DADDY_ADVISOR_TASK_EGRESS` | Never select or execute an intervention; reserved environment stripping remains |
513
617
 
514
618
  Historical advice/cost-gate records remain readable. Manual model choices and permission approvals remain active.
@@ -545,14 +649,13 @@ primitives, including `resolve`, `planSpawn`, `appendLedgerEvent`, `readRecords`
545
649
  The Files column names the main modules of each layer, not all of them; the module docstrings are the
546
650
  specification of who owns what.
547
651
 
548
-
549
- | Layer | Answers | Files |
550
- | :--- | :--- | :--- |
551
- | `src/kernel` | What may a child hold, and how is that carried? Mostly pure; the readers that discover what exists are the exception, and they are bounded. | `resolve`, `spawn`, `propagation`, `catalog`, `definitions`, `capabilities`, `approval`, `chain`, `context-handoff`, `fanout`, `correlation`, `refusals`, `env-names`, `project-paths`, `workspace`, `bounded-read` |
552
- | `src/governance` | What was decided, and where is it written? | `record`, `ledger`, `ledger-events`, `ledger-report`, `approval-store`, `approval-prompt`, `grant-store`, `init`, `workspace-lease`, `execution-retention` |
553
- | `src/executors` | How does a child process start and end? | `executor`, `run-herdr`, `herdr-*`, `pane-reaper` |
554
- | `src/products` | What does the operator see or report? | `activity-timeline`, `dashboard-*`, `episode-report`, `episode-outcomes` |
555
- | `extensions/` | The pi extension and its wiring: hooks, the three tools, approvals flow, `/grants`. | `grants.ts` is the entry point |
652
+ | Layer | Answers | Files |
653
+ | :--------------- | :------------------------------------------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
654
+ | `src/kernel` | What may a child hold, and how is that carried? Mostly pure; the readers that discover what exists are the exception, and they are bounded. | `resolve`, `spawn`, `propagation`, `catalog`, `definitions`, `capabilities`, `approval`, `chain`, `context-handoff`, `fanout`, `correlation`, `refusals`, `env-names`, `project-paths`, `workspace`, `bounded-read` |
655
+ | `src/governance` | What was decided, and where is it written? | `record`, `ledger`, `ledger-events`, `ledger-report`, `approval-store`, `approval-prompt`, `grant-store`, `init`, `workspace-lease`, `execution-retention` |
656
+ | `src/executors` | How does a child process start and end? | `executor`, `run-herdr`, `herdr-*`, `pane-reaper` |
657
+ | `src/products` | What does the operator see or report? | `activity-timeline`, `dashboard-*`, `episode-report`, `episode-outcomes` |
658
+ | `extensions/` | The pi extension and its wiring: hooks, the three tools, approvals flow, `/grants`. | `grants.ts` is the entry point |
556
659
 
557
660
  ## Tests
558
661
 
@@ -569,7 +672,6 @@ PI_DADDY_IT_MODEL=1 npm run test:integration --workspace=pi-daddy # opt-in real-
569
672
 
570
673
  `pi-daddy` under `packages/pi-daddy` is the only published package; the workspace root is private.
571
674
 
572
-
573
675
  ### Exact definition runtime choices (candidate)
574
676
 
575
677
  A selected definition may author a single-line `runtime-preferences` JSON array:
@@ -596,3 +698,105 @@ Call `delegate_describe({agent:"build"})` and carry its `definitionId` into `del
596
698
  child, or a `delegate_chain` step. Principal bindings require that precondition. Description starts no child
597
699
  and grants no authority. A stale ID refuses before approval or launch. This hash is an observation and
598
700
  precondition, not an approval record or a learned-policy authorization.
701
+
702
+ ### Optional retained-result consumers
703
+
704
+ `pi-daddy:operation-artifact-ready:v1` is a best-effort trusted extension hint containing `{ version: 1, reference }`. A missing or failing consumer cannot change the durable result or relaunch work. Pi's custom entry likewise holds only a reference. Consumers recover missed hints through the trusted `pi-daddy:operation-artifacts:v1` event; this is not a model-callable tool.
705
+
706
+ Requests carry `version:1`, a bounded `requestId`, current `sessionId` and canonical `cwd`, an `action`, and a reply callback. `list` accepts a limit of 1–64 directory entries and an optional opaque continuation cursor. Its response includes exact references, unfinished-admission and invalid-entry counts, completion and optional next cursor. Each page is bounded; traversal is not a snapshot under concurrent publication. Only the current owner is enumerated. A new traversal replaces the previous cursor; session replacement closes it. Consumers serialize scans and restart on failed pages rather than treating missing registration as completed.
707
+
708
+ `read` accepts an exact producer reference and optional expected `producerInstance`. The instance binds the canonical selected agent directory and filesystem identity. Artifact bytes and original admission/scope are verified under that selected root. A previous owner's exact read additionally requires a trusted asynchronous `authorize` callback, checked before and after reading. A consumer must derive that callback from its already retained, explicitly selected project registration; do not forward model-provided paths or permission flags. This does not grant live execution authority or semantic approval.
709
+
710
+ `openOperationArtifactScan(agentDirectory, owner)` and `operationArtifactInstance(agentDirectory)` are root package exports for trusted local consumers. A scan has `next(limit)` and `close()`; callers own closing it. No Bookie import or dependency is needed. Bookie may separately register reference metadata after operator consent. A failed/partial producer result remains failed/partial evidence; an admission without a result is not registration-ready completion proof.
711
+
712
+ ### One-host initiative continuation
713
+
714
+ A trusted work-map owner can select an initiative through `pi-daddy:initiative:v1`. Bookie's optional
715
+ `/bookie-work` command supplies the exact selected Project/map/task revisions and asks the operator before
716
+ acquisition. Daddy remains usable without Bookie: normal delegation is unchanged and initiative association
717
+ stays unavailable until a trusted owner selects a map. There is no background scheduler or new model call.
718
+
719
+ After selection, `initiative_task` associates a selected `taskId`/`taskRevision` with the intended
720
+ `operationId`. Use that ID as ordinary delegation's `operation_id`. Association does not dispatch, approve,
721
+ or grant tools. Ordinary delegation still checks current capabilities, selected definition and workspace
722
+ routing; actual writers still use the existing workspace lease. A trusted `assertExecutionScope` callback
723
+ also compares the actual routed child directory/workspace with this task's selected resource roots before
724
+ spawn. General permission for another repository does not make it this task's target. The original session, operation and
725
+ execution identities remain in durable attempt records when a later coordinator takes over.
726
+
727
+ One coordinator holds the existing OS ownership lock per initiative on this host. Acquisition requires an
728
+ exact previous record revision, and every mutation checks the owner generation and selected-map callback.
729
+ A lost process or an old timestamp is insufficient for takeover. Every earlier attempt must have exact
730
+ producer no-start/native-cleanup evidence. External or unknown effects additionally need a selected exact
731
+ canonical receipt, verified by the trusted work-map owner against original owner/task/operation/execution
732
+ identity and current receipt content. A human confirmation can establish operator-confirmed reconciliation;
733
+ it never invents provider success or task acceptance. Missing or changed receipts remain blocked. Local
734
+ cleanup is process settlement, not semantic acceptance, a sandbox, or a way to stop arbitrary shell writes.
735
+
736
+ The owner status is a cached dashboard contribution with an explicit initiative scope, known session count,
737
+ and bounded task observations. It knows only recorded relationships. Task reviews, releases and registry
738
+ publication remain separate owner facts. The six terminal views do not become a global initiative registry.
739
+
740
+ After restart, trusted `recover` acquires the same lock and exact state revision without changing the old
741
+ owner/generation or allowing dispatch. The handle lists bounded pending effects and reconciles only a selected
742
+ exact receipt. Release then normal acquisition establishes the next generation. Native process settlement
743
+ is required independently; a receipt cannot authorize takeover while an owned process remains unresolved.
744
+
745
+ State is a private, bounded per-initiative record under the selected agent directory (256 task revisions,
746
+ 1,024 attempt links, 512 KiB). A retained initialization marker makes a deleted record fail closed; restore
747
+ trusted state instead of treating deletion as a new initiative. Closed or revoked selection does not erase
748
+ unresolved attempts. No record is written by dashboard redraws.
749
+
750
+ Trusted event requests include `version:1`, `requestId`, `sessionId`, `cwd`, `initiativeId`, and `reply`.
751
+ `action:"status"` returns an exact `revision` or null for never-initialized state. `action:"acquire"` additionally
752
+ requires `expectedRevision`, selected `tasks:[{taskId,taskRevision,effectScope}]`, and a trusted
753
+ `assertSelection()` and task-specific `assertTaskReady({taskId,taskRevision})` callbacks. The latter is
754
+ rechecked at association, admission and launch; current inputs alone do not establish dependency readiness.
755
+ The reply echoes request/owner identity and returns a handle with
756
+ `associate`, `observe`, `release` (clean transfer), and `close` (abandon cooperative ownership; no settlement
757
+ claim). `observe` is read-only and returns an `assertCurrent` recheck for exact generation, task revision
758
+ and observed execution states. A callback or opaque identifier supplied by model text is not this authority.
759
+
760
+ `action:"recover"` uses those same selected-scope callbacks but returns `recoveryOnly:true`. Both handle modes
761
+ provide `pendingEffects()` and `reconcileEffect({initiativeId,taskId,taskRevision,owner,operationId,executionId,
762
+ effectScope,receipt:{reference,sha256}})`. Only the trusted `assertEffectReconciled` callback can verify that
763
+ receipt. No callback means unresolved effects. Task revisions retain their exact `sha256:<64hex>` source
764
+ identity (bare 64-hex revisions are also accepted); receipt digests are bare 64-hex values. Revalidation of a
765
+ previous receipt is required in the new session, using the original attempt identity, not the new owner.
766
+
767
+ Selected tasks may include one bounded neutral `effectTarget:{owner,kind,reference}`. Its responsible owner
768
+ binds the exact target into the task revision. Receipt `observation` is optional for old records; when present
769
+ it names the same target, an `applied`, `not-applied` or `unknown` outcome, and `operator-attested` or
770
+ `owner-verified` provenance. Daddy does not interpret package, registry or other business semantics.
771
+ `unknown` never resolves effects. Applied/not-applied reconciliation never accepts the task or grants execution.
772
+ An old receipt without an outcome remains readable without inventing an outcome during upgrade.
773
+
774
+ `observe` returns the selected revision's `effectObservation`: pending only when no attempt exists or exact
775
+ no-start evidence exists, otherwise unknown until native settlement and a current exact receipt establish an
776
+ outcome. Older revisions can independently require reconciliation; their outcome is never rebound to a new
777
+ target. `pendingEffects` includes each original target, and `reconcileEffect` returns that historical attempt's
778
+ exact observation. Recovery can therefore confirm an old target after a plan amendment while the current
779
+ selected target remains pending. The work-map owner still validates current target resources separately.
780
+
781
+ Task-readiness callbacks must not turn the newly admitted attempt's honest unknown state into a self-block
782
+ at launch. Daddy's `begin` refuses a new attempt while any prior attempt or effects are unresolved; the
783
+ work-map owner separately rejects repeating an already-applied target and enforces semantic prerequisites.
784
+ Immediately before start, Daddy rechecks prior attempts across all revisions of that task, excluding only the
785
+ exact already-admitted owner/operation/execution/request identity. Revoking an older receipt after admission
786
+ therefore blocks launch without misclassifying the current admitted attempt as evidence of earlier effects.
787
+
788
+ For a selected target, changing only the task revision does not authorize applying that identical target again.
789
+ Admission and launch refuse a current exact applied receipt from any retained revision of the same task. This
790
+ prevents duplicate effects; it does not reclassify the old receipt as current task acceptance. A different target
791
+ still needs normal readiness, permission, resource validation and reconciliation of earlier attempts.
792
+
793
+ Initiative dashboard refresh is display-only: it uses at most five cached observations from real owner reads,
794
+ keeps their original timestamps and labels missing or invalidated facts unavailable/stale. It performs no
795
+ semantic currentness scan, native read, model call or durable write. Work-map reads and every admission/start
796
+ boundary still invoke their authoritative currentness checks; cached display facts never authorize execution.
797
+
798
+ Trusted work-map clients may provide `assertObservationAuthority` for exact runtime-fact reads. It binds current read permission and selected owner; it does not certify current authored intent, task acceptance or permission to execute. The client still checks canonical inputs before disclosing or reusing a projection. Missing read callbacks use the original full selection guard. Claim, begin, start, reconciliation and release always keep the full guard; native receipts, held ownership and exact generation checks also remain on observations.
799
+
800
+ Exact effect-receipt validators also use the observation guard: checking an existing receipt cannot itself authorize a mutation. Coordinator acquisition, claim, begin, start, reconcile and release independently bracket those awaits with full mutation authority, including a final check before retaining an attestation.
801
+
802
+ After safe exclusive coordinator takeover, a settled previous-generation task is reported as `unclaimed` until explicitly claimed. Observation does not rewrite its historical generation or attempts. Recovery-only handles, running attempts and uncertain settlement remain non-free; current-generation claims remain `owned`.
@@ -0,0 +1,63 @@
1
+ import type { OperationArtifactOwner } from "../kernel/operation-artifact.ts";
2
+ import type { OperationRequest } from "../kernel/dispatch-operation.ts";
3
+ import { type InitiativeTask, type InitiativeTaskIdentity, type InitiativeObservation, type InitiativeEffectReconciliation } from "../kernel/initiative.ts";
4
+ import { type InitiativeResolution } from "./initiative-effects.ts";
5
+ export interface InitiativeCoordinatorOptions extends InitiativeResolution {
6
+ assertAuthority(): void | Promise<void>;
7
+ /** Optional read permission for exact owner facts; never substitutes for mutation or task-readiness authority. */
8
+ assertObservationAuthority?(): void | Promise<void>;
9
+ }
10
+ export interface AcquireInitiative {
11
+ initiativeId: string;
12
+ owner: OperationArtifactOwner;
13
+ expectedRevision: string | null;
14
+ recoveryOnly?: boolean;
15
+ }
16
+ export declare function acquireInitiativeCoordinator(directory: string, request: AcquireInitiative, options: InitiativeCoordinatorOptions): Promise<{
17
+ generation: number;
18
+ recoveryOnly: boolean;
19
+ revision: () => string;
20
+ metadata: () => {
21
+ initiativeId: string;
22
+ generation: number;
23
+ knownSessions: number;
24
+ recordedTasks: number;
25
+ recordedAttempts: number;
26
+ };
27
+ assertCurrent: () => Promise<void>;
28
+ assertObservationCurrent: () => Promise<void>;
29
+ claim(task: InitiativeTask): Promise<void>;
30
+ begin(task: InitiativeTask, operation: OperationRequest): Promise<void>;
31
+ assertPriorAttemptsSettled(task: InitiativeTask, operation: OperationRequest): Promise<void>;
32
+ notAdmitted(operation: OperationRequest): Promise<void>;
33
+ observe(input: InitiativeTaskIdentity, selectedTask?: InitiativeTask): Promise<InitiativeObservation | {
34
+ status: "unavailable";
35
+ }>;
36
+ /** Bind a final to the only admitted attempt for this exact selected task revision. */
37
+ handoffAttempt(identity: InitiativeTaskIdentity, selectedTask: InitiativeTask): Promise<{
38
+ attempt: import("../kernel/initiative.ts").InitiativeAttempt;
39
+ assertCurrent: () => void | Promise<void>;
40
+ } | undefined>;
41
+ pendingEffects(): Promise<{
42
+ effectTarget?: import("../kernel/initiative.ts").InitiativeEffectTarget | undefined;
43
+ execution: "running" | "settled" | "unknown";
44
+ owner: OperationArtifactOwner;
45
+ operationId: string;
46
+ executionId: string;
47
+ effectScope: InitiativeTask["effectScope"];
48
+ initiativeId: string;
49
+ taskId: string;
50
+ taskRevision: string;
51
+ }[]>;
52
+ reconcileEffect(input: InitiativeEffectReconciliation): Promise<{
53
+ effectObservation?: import("../kernel/initiative.ts").InitiativeEffectObservation | undefined;
54
+ reconciled: boolean;
55
+ taskAccepted: boolean;
56
+ executionAuthorized: boolean;
57
+ }>;
58
+ release(): Promise<void>;
59
+ /** Abandon only cooperative ownership; unresolved attempts remain durable and block takeover. */
60
+ close(): Promise<void>;
61
+ }>;
62
+ export type InitiativeCoordinator = Awaited<ReturnType<typeof acquireInitiativeCoordinator>>;
63
+ //# sourceMappingURL=initiative-coordinator.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"initiative-coordinator.d.ts","sourceRoot":"","sources":["../../src/governance/initiative-coordinator.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,iCAAiC,CAAC;AAC9E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AAExE,OAAO,EAGL,KAAK,cAAc,EACnB,KAAK,sBAAsB,EAE3B,KAAK,qBAAqB,EAC1B,KAAK,8BAA8B,EACpC,MAAM,yBAAyB,CAAC;AACjC,OAAO,EASL,KAAK,oBAAoB,EAC1B,MAAM,yBAAyB,CAAC;AAIjC,MAAM,WAAW,4BAA6B,SAAQ,oBAAoB;IACxE,eAAe,IAAI,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;IACxC,kHAAkH;IAClH,0BAA0B,CAAC,IAAI,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;CACrD;AACD,MAAM,WAAW,iBAAiB;IAChC,YAAY,EAAE,MAAM,CAAC;IACrB,KAAK,EAAE,sBAAsB,CAAC;IAC9B,gBAAgB,EAAE,MAAM,GAAG,IAAI,CAAC;IAChC,YAAY,CAAC,EAAE,OAAO,CAAC;CACxB;AACD,wBAAsB,4BAA4B,CAChD,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,iBAAiB,EAC1B,OAAO,EAAE,4BAA4B;;;;;;;;;;;;;gBAsHrB,cAAc;gBAed,cAAc,aAAa,gBAAgB;qCA8BhB,cAAc,aAAa,gBAAgB;2BA0B3D,gBAAgB;mBAkB9B,sBAAsB,iBACd,cAAc,GAC5B,OAAO,CAAC,qBAAqB,GAAG;QAAE,MAAM,EAAE,aAAa,CAAA;KAAE,CAAC;IA2E7D,uFAAuF;6BACxD,sBAAsB,gBAAgB,cAAc;;;;;;;;;;;;;;;2BAkC5D,8BAA8B;;;;;;;IA0CrD,iGAAiG;;GAUtG;AACD,MAAM,MAAM,qBAAqB,GAAG,OAAO,CAAC,UAAU,CAAC,OAAO,4BAA4B,CAAC,CAAC,CAAC"}