@e4779/pi-fabric 0.131.0-fork.32 → 0.131.4-fork.33

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 (111) hide show
  1. package/README.md +1 -1
  2. package/dist/activity/store.d.ts.map +1 -1
  3. package/dist/actors/feedback.d.ts +5 -0
  4. package/dist/actors/feedback.d.ts.map +1 -0
  5. package/dist/actors/global-registry.d.ts.map +1 -1
  6. package/dist/actors/manager.d.ts.map +1 -1
  7. package/dist/agents/completion-inbox.d.ts.map +1 -1
  8. package/dist/agents/manager.d.ts.map +1 -1
  9. package/dist/agents/request.d.ts.map +1 -1
  10. package/dist/agents/transports/herdr-core-socket.d.ts +13 -0
  11. package/dist/agents/transports/herdr-core-socket.d.ts.map +1 -0
  12. package/dist/agents/transports/herdr-core-transport.d.ts +10 -0
  13. package/dist/agents/transports/herdr-core-transport.d.ts.map +1 -0
  14. package/dist/agents.js +1 -1
  15. package/dist/audit/details.d.ts +2 -0
  16. package/dist/audit/details.d.ts.map +1 -1
  17. package/dist/chunks/{chunk-3PKZSIRA.js → chunk-ASOJYFKU.js} +8 -4
  18. package/dist/chunks/chunk-ASOJYFKU.js.map +7 -0
  19. package/dist/chunks/{chunk-ZFWICFNJ.js → chunk-DGUXJSYA.js} +41 -17
  20. package/dist/chunks/chunk-DGUXJSYA.js.map +7 -0
  21. package/dist/chunks/{chunk-WGMCNCP6.js → chunk-G2DZJ5LK.js} +86 -49
  22. package/dist/chunks/chunk-G2DZJ5LK.js.map +7 -0
  23. package/dist/chunks/{chunk-7CIES6X2.js → chunk-HRVYXRWZ.js} +2 -2
  24. package/dist/chunks/chunk-HRVYXRWZ.js.map +7 -0
  25. package/dist/chunks/{chunk-36XQFTEN.js → chunk-L6H46CPY.js} +2 -2
  26. package/dist/chunks/{chunk-4KX6BIPL.js → chunk-LRSZFYUC.js} +2 -2
  27. package/dist/chunks/chunk-LRSZFYUC.js.map +7 -0
  28. package/dist/chunks/{chunk-5BOTHX47.js → chunk-LZ2ZXOCU.js} +4 -4
  29. package/dist/chunks/chunk-LZ2ZXOCU.js.map +7 -0
  30. package/dist/chunks/{chunk-UFMYN5TA.js → chunk-MX53BRAC.js} +2 -2
  31. package/dist/chunks/{chunk-WWTGWGH7.js → chunk-RKJPBTBB.js} +22 -6
  32. package/dist/chunks/chunk-RKJPBTBB.js.map +7 -0
  33. package/dist/chunks/{chunk-YHFWMAQ5.js → chunk-TEMKDJJY.js} +151 -52
  34. package/dist/chunks/chunk-TEMKDJJY.js.map +7 -0
  35. package/dist/chunks/{chunk-IOGDTIGN.js → chunk-U6Y6TKJL.js} +3 -3
  36. package/dist/chunks/{chunk-IOGDTIGN.js.map → chunk-U6Y6TKJL.js.map} +1 -1
  37. package/dist/chunks/{chunk-VNWQIGQL.js → chunk-VGRUWTMG.js} +415 -252
  38. package/dist/chunks/chunk-VGRUWTMG.js.map +7 -0
  39. package/dist/chunks/{chunk-X7QETPBC.js → chunk-ZHROHNEE.js} +1 -1
  40. package/dist/commands/fabric-handler.js +1 -1
  41. package/dist/compaction/claim-events.js +1 -1
  42. package/dist/components/configuration.js +2 -2
  43. package/dist/config.d.ts +1 -1
  44. package/dist/config.d.ts.map +1 -1
  45. package/dist/core/call-presentation.d.ts +14 -0
  46. package/dist/core/call-presentation.d.ts.map +1 -0
  47. package/dist/core/shell-inbox.d.ts.map +1 -1
  48. package/dist/durable/agent.d.ts.map +1 -1
  49. package/dist/durable/worker-host.js +1 -1
  50. package/dist/durable-extension.d.ts +1 -1
  51. package/dist/durable-extension.js +1 -1
  52. package/dist/durable-extension.js.map +1 -1
  53. package/dist/durable-host.js +1 -1
  54. package/dist/durable.d.ts.map +1 -1
  55. package/dist/durable.js +5 -4
  56. package/dist/durable.js.map +2 -2
  57. package/dist/extension-bootstrap.js +5 -5
  58. package/dist/fabric-exec-tool.d.ts.map +1 -1
  59. package/dist/fabric-runtime-state.d.ts.map +1 -1
  60. package/dist/fabric-runtime-state.js +87 -60
  61. package/dist/fabric-runtime-state.js.map +4 -4
  62. package/dist/feedback.d.ts +5 -0
  63. package/dist/feedback.d.ts.map +1 -0
  64. package/dist/index.js +5 -5
  65. package/dist/jev.js +1 -1
  66. package/dist/main-agent.d.ts +2 -1
  67. package/dist/main-agent.d.ts.map +1 -1
  68. package/dist/providers/agents-provider.d.ts.map +1 -1
  69. package/dist/providers/jev-provider.js +1 -1
  70. package/dist/residency/host.js +3 -3
  71. package/dist/residency/pi-entry.js +3 -3
  72. package/dist/runtime/core-override-guest-types.js +2 -2
  73. package/dist/runtime/guest-types.d.ts +1 -1
  74. package/dist/runtime/guest-types.d.ts.map +1 -1
  75. package/dist/runtime/guest-types.js +1 -1
  76. package/dist/runtime/monty-runtime.js +1 -1
  77. package/dist/runtime/typescript-kernel.js +2 -2
  78. package/dist/topology/participant-directory.d.ts.map +1 -1
  79. package/dist/type-error-guidance.js +1 -1
  80. package/dist/ui/dashboard-model.d.ts.map +1 -1
  81. package/dist/ui/dashboard.js +8 -5
  82. package/dist/ui/dashboard.js.map +2 -2
  83. package/dist/ui/fabric-render.d.ts +1 -0
  84. package/dist/ui/fabric-render.d.ts.map +1 -1
  85. package/dist/ui/settings-values.d.ts +1 -1
  86. package/dist/ui/settings-values.d.ts.map +1 -1
  87. package/dist/ui/settings.js +2 -2
  88. package/dist/ui/settings.js.map +2 -2
  89. package/dist/ui/widget.d.ts +8 -4
  90. package/dist/ui/widget.d.ts.map +1 -1
  91. package/docs/agents.md +9 -6
  92. package/docs/background-tasks.md +24 -12
  93. package/docs/configuration.md +2 -0
  94. package/docs/interface.md +3 -1
  95. package/docs/jev.md +1 -1
  96. package/package.json +9 -9
  97. package/skillsets/python/fabric-council/SKILL.md +9 -7
  98. package/skillsets/typescript/fabric-council/SKILL.md +4 -3
  99. package/skillsets/typescript/fabric-exec/references/agents.md +5 -5
  100. package/dist/chunks/chunk-3PKZSIRA.js.map +0 -7
  101. package/dist/chunks/chunk-4KX6BIPL.js.map +0 -7
  102. package/dist/chunks/chunk-5BOTHX47.js.map +0 -7
  103. package/dist/chunks/chunk-7CIES6X2.js.map +0 -7
  104. package/dist/chunks/chunk-VNWQIGQL.js.map +0 -7
  105. package/dist/chunks/chunk-WGMCNCP6.js.map +0 -7
  106. package/dist/chunks/chunk-WWTGWGH7.js.map +0 -7
  107. package/dist/chunks/chunk-YHFWMAQ5.js.map +0 -7
  108. package/dist/chunks/chunk-ZFWICFNJ.js.map +0 -7
  109. /package/dist/chunks/{chunk-36XQFTEN.js.map → chunk-L6H46CPY.js.map} +0 -0
  110. /package/dist/chunks/{chunk-UFMYN5TA.js.map → chunk-MX53BRAC.js.map} +0 -0
  111. /package/dist/chunks/{chunk-X7QETPBC.js.map → chunk-ZHROHNEE.js.map} +0 -0
@@ -53,11 +53,15 @@ export declare const shouldShowFabricWidget: (snapshot: FabricDashboardSnapshot,
53
53
  export declare const WIDGET_TERMINAL_ROW_SHARE = 0.5;
54
54
  /** Effective row budget: the configured maximum, bounded by the live pane. */
55
55
  export declare const widgetRowLimit: (maxRows: number, terminalRows?: number) => number;
56
- /**
57
- * Row budget while the widget has focus. Focus is a request to see the list,
58
- * so it may use its whole terminal share instead of `maxRows`, but never more.
59
- */
56
+ /** Keyboard focus must not resize the footer or move the transcript. */
60
57
  export declare const widgetFocusedRowLimit: (maxRows: number, terminalRows?: number) => number;
58
+ /** Reserve an overflow row for the whole scroll range, not just while rows remain below. */
59
+ export declare const widgetViewport: (contentRows: number, budget: number, offset: number) => {
60
+ windowRows: number;
61
+ hasCue: boolean;
62
+ maxOffset: number;
63
+ offset: number;
64
+ };
61
65
  export declare class FabricWidget implements Component, Focusable {
62
66
  #private;
63
67
  readonly theme: Theme;
@@ -1 +1 @@
1
- {"version":3,"file":"widget.d.ts","sourceRoot":"","sources":["../../src/ui/widget.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,aAAa,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAEvG,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,iCAAiC,CAAC;AAC7D,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AACvD,OAAO,EAAE,qBAAqB,EAA4B,MAAM,gBAAgB,CAAC;AAQjF,OAAO,EAGL,KAAK,uBAAuB,EAE7B,MAAM,YAAY,CAAC;AAgDpB,oDAAoD;AACpD,MAAM,WAAW,eAAe;IAC9B;;;OAGG;IACH,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,GAAG,OAAO,CAAC;IAC3C,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,qFAAqF;AACrF,MAAM,WAAW,uBAAuB;IACtC,kFAAkF;IAClF,IAAI,CAAC,EAAE,CAAC,GAAG,EAAE,eAAe,KAAK,IAAI,CAAC;IACtC;;;OAGG;IACH,OAAO,EAAE,CAAC,OAAO,CAAC,EAAE,MAAM,KAAK,IAAI,CAAC;IACpC,4EAA4E;IAC5E,aAAa,EAAE,MAAM,IAAI,CAAC;IAC1B,6EAA6E;IAC7E,QAAQ,CAAC,EAAE,MAAM,IAAI,CAAC;IACtB,wFAAwF;IACxF,aAAa,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,MAAM,GAAG,SAAS,CAAC;IACtD,oGAAoG;IACpG,OAAO,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IACnC,+GAA+G;IAC/G,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,iFAAiF;IACjF,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,OAAO,CAAC;CAC9B;AA+FD,eAAO,MAAM,sBAAsB,GACjC,UAAU,uBAAuB,EACjC,MAAM,kBAAkB,EACxB,iCAAuC,KACtC,OAcF,CAAC;AAEF;;;;;;GAMG;AACH,eAAO,MAAM,yBAAyB,MAAM,CAAC;AAE7C,8EAA8E;AAC9E,eAAO,MAAM,cAAc,GAAI,SAAS,MAAM,EAAE,eAAe,MAAM,KAAG,MAOvE,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,qBAAqB,GAAI,SAAS,MAAM,EAAE,eAAe,MAAM,KAAG,MAI9E,CAAC;AAKF,qBAAa,YAAa,YAAW,SAAS,EAAE,SAAS;;IAErD,QAAQ,CAAC,KAAK,EAAE,KAAK;IACrB,QAAQ,CAAC,QAAQ,EAAE,MAAM,uBAAuB;IAChD,QAAQ,CAAC,OAAO,EAAE,MAAM;IAGxB,QAAQ,CAAC,YAAY,CAAC,GAAE,MAAM,MAAM,GAAG,SAAS;IAChD,QAAQ,CAAC,SAAS;IAClB,QAAQ,CAAC,WAAW,CAAC,EAAE,uBAAuB;gBAPrC,KAAK,EAAE,KAAK,EACZ,QAAQ,EAAE,MAAM,uBAAuB,EACvC,OAAO,EAAE,MAAM,EAGf,YAAY,CAAC,GAAE,MAAM,MAAM,GAAG,SAAS,aAAA,EACvC,SAAS,wBAA8B,EACvC,WAAW,CAAC,EAAE,uBAAuB,YAAA;IAGhD,oEAAoE;IACpE,OAAO,UAAS;IAUhB,6FAA6F;IAC7F,aAAa,IAAI,IAAI;IAOrB,yEAAyE;IACzE,WAAW,IAAI,IAAI;IAInB,kDAAkD;IAClD,OAAO,IAAI,OAAO;IAQlB,WAAW,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IA6B/B,WAAW,CAAC,KAAK,EAAE,aAAa,GAAG,mBAAmB,GAAG,SAAS;IAuDlE,MAAM,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE;IA+B/B,UAAU,IAAI,OAAO;IAYrB,UAAU,IAAI,IAAI;CAqOnB"}
1
+ {"version":3,"file":"widget.d.ts","sourceRoot":"","sources":["../../src/ui/widget.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,aAAa,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAEvG,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,iCAAiC,CAAC;AAC7D,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAEvD,OAAO,EAAE,qBAAqB,EAA4B,MAAM,gBAAgB,CAAC;AAQjF,OAAO,EAGL,KAAK,uBAAuB,EAE7B,MAAM,YAAY,CAAC;AAgDpB,oDAAoD;AACpD,MAAM,WAAW,eAAe;IAC9B;;;OAGG;IACH,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,GAAG,OAAO,CAAC;IAC3C,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,qFAAqF;AACrF,MAAM,WAAW,uBAAuB;IACtC,kFAAkF;IAClF,IAAI,CAAC,EAAE,CAAC,GAAG,EAAE,eAAe,KAAK,IAAI,CAAC;IACtC;;;OAGG;IACH,OAAO,EAAE,CAAC,OAAO,CAAC,EAAE,MAAM,KAAK,IAAI,CAAC;IACpC,4EAA4E;IAC5E,aAAa,EAAE,MAAM,IAAI,CAAC;IAC1B,6EAA6E;IAC7E,QAAQ,CAAC,EAAE,MAAM,IAAI,CAAC;IACtB,wFAAwF;IACxF,aAAa,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,MAAM,GAAG,SAAS,CAAC;IACtD,oGAAoG;IACpG,OAAO,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IACnC,+GAA+G;IAC/G,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,iFAAiF;IACjF,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,OAAO,CAAC;CAC9B;AAqGD,eAAO,MAAM,sBAAsB,GACjC,UAAU,uBAAuB,EACjC,MAAM,kBAAkB,EACxB,iCAAuC,KACtC,OAcF,CAAC;AAEF;;;;;;GAMG;AACH,eAAO,MAAM,yBAAyB,MAAM,CAAC;AAE7C,8EAA8E;AAC9E,eAAO,MAAM,cAAc,GAAI,SAAS,MAAM,EAAE,eAAe,MAAM,KAAG,MAOvE,CAAC;AAEF,wEAAwE;AACxE,eAAO,MAAM,qBAAqB,GAAI,SAAS,MAAM,EAAE,eAAe,MAAM,KAAG,MACxC,CAAC;AAExC,4FAA4F;AAC5F,eAAO,MAAM,cAAc,GAAI,aAAa,MAAM,EAAE,QAAQ,MAAM,EAAE,QAAQ,MAAM;;;;;CAOjF,CAAC;AAKF,qBAAa,YAAa,YAAW,SAAS,EAAE,SAAS;;IAErD,QAAQ,CAAC,KAAK,EAAE,KAAK;IACrB,QAAQ,CAAC,QAAQ,EAAE,MAAM,uBAAuB;IAChD,QAAQ,CAAC,OAAO,EAAE,MAAM;IAGxB,QAAQ,CAAC,YAAY,CAAC,GAAE,MAAM,MAAM,GAAG,SAAS;IAChD,QAAQ,CAAC,SAAS;IAClB,QAAQ,CAAC,WAAW,CAAC,EAAE,uBAAuB;gBAPrC,KAAK,EAAE,KAAK,EACZ,QAAQ,EAAE,MAAM,uBAAuB,EACvC,OAAO,EAAE,MAAM,EAGf,YAAY,CAAC,GAAE,MAAM,MAAM,GAAG,SAAS,aAAA,EACvC,SAAS,wBAA8B,EACvC,WAAW,CAAC,EAAE,uBAAuB,YAAA;IAGhD,oEAAoE;IACpE,OAAO,UAAS;IAahB,6FAA6F;IAC7F,aAAa,IAAI,IAAI;IAQrB,yEAAyE;IACzE,WAAW,IAAI,IAAI;IAKnB,kDAAkD;IAClD,OAAO,IAAI,OAAO;IAQlB,WAAW,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IA6B/B,WAAW,CAAC,KAAK,EAAE,aAAa,GAAG,mBAAmB,GAAG,SAAS;IAoElE,MAAM,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE;IA+B/B,UAAU,IAAI,OAAO;IAYrB,UAAU,IAAI,IAAI;CAkOnB"}
package/docs/agents.md CHANGED
@@ -549,7 +549,10 @@ This is the host-level equivalent of the `pi-model-switch` extension's `switch_m
549
549
  | `screen` | Creates one detached GNU Screen session for each child | `screen -r …` |
550
550
  | `localterm` | Creates one pinned LocalTerm PTY for each child | `localterm session attach …` |
551
551
  | `herdr` | Creates one background Herdr tab for each child | `herdr terminal attach …` |
552
- | `auto` | Tries Herdr, LocalTerm, tmux, screen, and then process | Depends on the transport |
552
+ | `herdr-core` | Creates one background Herdr Core terminal per child | `hc attach tN` |
553
+ | `auto` | Tries Herdr Core, Herdr, LocalTerm, tmux, screen, and then process | Depends on the transport |
554
+
555
+ Herdr Core (`herdr-core`) is a separate terminal service, not the Herdr workspace/tab API. Both explicit selection (`transport: "herdr-core"`) and auto-selection require the parent’s injected `HC_TERMINAL_ID` and `HC_TERMINAL_SOCKET`, and a reachable generation-1 service advertising terminal run/get/kill. Fabric uses only that socket (including native Windows pipe names); it does not search other sessions, start/restart the service, or require a CLI on PATH. Auto falls through safely when this context is missing, unreachable or incompatible; explicit selection reports unavailable. Each child receives direct argv and cwd, a unique sanitized name, and Core’s own child identity, not a copy of the parent’s environment. Launches disable typed parent notifications, waiting, keep/recovery, and outliving the parent. Handles report Core terminal addresses and `hc attach tN`; use `herdr-core attach tN` if the `hc` alias is absent, in the same Core session. Finished or removed terminals are not alive. Stop kills only that child; it does not remove retained output or mutate the service lifecycle. RPC failures other than a missing child remain visible. Existing Herdr status and session-label UI features still apply only to legacy Herdr.
553
556
 
554
557
  Herdr uses its local socket API to create an argv-backed background tab as one atomic operation. It does not change focus or require shell quoting. Automatic selection works only when the parent Pi process already runs in Herdr. This requires `HERDR_ENV=1` with an injected workspace and socket. Select `transport: "herdr"` under the same conditions. Use the attach command in the handle to open a child directly.
555
558
 
@@ -644,7 +647,7 @@ const peerRoot = sessions.find((participant) => participant.id !== main.id);
644
647
  if (peerRoot) {
645
648
  await agents.steer({ id: peerRoot.id, message: "Coordinate on the shared migration." });
646
649
  }
647
- await agents.followUp({ id: main.id, message: "After the audit, reconcile the findings." });
650
+ await agents.steer({ id: main.id, message: "Reconcile these audit findings." });
648
651
 
649
652
  const lineage = await agents.list({ scope: "lineage" });
650
653
  return { self: await agents.self(), lineage };
@@ -654,7 +657,7 @@ Child dialogs (`select`, `confirm`, `input`, `editor`) are cancelled by default.
654
657
 
655
658
  Routing also gives a Pi child with extensions the tools in `agents.childQuestionTools` (default `["ask"]`), so the caller does not have to name them in `tools`. A child's system prompt lists only the extension tools its `tools` allowlist permits.
656
659
 
657
- For Main and one-shot agents, `steer` arrives after the tool calls in the current turn and before the next model call. A workflow that runs inside one `fabric_exec` is one tool call, so Main's steer waits for all of it; move the program to the background (Ctrl+B twice, or `background: true`) to steer Main while it runs, see [Background programs](background-tasks.md#background-programs). `followUp` waits until the current run settles. For actors, both operations add a message to the serial mailbox. `agents.status({ id })` accepts any participant ID. It returns complete details for a local run or actor and a bounded directory summary for a remote participant. `agents.setSteeringMode` and `setFollowUpMode` continue to control local one-shot runs.
660
+ For Main and one-shot agents, `steer` arrives after the tool calls in the current turn and before the next model call. Incoming agent-originated Main feedback (including child, actor, peer, lifecycle, and resident relay messages) uses **hidden steering**, even when the sender requested `followUp`. Main records the actual delivery and the requested mode in message details. The human sees a bounded, single-line notification naming the sender, not a chat bubble; the full message and JSON-serializable data remain in model context and session audit. UI-less hosts still receive the hidden feedback; notification failure never replays it. A workflow that runs inside one `fabric_exec` is one tool call, so Main's steer waits for all of it; move the program to the background (Ctrl+B twice, or `background: true`) to steer Main while it runs, see [Background programs](background-tasks.md#background-programs). For one-shot targets, `followUp` still waits until the current run settles. Direct human Main messages retain their chosen steer/follow-up controls. For actors, both operations add a message to the serial mailbox. `triggerTurn: false` remains passive: it never starts idle Main, and Pi appends it after the current turn when Main is active. Intentional blocking handoff final-answer continuations retain their existing behavior. `agents.status({ id })` accepts any participant ID. It returns complete details for a local run or actor and a bounded directory summary for a remote participant. `agents.setSteeringMode` and `setFollowUpMode` continue to control local one-shot runs.
658
661
 
659
662
  Local routing returns `"main"` or `"local"`. For cross-process `steer`, `followUp`, and `stop`, Fabric resolves the exact owner of the target. It sends a control command addressed to that owner and waits for an acknowledgement that matches the version, target, and owner identity. Success returns `routed: "mesh", acknowledged: true` after this verified acknowledgement. Unknown IDs, stale owners, rejection, and timeout throw an error. The dashboard actions `s`, `u`, and `x` use the same route. Set `mesh.enabled` to use cross-process control. See [`references/agents.md`](../skillsets/typescript/fabric-exec/references/agents.md).
660
663
 
@@ -719,7 +722,7 @@ if (peer) {
719
722
 
720
723
  Pi events use these names: `pi.input`, `pi.agent_start`, `pi.agent_end`, `pi.turn_end`, `pi.agent_settled`, `pi.tool_error`, and `pi.session_compact`. Runner-neutral terminal events use `run.completed`, `run.failed`, `run.stopped`, and `run.timed_out`. Recovery events use `run.resumed` for a relaunched attempt after an unexpected stop, and `run.detached` for a run that outlived its caller's cancellation. The `tokens.usage` event provides bounded usage. The `component.state` event reports supervised component transitions. Lifecycle envelopes contain source identity and bounded operational metadata. They do not contain session transcripts.
721
724
 
722
- A detached local `agents.spawn()` has a smaller convenience route. When `agents.notifyOnComplete` is enabled, terminal completion automatically sends Main a triggered follow-up. A call to `agents.wait()` makes the run foreground work and disables that detached notification.
725
+ A detached `agents.spawn()` has a smaller convenience route. When `agents.notifyOnComplete` is enabled, local and resident completions show a concise UI notification immediately. The completion inbox batches unread result summaries as hidden steering after the current tool turn, or wakes idle Main once. Full results remain in the run store (`agents.wait`/`agents.log`); summaries are bounded. `agents.wait()`/`join()` and terminal `agents.status()` acknowledge the result and retract pending context delivery, even if completion preceded the wait. Running status and UI/list polling do not acknowledge it. Interrupted results stay parked until new input; a recovered error can release them. Durable spawns preserve unread deliveries and acknowledgments across reconnects. This convenience route is distinct from explicit lifecycle subscriptions, whose delivery remains at-least-once across a crash.
723
726
 
724
727
  For a code-owned typed alternative to a reasoning actor, use [Jev Main-turn observers](jev.md#main-turn-advisors-and-supervisors). They consume bounded selected event context with `program.nextEvent()`, work without mesh, and can explicitly opt into freshness-checked advice. They are session-owned Jev runs, not participant subscription targets.
725
728
 
@@ -884,7 +887,7 @@ Choose one of these response modes:
884
887
  - With `text`, each non-empty response becomes an actor outbox message.
885
888
  - With `directive`, validated output in the form `{ action: "silent" | "message" | "stop", message?, data? }` lets the actor choose whether to intervene.
886
889
 
887
- Delivery can stay in `mailbox` or enter the main session through `steer`, `followUp`, or `nextTurn`. For `steer` and `followUp`, explicitly set `triggerTurn: true | false`. A value of `true` starts Main when it is idle. A value of `false` is passive, and Fabric labels it as unable to start Main. The `mailbox` and `nextTurn` modes never start Main, so they reject `triggerTurn: true`. This policy keeps a delivered actor message from looking like a stalled continuation. Fabric applies no extra 8,000-character truncation to local actor or agent messages sent to Main. Standard limits for model context, providers, and cross-mesh event size still apply.
890
+ Delivery can stay in `mailbox` or enter Main through `steer`, legacy `followUp` (now a steering alias for incoming feedback), or intentional `nextTurn`. Actor output uses a bounded sender notification and a hidden full-content message, including structured directive data. For `steer` and `followUp`, explicitly set `triggerTurn: true | false`. A value of `true` starts Main when it is idle. A value of `false` is passive, and Fabric labels it as unable to start Main. The `mailbox` and `nextTurn` modes never start Main, so they reject `triggerTurn: true`. This policy keeps a delivered actor message from looking like a stalled continuation. Fabric applies no extra 8,000-character truncation to local actor or agent messages sent to Main. Standard limits for model context, providers, and cross-mesh event size still apply. `nextTurn` still waits for the next user prompt; `mailbox` stays out of Main entirely. No scheduling, ownership, or deduplication policy is changed by the notification projection.
888
891
 
889
892
  The actor cannot change delivery from its response. The owner can update a live actor or global template and keep its history:
890
893
 
@@ -896,7 +899,7 @@ await agents.setDeliveryPolicy({
896
899
  });
897
900
  ```
898
901
 
899
- Set `scope: "global"` to update a reusable template. In the dashboard, press `y` on an actor or template, then choose mailbox, steer, follow-up, or next-turn delivery. Lowercase `m` and `e` change this Pi session. Uppercase `M` and `E` change the owner-gated project defaults. These changes keep the Pi or Claude runner session. Use `agents.ask()` for a blocking exchange and `agents.tell()` for fire-and-forget mail. Both accept one-activation `model` and `thinking` overrides. Read shared history with `agents.messages()`. `agents.remove()` is local-owner-only for session actors and routes durable actors to the resident owner.
902
+ Set `scope: "global"` to update a reusable template. In the dashboard, press `y` on an actor or template, then choose mailbox, steer, legacy follow-up (steering alias), or next-turn delivery. Lowercase `m` and `e` change this Pi session. Uppercase `M` and `E` change the owner-gated project defaults. These changes keep the Pi or Claude runner session. Use `agents.ask()` for a blocking exchange and `agents.tell()` for fire-and-forget mail. Both accept one-activation `model` and `thinking` overrides. Read shared history with `agents.messages()`. `agents.remove()` is local-owner-only for session actors and routes durable actors to the resident owner.
900
903
 
901
904
  ## Paged agent logs
902
905
 
@@ -88,14 +88,24 @@ before sealing their log, regardless of extension shutdown order.
88
88
 
89
89
  ## Agent awareness and yielding
90
90
 
91
- Before each model request, Fabric projects one bounded live-task reminder into
92
- context, independently of the returned `fabric_exec` value. Even if a program
93
- discards the nested shell result, the owning agent can see that work is running.
94
- The reminder is reconstructed from live session state after context compaction;
95
- it is not a persisted transcript entry and **never triggers a turn** itself.
96
- Unchanged task state keeps the same message; elapsed time and process output do
97
- not churn it. It includes at most eight task IDs and short, quoted labels, with
98
- an omitted count for additional jobs.
91
+ When a task moves to the background, Fabric appends one note to the result of
92
+ the tool call that spilled it, independently of the returned `fabric_exec`
93
+ value. Even if a program discards the nested shell result, the owning agent can
94
+ see that work is running. Tasks spilled by one call share one note, which
95
+ includes at most eight task IDs and short, quoted labels, with an omitted count
96
+ for additional jobs, and never elapsed time or process output. The note
97
+ **never triggers a turn** itself.
98
+
99
+ The note records a moment and is never edited or retracted; later task events
100
+ report each outcome in transcript order. Fabric does not rewrite requests for
101
+ awareness, so each request extends the previous one and the provider's prompt
102
+ cache keeps hitting while tasks run. A reminder projected at the end of every
103
+ request would be missing from the next request in that position, which caps
104
+ the cached prefix at the last request without it. The note lives in an ordinary
105
+ tool result, not a custom message, because Pi rebuilds custom-message objects
106
+ on every refresh and its idle cache warmer, which compares objects by identity,
107
+ then treats the conversation as changed. After compaction, which replaces the
108
+ prefix anyway, Fabric restates still-running tasks on the next tool result.
99
109
 
100
110
  For ordinary detached commands and wake-enabled monitors, it tells the agent to
101
111
  continue independent work or **end the turn if it needs their results**. Completion
@@ -104,10 +114,12 @@ are unnecessary. UI-only monitors are explicitly marked **no automatic wakeup**,
104
114
  including on completion, so the agent must not yield expecting them to resume it.
105
115
  Pending required results are not evidence that the assignment is complete.
106
116
 
107
- Foreground, completed, stopping, and abandoned-branch jobs are excluded. Abort/error
108
- suspension suppresses the reminder until new input, just like automatic delivery.
109
- Reload/session shutdown removes the context hook along with the inbox. Awareness
110
- works without a terminal and does not restore processes across Pi restarts.
117
+ Foreground jobs, jobs that end before the next tool result, abandoned-branch
118
+ jobs, and durable tasks reattached after a restart are not announced; the
119
+ process that spilled a reattached task already wrote its note. A note stays on
120
+ its own branch of the session tree. Reload/session shutdown closes the inbox.
121
+ Awareness works without a terminal and does not restore processes across Pi
122
+ restarts.
111
123
 
112
124
  ### Prompt-cache warming while yielded
113
125
 
@@ -685,6 +685,8 @@ Fabric attributes each file through a `session_info` marker (`fabricagent-<name>
685
685
 
686
686
  ccusage's double-count guard rejects a named store that overlaps the default pi store, so the isolated-row form requires the separate directory.
687
687
 
688
+ `agents.transport` accepts `process` (default), `auto`, `tmux`, `screen`, `localterm`, `herdr`, and `herdr-core`; per-call `transport` uses the same values. Herdr Core requires the existing parent terminal’s `HC_TERMINAL_ID` and `HC_TERMINAL_SOCKET` plus a reachable generation-1 service. It never starts a server. `auto` tries Core before legacy Herdr and falls back when unavailable.
689
+
688
690
  See [agents, actors & mesh](agents.md) for the runner and transport details.
689
691
 
690
692
  ## MCP
package/docs/interface.md CHANGED
@@ -10,6 +10,8 @@ Nested `pi.read`, `pi.bash`, `pi.powershell`, `pi.grep`, `pi.find`, `pi.ls`, `pi
10
10
 
11
11
  Fabric keeps its orchestration-specific behavior around those previews. Multi-call rows stay compact, and live write composition with phase/call progress stays visible during the run. Agent and actor audits can expose their current child tools directly in the parent card, with owner, runner, and run metadata. One execution-wide throttle coalesces parallel nested-call updates before they reach Pi, and continuous streams are not starved. Long ANSI rows are bounded without clearing the enclosing tool background. The widget lease plus result-to-source row transfer keep completion height stable. The highlighter initializes lazily and falls back to plain text until it is ready. When Pi switches between its light and dark variants, the highlighter swaps themes live. Collapsed previews use the configured expand keybinding, for example `Ctrl-O`.
12
12
 
13
+ Successful internal `native.load` calls are hidden from ordinary tool rows and call totals, including partial updates, resumed cards, and dashboard summaries. Errors remain visible, and the raw audits and execution trace still record the calls. This is a presentation filter only: branch-local `load`/`store` behavior and commit ordering are unchanged. Built-in provider actions use scoped labels and bounded, allowlisted target metadata (for example `tasks.wait task-id`); stdin, credentials, arbitrary program input, and model state are not used as fallback labels.
14
+
13
15
  ## Terminal title
14
16
 
15
17
  In an interactive session, the terminal window/tab title carries the declared `fabric_exec` display name: `record release evidence`, `Apply migration`, and so on. Nested call detail such as `read src/config.ts · typescript` never reaches the window; it stays in the transcript and the activity surface, where there is room for it.
@@ -24,7 +26,7 @@ See [Background tasks and monitors](background-tasks.md) for completion delivery
24
26
 
25
27
  ## Agent list
26
28
 
27
- The Fabric widget sits at the bottom of the screen, below Pi's footer and a blank row, as in Claude Code. Its header is the main session's row: `● FAB-3` shows the session's [peer label](agents.md#peer-labels-and-queue-gates), followed by the current run's declared name and totals. A new session takes its label at its first Fabric use, so a session that has done nothing yet shows none. Without a label it reads `● Fabric`. A session with a label also shows it on the right of the editor's top border, in a badge like the one a conversation window shows for its target, whether or not the list is showing. While the list has no row to select, with no agent, actor worker, or shell task (idle actors have none), it takes no rows. The badge yields to Pi's own border text, such as a scroll indicator, and needs the list to be placed after the footer; otherwise the header row stays. Below it, running agents and actors are listed as a tree, above any background shell tasks, each child under its parent and indented by depth. Each row shows a circle, the participant's name, what it is doing, its model, tool calls, tokens, and elapsed time. What it is doing is the latest display name the agent declared for a `fabric_exec` call, which holds until it declares another; before that, the row shows the current tool or `thinking`. A finished row shows its result or error. The circle's colour is the status: accent while running, green when done, red on failure. Shell tasks list one per row after agents and actors, within the same row budget. Shell rows are selectable like agents: **Enter** or a click on a shell opens that task's detail with its output, status, and stop action. There is no secondary task-list overlay. **Esc** closes a task opened this way in one step, and focus returns to the list. Lines disclose progressively: when a line is too wide, its statistics drop first, then its title or activity is shortened, and its key hints go last. Pi gives extensions no slot below its footer, so Fabric registers an empty below-editor widget and places the list after the footer itself, in both the fullscreen and the regular renderer. Pi's footer and footers from other extensions stay as they are. In fullscreen mode, the list uses only the rows left after Pi's editor, other widgets (including Better OpenAI's status line), and footer, keeping at least one transcript row. It shrinks or temporarily disappears when those need the space, and returns when space is available. If Pi's layout is not the one Fabric expects, the list falls back to below the editor and stays last among the widgets other extensions place there. Press **↓** in an empty editor to move into the list; **ctrl+shift+e**, **`/fabric focus`**, or a click on a row also focuses it. The filled circle `●` marks the selected row, and **↑↓** or **j/k** moves it. **↑** on the top row returns to the editor. **Enter** or a click opens the participant's full conversation, where you can read its whole transcript, see its model and thinking level, and steer it or send a follow-up. Closing that view returns focus to the list. As in Claude Code, there is no inline preview: the conversation is where a participant's activity is shown. In Pi's fullscreen renderer, hovering the pointer over a row fills its circle too. Pi turns on hover tracking only outside tmux, zellij, and screen, and there is no event for leaving the widget, so the hover clears when the pointer crosses the header or the next key is pressed. **Esc** returns focus to the editor; while the list has focus, Esc does not halt background workers. Any other key returns focus to the editor and reaches it, so typing, Ctrl+C, and shortcuts keep working; only a click on a participant row takes focus. While it has focus, the list may grow past `ui.maxRows` to half of the terminal height, still bounded by the space left for it in the fullscreen dock. Arrow keys scroll within that bounded viewport, keeping every participant and task reachable. Unfocused overflow folds into a `+N` marker.
29
+ The Fabric widget sits at the bottom of the screen, below Pi's footer and a blank row, as in Claude Code. Its header is the main session's row: `● FAB-3` shows the session's [peer label](agents.md#peer-labels-and-queue-gates), followed by the current run's declared name and totals. A new session takes its label at its first Fabric use, so a session that has done nothing yet shows none. Without a label it reads `● Fabric`. A session with a label also shows it on the right of the editor's top border, in a badge like the one a conversation window shows for its target, whether or not the list is showing. While the list has no row to select, with no agent, actor worker, or shell task (idle actors have none), it takes no rows. The badge yields to Pi's own border text, such as a scroll indicator, and needs the list to be placed after the footer; otherwise the header row stays. Below it, running agents and actors are listed as a tree, above any background shell tasks, each child under its parent and indented by depth. Each row shows a circle, the participant's name, what it is doing, its model, tool calls, tokens, and elapsed time. What it is doing is the latest display name the agent declared for a `fabric_exec` call, which holds until it declares another; before that, the row shows the current tool or `thinking`. A finished row shows its result or error. The circle's colour is the status: accent while running, green when done, red on failure. Shell tasks list one per row after agents and actors, within the same row budget. Shell rows are selectable like agents: **Enter** or a click on a shell opens that task's detail with its output, status, and stop action. There is no secondary task-list overlay. **Esc** closes a task opened this way in one step, and focus returns to the list. Lines disclose progressively: when a line is too wide, its statistics drop first, then its title or activity is shortened, and its key hints go last. Pi gives extensions no slot below its footer, so Fabric registers an empty below-editor widget and places the list after the footer itself, in both the fullscreen and the regular renderer. Pi's footer and footers from other extensions stay as they are. In fullscreen mode, the list uses only the rows left after Pi's editor, other widgets (including Better OpenAI's status line), and footer, keeping at least one transcript row. It shrinks or temporarily disappears when those need the space, and returns when space is available. If Pi's layout is not the one Fabric expects, the list falls back to below the editor and stays last among the widgets other extensions place there. Press **↓** in an empty editor to move into the list; **ctrl+shift+e**, **`/fabric focus`**, or a click on a row also focuses it. The filled circle `●` marks the selected row, and **↑↓** or **j/k** moves it. **↑** on the top row returns to the editor. **Enter** or a click opens the participant's full conversation, where you can read its whole transcript, see its model and thinking level, and steer it or send a follow-up. Closing that view returns focus to the list. As in Claude Code, there is no inline preview: the conversation is where a participant's activity is shown. In Pi's fullscreen renderer, hovering the pointer over a row fills its circle too. Pi turns on hover tracking only outside tmux, zellij, and screen, and there is no event for leaving the widget, so the hover clears when the pointer crosses the header or the next key is pressed. **Esc** returns focus to the editor; while the list has focus, Esc does not halt background workers. Any other key returns focus to the editor and reaches it, so typing, Ctrl+C, and shortcuts keep working; only a click on a participant row takes focus. The list never grows past `ui.maxRows` on focus and remains bounded by half the terminal height and the space left in the fullscreen dock. Arrow keys and the mouse wheel over the list scroll within that viewport, keeping every participant and task reachable without moving the footer. When content overflows, a bottom cue row stays reserved across the whole scroll range: `↓ N more` appears there while children remain below, and the row is blank at the end. `↑ N more` appears in the main header when children are above the viewport. Very short viewports prioritize the header and a reachable child over the cue. Short or idle lists do not reserve a large empty area.
28
30
 
29
31
  ## Focused conversations
30
32
 
package/docs/jev.md CHANGED
@@ -330,7 +330,7 @@ return {id:observer.id, state:observer.state};
330
330
 
331
331
  ### Delivery, freshness, and interruption
332
332
 
333
- Delivery defaults to off. Opt into `"steer"` or `"followUp"`; `triggerTurn` defaults to false. `maxAdvice` bounds delivery attempts for the run (feedback/stale suppression does not consume a delivery attempt) (1–16, default 4). Advice must be sent before requesting the next event; it needs the last consumed event ID and must still match the latest completed-turn/task/context revision and age limit. A next turn may be in flight; a newer completed turn, real input, compaction, or cancellation invalidates old advice. The check is at enqueue time, not a guarantee that context cannot change before Main consumes a queued message.
333
+ Delivery defaults to off. Opt into `"steer"` or legacy `"followUp"` (both deliver Main feedback as hidden steering); `triggerTurn` defaults to false and never wakes idle Main when false. UI hosts show a bounded notification naming the advisor instead of a chat bubble. The full advice remains in model context and session audit, with actual and requested delivery modes. `maxAdvice` bounds delivery attempts for the run (feedback/stale suppression does not consume a delivery attempt) (1–16, default 4). Advice must be sent before requesting the next event; it needs the last consumed event ID and must still match the latest completed-turn/task/context revision and age limit. A next turn may be in flight; a newer completed turn, real input, compaction, or cancellation invalidates old advice. The check is at enqueue time, not a guarantee that context cannot change before Main consumes a queued message.
334
334
 
335
335
  There is at most **one delivery attempt across all Jev observers per external user input**. Automatic continuations and extension-injected input do not reset this feedback latch. Duplicate, stale, disabled, over-budget, feedback-gated, or failed deliveries return `{delivered:false,reason}`; failures are not replayed. This prevents an advisor from repeatedly waking/steering Main based on its own intervention. Additional turns may still be classified and recorded within budget. Broader separately granted tools retain their own authority; these safeguards specifically govern `jev.advise`.
336
336
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@e4779/pi-fabric",
3
- "version": "0.131.0-fork.32",
3
+ "version": "0.131.4-fork.33",
4
4
  "description": "A programmable tool and agent runtime for Pi",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -143,9 +143,9 @@
143
143
  "image": "https://raw.githubusercontent.com/fabric-runtime/pi-fabric/main/media/banner.svg"
144
144
  },
145
145
  "dependencies": {
146
- "@earendil-works/chord": "1.4.0",
147
- "@earendil-works/pi-codemode": "1.4.0",
148
- "@earendil-works/pi-durable": "1.4.0",
146
+ "@earendil-works/chord": "1.5.0",
147
+ "@earendil-works/pi-codemode": "1.5.0",
148
+ "@earendil-works/pi-durable": "1.5.0",
149
149
  "@jitl/quickjs-singlefile-mjs-release-sync": "^0.32.0",
150
150
  "@lezer/common": "^1.5.2",
151
151
  "@lezer/python": "^1.1.19",
@@ -155,7 +155,7 @@
155
155
  "cross-spawn": "^7.0.6",
156
156
  "diff": "^9.0.0",
157
157
  "mcporter": "^0.12.3",
158
- "pi-fabric-worker-sdk": "npm:@earendil-works/pi-coding-agent@1.4.0",
158
+ "pi-fabric-worker-sdk": "npm:@earendil-works/pi-coding-agent@1.5.0",
159
159
  "quickjs-emscripten-core": "^0.32.0",
160
160
  "shiki": "4.4.3",
161
161
  "typescript": "^6.0.3",
@@ -172,10 +172,10 @@
172
172
  "@earendil-works/pi-durable": ">=1.4.0"
173
173
  },
174
174
  "devDependencies": {
175
- "@earendil-works/pi-agent-core": "1.4.0",
176
- "@earendil-works/pi-ai": "1.4.0",
177
- "@earendil-works/pi-coding-agent": "1.4.0",
178
- "@earendil-works/pi-tui": "1.4.0",
175
+ "@earendil-works/pi-agent-core": "1.5.0",
176
+ "@earendil-works/pi-ai": "1.5.0",
177
+ "@earendil-works/pi-coding-agent": "1.5.0",
178
+ "@earendil-works/pi-tui": "1.5.0",
179
179
  "@types/cross-spawn": "^6.0.6",
180
180
  "@types/node": "^26.1.2",
181
181
  "esbuild": "^0.25.12",
@@ -11,6 +11,7 @@ Use one Python `fabric_exec`. Pass `payloads.task`, a JSON array in `payloads.ro
11
11
  ```python
12
12
  import asyncio
13
13
  import json
14
+ import uuid
14
15
  from datetime import datetime, timezone
15
16
 
16
17
  async def ask(task, name, options=None):
@@ -102,15 +103,16 @@ if not completed:
102
103
  return dict(summary, status="failed", failures=failures, result=None)
103
104
  # Park completed reports in mesh before synthesis: an audit trail that survives this
104
105
  # program, and full-text recovery when synthesis fails or a budget runs out.
105
- reports_key = "council/" + datetime.now(timezone.utc).strftime("%Y-%m-%d-%H-%M-%S") + "/reports"
106
+ # The run id keeps same-second councils from overwriting each other: mesh.put is create-or-update.
107
+ reports_key = "council/" + datetime.now(timezone.utc).strftime("%Y-%m-%d-%H-%M-%S") + "-" + uuid.uuid4().hex[:8] + "/reports"
106
108
  try:
107
- await mesh.put({
108
- "key": reports_key,
109
- "value": [
109
+ await mesh.put(
110
+ key=reports_key,
111
+ value=[
110
112
  {"role": item.get("role"), **({"model": item["model"]} if item.get("model") else {}), "report": item["report"]}
111
113
  for item in completed
112
114
  ],
113
- })
115
+ )
114
116
  reports = reports_key
115
117
  except Exception as error:
116
118
  reports = {"error": str(error)}
@@ -120,7 +122,7 @@ try:
120
122
  result = await ask("Synthesize only the completed reports into one decision. Reject unsupported claims, preserve material disagreements, and attribute concerns to roles. Never infer views of failed roles.\nTask:\n" + π.task + "\nReports:\n" + json.dumps(completed), "council synthesis", {"model": synthesis_model} if synthesis_model else None)
121
123
  return dict(summary, status="partial" if failures else "success", failures=failures, result=result, reports=reports)
122
124
  except Exception as error:
123
- return dict(summary, status="partial", failures=failures, result=None, synthesisError=str(error), reports=reports, fallback=[{"role": item.get("role"), "status": "completed", "report": item["report"][:1200]} for item in completed])
125
+ return dict(summary, status="partial", failures=failures, result=None, synthesisError=str(error), reports=reports, fallback=[{"role": item.get("role"), "status": "completed", "report": item["report"] if isinstance(reports, dict) else item["report"][:1200]} for item in completed])
124
126
  ```
125
127
 
126
- Reserve at least the role count plus one agent call. Concurrency remains host-limited; usage settles afterward, not as a hard token reservation. Model keys must match a Pi registry key from `tools.models()` exactly, ignoring case; the program refuses a `models.aliases` name or a partial id, and checks every key before any agent runs. Whenever at least one seat completes, full role reports are parked to mesh under a `council/<timestamp>/reports` key carried by every outcome as `reports`: `mesh.get` it for audit or to retry a budget-starved synthesis with one plain agent, and `mesh.delete` it when no longer needed; on synthesis failure the fallback carries report heads plus that mesh key, so full texts never need to land in context. Every result lists `seats` with each role's pinned model, thinking, and status, plus `synthesisModel` when one was pinned. These are the models the program requested; keeping a run on its pinned model is the host's job. Successful synthesis returns only the compact decision, coverage, seats, and failures; raw reports return only on synthesis failure. A partial result is useful evidence with named gaps, not permission for an automatic whole-council rerun. Retry only the failed role or synthesis when needed. Do not use a council for a lookup.
128
+ Reserve at least the role count plus one agent call. Concurrency remains host-limited; usage settles afterward, not as a hard token reservation. Model keys must match a Pi registry key from `tools.models()` exactly, ignoring case; the program refuses a `models.aliases` name or a partial id, and checks every key before any agent runs. Whenever at least one seat completes, full role reports are parked to mesh under a `council/<timestamp>-<run>/reports` key carried by every outcome as `reports`: `mesh.get` it for audit or to retry a budget-starved synthesis with one plain agent, and `mesh.delete` it when no longer needed; on synthesis failure the fallback result carries report heads plus that mesh key, not the full texts; the synthesis prompt still embeds every completed report, so synthesis input grows with total report size. When mesh storage itself fails, `reports` is an `{"error": ...}` object instead of a key — never pass it to `mesh.get` or `mesh.delete` — and the synthesis-failure fallback then carries the full untruncated reports. A single completed role returns its full report directly as `result` without a synthesis call. Every result lists `seats` with each role's pinned model, thinking, and status, plus `synthesisModel` when one was pinned. These are the models the program requested; keeping a run on its pinned model is the host's job. Successful synthesis returns the compact decision, coverage, seats, failures, and `reports` (the mesh key, or the storage error object when parking failed); raw reports return only on synthesis failure. A partial result is useful evidence with named gaps, not permission for an automatic whole-council rerun. Retry only the failed role or synthesis when needed. Do not use a council for a lookup.
@@ -113,7 +113,8 @@ if (completed.length === 0) {
113
113
  }
114
114
  // Park completed reports in mesh before synthesis: an audit trail that survives this
115
115
  // program, and full-text recovery when synthesis fails or a budget runs out.
116
- const reportsKey = `council/${new Date().toISOString().slice(0, 19).replace(/[:T]/g, "-")}/reports`;
116
+ // The run suffix keeps same-second councils from overwriting each other: mesh.put is create-or-update.
117
+ const reportsKey = `council/${new Date().toISOString().slice(0, 19).replace(/[:T]/g, "-")}-${Math.random().toString(36).slice(2, 8)}/reports`;
117
118
  let reports: string | { error: string } = reportsKey;
118
119
  try {
119
120
  await mesh.put({
@@ -168,13 +169,13 @@ try {
168
169
  fallback: completed.map((outcome) => ({
169
170
  role: outcome.role,
170
171
  status: "completed",
171
- report: outcome.report.slice(0, 1200),
172
+ report: typeof reports === "string" ? outcome.report.slice(0, 1200) : outcome.report,
172
173
  })),
173
174
  };
174
175
  }
175
176
  ```
176
177
 
177
- Pass the task as `strings.task`, the JSON role array as `strings.roles`, and the synthesis model key as `strings.synthesis`; an empty `strings.synthesis` keeps the session default. A role is a string or `{ "role": "security", "model": "provider/id", "thinking": "high" }`, and a role without `model` runs on the session default. Model keys must match a Pi registry key from `tools.models()` exactly, ignoring case; the skill refuses a `models.aliases` name or a partial id, and checks every key before any agent runs. Every result lists `seats`, each with its role, pinned model and thinking, and status, plus `synthesisModel` when one was pinned. These are the models the skill requested; keeping a run on its pinned model is the host's job. Successful synthesis returns only the compact decision, coverage, seats, and failures. Whenever at least one seat completes, the full role reports are parked to mesh under a `council/<timestamp>/reports` key and every outcome carries it as `reports`: `mesh.get` it for audit or to retry a budget-starved synthesis with one plain agent, and `mesh.delete` it when no longer needed. On synthesis failure the fallback carries report heads plus that mesh key, so full texts never need to land in context; one surviving role returns directly without spending another agent call.
178
+ Pass the task as `strings.task`, the JSON role array as `strings.roles`, and the synthesis model key as `strings.synthesis`; an empty `strings.synthesis` keeps the session default. A role is a string or `{ "role": "security", "model": "provider/id", "thinking": "high" }`, and a role without `model` runs on the session default. Model keys must match a Pi registry key from `tools.models()` exactly, ignoring case; the skill refuses a `models.aliases` name or a partial id, and checks every key before any agent runs. Every result lists `seats`, each with its role, pinned model and thinking, and status, plus `synthesisModel` when one was pinned. These are the models the skill requested; keeping a run on its pinned model is the host's job. Successful synthesis returns the compact decision, coverage, seats, failures, and `reports` (the mesh key, or the storage error object when parking failed). Whenever at least one seat completes, the full role reports are parked to mesh under a `council/<timestamp>-<run>/reports` key and every outcome carries it as `reports`: check `typeof reports === "string"` first, because a failed `mesh.put` yields an `{ error }` object instead of a key — never pass that to `mesh.get` or `mesh.delete`, and the synthesis-failure fallback then carries the full untruncated reports. Otherwise `mesh.get` the key for audit or to retry a budget-starved synthesis with one plain agent, and `mesh.delete` it when no longer needed. On synthesis failure the fallback result carries report heads plus that mesh key, not the full texts; the synthesis prompt still embeds every completed report, so synthesis input grows with total report size. One surviving role returns directly without spending another agent call.
178
179
 
179
180
  Concurrent calls can overshoot an observational `tokenBudget` because usage settles afterward. Reserve at least `seats.length + 1` top-level agent calls when synthesis may run, and use a finite role set rather than relying on token accounting as a hard concurrent ceiling. A budget-exhausted synthesis loses nothing: the parked reports are complete, so re-run only the synthesis step.
180
181
 
@@ -21,7 +21,7 @@ For Pi leaf or recursive agents, selecting `cwd` neither grants nor requires pro
21
21
  - `runner` is `pi`, `claude`, or `veda` and defaults to `agents.runner` (`pi`). The `veda` runner drives the Veda CLI as a one-shot headless child; `agents.veda.backend` selects Veda’s underlying CLI (`agy`, `codex`, `claude-code`, `droid`, `pi`, or another backend registered by the installed Veda build), while `persona` selects its behavior. An explicit `agents.run({ model })` overrides `agents.veda.model`; if both are omitted, Veda selects its backend default (see `docs/agents.md`). Extensions may register more runner ids through `pi-fabric/runners`; requests needing a capability the runner does not declare fail before launch. A result with `outcome: "indeterminate"` means Fabric cannot confirm whether the work ran; it is never retried automatically, so inspect before re-running.
22
22
  - `kernel` is `"typescript"`, `"python"`, or `"inherit"`. Omitted/`inherit` takes the caller's `executor.kernel`; a concrete value lets the model or skill choose its strongest language for the **child**. It never switches the current `fabric_exec` program. Concrete values require Pi with Fabric extensions; Claude/Veda/`extensions: false` reject them, while omitted/`inherit` leaves those runners native with no `kernel` in status. Supported handles/results/status expose the resolved language. Workflow, RLM, and council requests forward `kernel` too. Python uses the caller's configured `executor.pythonRuntime` backend (`monty` by default); there is no public per-request backend selector. Monty is sandboxed and fails closed if its optional dependency is missing. CPython requires explicit configuration and outside schema enforce is trusted native code, not QuickJS isolation.
23
23
  - The caller's resolved language and configured Python backend are frozen before worker launch or durable/trajectory transfer. Recursive and alternate-cwd children inherit them through validated worker environment overrides after config merge, not the destination cwd's language defaults. Explicit kernels and inherited Python ensure Fabric is loaded even outside full-code mode. See [execution kernels](../../../../docs/kernels.md).
24
- - `transport` is one of `auto`, `process`, `tmux`, `screen`, `localterm`, `herdr` (default `process`). `auto` tries Herdr when the parent runs inside a Herdr workspace, then LocalTerm, tmux, screen, and process.
24
+ - `transport` is one of `auto`, `process`, `tmux`, `screen`, `localterm`, `herdr`, `herdr-core` (default `process`). `auto` first tries Herdr Core with injected `HC_TERMINAL_ID`/`HC_TERMINAL_SOCKET` and a reachable generation-1 service, then Herdr inside a Herdr workspace, LocalTerm, tmux, screen, and process. Explicit `herdr-core` requires the same Core context; it never starts a server. Core handles use terminal addresses and `hc attach tN`, not workspace/tab/pane IDs.
25
25
  - Pi `model` values resolve only within the execution owner's visible `tools.models()` / `agents.models({ runner: "pi" })` set; omitted uses `agents.model` or inherits the host model. Explicit values go through the `agents.switchModel` selector resolution: `models.aliases` names, exact matches, then the closest fuzzy match (pi-model-sort recency ties break toward the recently used model). Unresolved values and exhausted aliases fail before launch, and actor defaults or per-activation overrides are revalidated at their actual owner. Catalog-fresh or custom ids must first be visible in that registry. Claude values are `claude/<value>` keys from `agents.models({ runner: "claude" })`; omitted uses `agents.claude.model` or Claude Code's runtime default. Veda model strings continue to pass through to its backend unchanged. `agents.models()` defaults to the configured runner; `agents.models({ runner, model })` returns only the entries whose `key` equals `model` exactly (no alias or fuzzy resolution, `[]` when absent); Claude discovery is a local CLI control handshake and makes no model inference request.
26
26
  - `modelMatch: "exact"` (Pi runners only) selects a listed `provider/id` without aliases, closest or fuzzy matching, or alias thinking. Missing, malformed or unlisted models and non-Pi runners are refused before launch; `handoff`, `create`, and actor activations do not accept it. Admission is strict, and a child guard detects session model switches and some rewrites of known API payloads. **This is not a security guarantee or final-dispatch enforcement:** later hooks, unknown API payloads, providers and extension-made calls can route data elsewhere. Attribution may detect drift only after a call; do not rely on this mode to prevent data disclosure. See `docs/agents.md`. Omit `modelMatch` for default resolution.
27
27
  - `systemPrompt` is appended to the child's system prompt (Veda gets it as a `<system_instructions>` block); blank is ignored and durable `spawn` refuses it.
@@ -71,7 +71,7 @@ Lifecycle subscriptions are durable, source-qualified mesh routes. They let Main
71
71
  - `agents.subscribe({ from, events, to?, delivery, triggerTurn, once? })` creates a subscription. `from` is an exact participant id; `"main"` means the caller's lineage root. `to` defaults to that Main id.
72
72
  - `agents.subscriptions({ from?, to? })` lists project subscriptions.
73
73
  - `agents.unsubscribe({ id })` removes one.
74
- - `delivery` is `steer` or `followUp`. State `triggerTurn: true | false` explicitly; it controls whether delivery to an idle Main starts a turn.
74
+ - `delivery` is `steer` or `followUp`. Incoming Main feedback normalizes both to hidden steering (with a bounded sender notification); one-shot and actor target controls keep their existing semantics. State `triggerTurn: true | false` explicitly; false never starts idle Main. Actor output also uses hidden steering for legacy follow-up policies; `mailbox` and `nextTurn` remain intentional deferral choices.
75
75
  - `once: true` removes the subscription after its first successful matching delivery. Omitted keeps it active.
76
76
  - Creation starts at the current mesh sequence, so old lifecycle events are not replayed. Delivery cursors persist across owner restarts. Delivery is at-least-once across a crash between message insertion and cursor persistence; use the lifecycle event `id` to deduplicate side effects.
77
77
 
@@ -142,7 +142,7 @@ Every live root, one-shot/recursive agent, and persistent actor is represented i
142
142
  - `agents.peers()` remains the compatibility view of other live roots as `Peer <session-prefix>`. It is derived from `agents.members`, not maintained by a second registry.
143
143
  - A `<fabric-peers>` message in the transcript is a host notice, not a user request: it lists the other root sessions sharing this project's files by label and participant id, and is sent only when that set changes. Treat file or git changes you did not make as possibly theirs, and pass a listed id to `agents.steer` to coordinate.
144
144
  - `agents.status({ id })` accepts any known participant id. Local runs/actors return full local detail; remote participants return their bounded directory summary.
145
- - `agents.steer({ id, message, data? })` and `agents.followUp(...)` target Main, a live one-shot child, or an actor without discarding context.
145
+ - `agents.steer({ id, message, data? })` and `agents.followUp(...)` target Main, a live one-shot child, or an actor without discarding context. Incoming Main feedback always uses hidden steering, including when the sender requested `followUp`; the full message and structured data remain in context and audit, while UI notifications contain only a bounded sender/text preview. One-shot and actor mailbox controls retain their chosen operation.
146
146
  - `agents.stop({ id })` can stop a local or remotely owned agent/actor when its participant advertises `"stop"`. It returns the local agent result, local actor info, or an acknowledged remote control result according to the target.
147
147
  - Provider-registered work appears as `kind: "provider"` members with ids `provider:<provider>:<id>`. `agents.stop`, `agents.steer`, and `agents.followUp` accept those ids and call the provider; stop returns `{ ref, outcome: "confirmed" | "unconfirmed", detail? }`. Cancelling or timing out a program stops the non-detached provider work it started.
148
148
  - `agents.setSteeringMode({ id, mode })` / `agents.setFollowUpMode({ id, mode })` remain local one-shot controls.
@@ -155,7 +155,7 @@ const main = await agents.main();
155
155
  const project = await agents.members({ scope: "project" });
156
156
  const peerRoot = project.find((participant) => participant.kind === "root" && participant.id !== main.id);
157
157
  if (peerRoot) await agents.steer({ id: peerRoot.id, message: "Coordinate on the shared migration." });
158
- await agents.followUp({ id: main.id, message: "After the audit, reconcile the worker findings." });
158
+ await agents.steer({ id: main.id, message: "Reconcile the worker findings." });
159
159
  const handle = await agents.spawn({ task: "Audit auth flows.", tools: ["read", "grep", "find", "ls"] });
160
160
  // Watch progress, then redirect between turns without losing the child's context.
161
161
  const s = await agents.status({ id: handle.id });
@@ -190,7 +190,7 @@ call override → session binding → project default → Fabric or runner defau
190
190
  - `topics` lists durable mesh topics to subscribe to (see `mesh.md`).
191
191
  - `responseMode` is `text` (every non-empty response becomes an outbox message) or `directive` (validated `{ action, message?, data? }` where `action` is `silent`, `message`, or `stop`; the actor decides whether to intervene).
192
192
  - `delivery` is `mailbox`, `steer`, `followUp`, or `nextTurn`. An actor cannot escalate it in a response; the owner can replace it with `agents.setDeliveryPolicy({ id, delivery, triggerTurn, scope? })`.
193
- - `triggerTurn` is mandatory for `steer`/`followUp`: `true` starts Main when idle; `false` is passive and the delivered message visibly says it will not start Main. `mailbox`/`nextTurn` never start Main. `coalesce` is on by default.
193
+ - `triggerTurn` is mandatory for `steer`/`followUp`: `true` starts Main when idle; `false` is passive and the hidden context message says it will not start Main. The UI receives only a bounded sender notification, not a chat bubble. `mailbox`/`nextTurn` never start Main. `coalesce` is on by default.
194
194
  - `validWhile` is an optional pure synchronous predicate checked before an activation runs and again before its result is delivered. It receives immutable `{ activation, current }` facts. Return `false` or `{ valid: false, reason? }` to record the activation as stale and suppress delivery; an invalidated blocking `agents.ask()` rejects. The predicate source persists with project actors and global templates, so it cannot use closures, tools, promises, or host APIs.
195
195
  - `timeoutMs` follows the same floor as one-shot agents: omit it normally and set it only above `agents.timeoutMs` when an activation needs longer.
196
196
  - `tools` is the actor's persisted allowlist and defaults to `agents.defaultTools`. Replace it for future activations with `agents.setTools({ id, tools })`; an empty list disables optional tools. Pi actors retain the host-required `fabric_exec` tool unless created with `extensions: false`. Use `scope: "global"` to update a reusable template instead.