@mono-agent/agent-app 0.14.0 → 0.15.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 (121) hide show
  1. package/README.md +3 -7
  2. package/dist/app-config.d.ts.map +1 -1
  3. package/dist/app-config.js +3 -0
  4. package/dist/app-config.js.map +1 -1
  5. package/dist/app-controller-channels.d.ts +41 -7
  6. package/dist/app-controller-channels.d.ts.map +1 -1
  7. package/dist/app-controller-channels.js +2 -3
  8. package/dist/app-controller-channels.js.map +1 -1
  9. package/dist/app-controller-continuation.d.ts +43 -11
  10. package/dist/app-controller-continuation.d.ts.map +1 -1
  11. package/dist/app-controller-continuation.js.map +1 -1
  12. package/dist/app-controller-lifecycle.d.ts +34 -5
  13. package/dist/app-controller-lifecycle.d.ts.map +1 -1
  14. package/dist/app-controller-lifecycle.js.map +1 -1
  15. package/dist/app-controller-maintenance.d.ts +45 -8
  16. package/dist/app-controller-maintenance.d.ts.map +1 -1
  17. package/dist/app-controller-maintenance.js.map +1 -1
  18. package/dist/app-controller-memory-health.d.ts +39 -10
  19. package/dist/app-controller-memory-health.d.ts.map +1 -1
  20. package/dist/app-controller-memory-health.js.map +1 -1
  21. package/dist/app-controller-memory.d.ts +27 -5
  22. package/dist/app-controller-memory.d.ts.map +1 -1
  23. package/dist/app-controller-memory.js +0 -1
  24. package/dist/app-controller-memory.js.map +1 -1
  25. package/dist/app-controller-responder.d.ts +53 -7
  26. package/dist/app-controller-responder.d.ts.map +1 -1
  27. package/dist/app-controller-responder.js +1 -4
  28. package/dist/app-controller-responder.js.map +1 -1
  29. package/dist/app-controller-traceability.d.ts +63 -14
  30. package/dist/app-controller-traceability.d.ts.map +1 -1
  31. package/dist/app-controller-traceability.js.map +1 -1
  32. package/dist/app-controller-types.d.ts +63 -0
  33. package/dist/app-controller-types.d.ts.map +1 -0
  34. package/dist/app-controller-types.js +2 -0
  35. package/dist/app-controller-types.js.map +1 -0
  36. package/dist/app-controller-utils.d.ts +1 -1
  37. package/dist/app-controller-utils.d.ts.map +1 -1
  38. package/dist/app-controller.d.ts +5 -62
  39. package/dist/app-controller.d.ts.map +1 -1
  40. package/dist/app-controller.js +0 -6
  41. package/dist/app-controller.js.map +1 -1
  42. package/dist/background-lifecycle-utils.d.ts +27 -0
  43. package/dist/background-lifecycle-utils.d.ts.map +1 -0
  44. package/dist/background-lifecycle-utils.js +69 -0
  45. package/dist/background-lifecycle-utils.js.map +1 -0
  46. package/dist/background-log-maintenance.d.ts +6 -0
  47. package/dist/background-log-maintenance.d.ts.map +1 -0
  48. package/dist/background-log-maintenance.js +185 -0
  49. package/dist/background-log-maintenance.js.map +1 -0
  50. package/dist/background.d.ts +2 -4
  51. package/dist/background.d.ts.map +1 -1
  52. package/dist/background.js +3 -263
  53. package/dist/background.js.map +1 -1
  54. package/dist/channel-plugins.d.ts +2 -11
  55. package/dist/channel-plugins.d.ts.map +1 -1
  56. package/dist/channel-plugins.js +63 -60
  57. package/dist/channel-plugins.js.map +1 -1
  58. package/dist/channel-status-display.js +2 -6
  59. package/dist/channel-status-display.js.map +1 -1
  60. package/dist/channels.d.ts +5 -6
  61. package/dist/channels.d.ts.map +1 -1
  62. package/dist/channels.js +7 -5
  63. package/dist/channels.js.map +1 -1
  64. package/dist/cli-args.d.ts.map +1 -1
  65. package/dist/cli-args.js +50 -0
  66. package/dist/cli-args.js.map +1 -1
  67. package/dist/cli-background-command.js +1 -1
  68. package/dist/cli-background-command.js.map +1 -1
  69. package/dist/cli-validate-config-command.d.ts.map +1 -1
  70. package/dist/cli-validate-config-command.js +12 -8
  71. package/dist/cli-validate-config-command.js.map +1 -1
  72. package/dist/config-reference.d.ts +4 -1
  73. package/dist/config-reference.d.ts.map +1 -1
  74. package/dist/config-reference.js +242 -65
  75. package/dist/config-reference.js.map +1 -1
  76. package/dist/configured-agent.d.ts +2 -8
  77. package/dist/configured-agent.d.ts.map +1 -1
  78. package/dist/configured-agent.js +3 -25
  79. package/dist/configured-agent.js.map +1 -1
  80. package/dist/consumer-contract.d.ts.map +1 -1
  81. package/dist/consumer-contract.js +2 -4
  82. package/dist/consumer-contract.js.map +1 -1
  83. package/dist/doctor-observability.d.ts +7 -0
  84. package/dist/doctor-observability.d.ts.map +1 -0
  85. package/dist/doctor-observability.js +80 -0
  86. package/dist/doctor-observability.js.map +1 -0
  87. package/dist/doctor-types.d.ts +17 -0
  88. package/dist/doctor-types.d.ts.map +1 -0
  89. package/dist/doctor-types.js +2 -0
  90. package/dist/doctor-types.js.map +1 -0
  91. package/dist/doctor.d.ts +2 -12
  92. package/dist/doctor.d.ts.map +1 -1
  93. package/dist/doctor.js +7 -106
  94. package/dist/doctor.js.map +1 -1
  95. package/dist/first-run-readiness.d.ts +1 -1
  96. package/dist/first-run-readiness.d.ts.map +1 -1
  97. package/dist/first-run-readiness.js +1 -1
  98. package/dist/first-run-readiness.js.map +1 -1
  99. package/dist/index.d.ts +0 -2
  100. package/dist/index.d.ts.map +1 -1
  101. package/dist/index.js +0 -1
  102. package/dist/index.js.map +1 -1
  103. package/dist/managed-web-logs.d.ts +16 -0
  104. package/dist/managed-web-logs.d.ts.map +1 -0
  105. package/dist/managed-web-logs.js +153 -0
  106. package/dist/managed-web-logs.js.map +1 -0
  107. package/dist/posted-reply-history.d.ts.map +1 -1
  108. package/dist/posted-reply-history.js +3 -0
  109. package/dist/posted-reply-history.js.map +1 -1
  110. package/dist/web-command.d.ts +4 -1
  111. package/dist/web-command.d.ts.map +1 -1
  112. package/dist/web-command.js +31 -1
  113. package/dist/web-command.js.map +1 -1
  114. package/package.json +16 -16
  115. package/schema/mono-agent.config.schema.json +280 -162
  116. package/skills/mono-agent-composer/references/config-blueprint.md +4 -11
  117. package/skills/mono-agent-composer/references/discovery-questions.md +1 -1
  118. package/skills/mono-agent-composer/references/feature-coverage.md +4 -5
  119. package/skills/mono-agent-composer/references/package-map.md +4 -5
  120. package/skills/mono-agent-composer/references/playbooks.md +2 -2
  121. package/skills/mono-agent-composer/references/validation.md +1 -1
@@ -18,7 +18,8 @@ Every framework capability and how a composed agent reaches it. This table is th
18
18
  | Pi-native transport, retry, and durable provider-session tuning | config | `providers.piNative.{transport,piMaxRetries,maxRetryDelayMs,piSessionsRoot}` | `runtime.pi-native-tuning` |
19
19
  | Tool-output bloat guard, cost tracking | auto | built into every run | — |
20
20
  | Context handling / auto-compaction | config + provider | `runtime.compaction.*` (matching `MONO_AGENT_COMPACTION_*`) controls adaptive Pi compaction. Omitted budgets derive from the active model window; reactive recovery re-prompts exactly once only after a verified reduction, and persistent `context_limit` advances to a configured fallback | `runtime.context-compaction` |
21
- | Structured output (JSON schema), live input steering | code | harness `runtimeOptions` | — |
21
+ | Structured output (JSON schema) | code | harness `runtimeOptions.outputSchema` | — |
22
+ | Live input steering | auto + code | built into ordinary Slack, Telegram, and web-console turns; custom hosts use `runtimeOptions.liveInput` | — |
22
23
  | Tool approval gates (risk tiers, timeouts, always-allow) | code | `createMonoRuntime({ onToolApprovalRequest, ... })` — needs a host UI | — |
23
24
  | Fully custom runtime | code | `startMonoAgentApp({ runtime })` | — |
24
25
 
@@ -38,7 +39,7 @@ Every framework capability and how a composed agent reaches it. This table is th
38
39
  | BuJo memory (journal + LLM capture/reconcile ADD/UPDATE/SUPERSEDE/NOOP + entity graph + auto-scheduled consolidation; needs embeddings + an app-level `memory.llm`) | config | `memory.mode: "bujo"`, `path`; selected Ollama/LM Studio/OpenAI embeddings are independent from explicit `memory.llm` with `provider: "ollama"` (`model`, optional `endpoint`) or `provider: "agent-host"` (`model` is an SDK runtime model ref, optional `executionMode: "sdk"`) — see `docs/memory/index.md` | `memory.bujo` |
39
40
  | Supermemory external backend (server-side extraction/consolidation; async ingestion; explicitly installed plugin) | config | `memory.backend: "supermemory"`, `memory.writeMode`, `memory.supermemory.{baseUrl,apiKey,apiKeyEnv,container,timeoutMs,exposeMcpServer}`; install the exact matching `@mono-agent/memory-supermemory` version | `memory.backend-supermemory` |
40
41
  | BuJo consolidation auto-scheduler (projection-only `index.md` refresh + empty `future-log.md` stub + duplicate-group reporting; in-app, no external cron needed) | config | `memory.consolidation.{enabled,cron}` (five-field UTC, default `0 */2 * * *`, no hashed `H`); env `MONO_AGENT_MEMORY_CONSOLIDATION_CRON`, `MONO_AGENT_MEMORY_CONSOLIDATION_ENABLED` | `memory.bujo-consolidation` |
41
- | Memory maintenance CLI | cli | `mono-agent memory <subcommand>` from the agent folder (stats/today/show/search/top/audit/inspect/rebuild/rollback/…). The standalone `memory-bujo <subcommand> <root>` CLI was removed — its bin now prints a redirect and exits non-zero; routine BuJo consolidation runs via the in-app scheduler | — |
42
+ | Memory maintenance CLI | cli | `mono-agent memory <subcommand>` from the agent folder (stats/today/show/search/top/audit/inspect/rebuild/rollback/…). The standalone `memory-bujo <subcommand> <root>` CLI and bin were removed; routine BuJo consolidation runs via the in-app scheduler | — |
42
43
  | Config-aware memory preview CLI (stats/today/show/search/top plus metadata-only audit; remains available when the live recall tool is disabled; local search warns and falls back to FTS-only when embeddings are down) | cli | `mono-agent memory stats\|today\|show <date>\|search <query>\|top\|audit [--limit <n>] [--json]` | — |
43
44
  | Memory liveness check (managed tier/provider/model/dimension identity; provider-native typed discovery plus real finite-vector/dimension probe for Ollama or LM Studio; declared auth env; BuJo LLM config + consolidation cadence; no cross-provider fallback) | cli | `mono-agent validate` | — |
44
45
  | Memory write modes and per-turn BuJo capture | config | `memory.writeMode`: `disabled`, `append-host-summary`, or `capture`; capture requires `memory.mode: "bujo"` | `memory.write-mode`, `memory.per-turn-capture` |
@@ -78,7 +79,6 @@ Every framework capability and how a composed agent reaches it. This table is th
78
79
  | A2A provider (Agent Card, JSON-RPC + REST, streaming, bearer, configurable request-body limit, opt-in durable dispatch identity) | config | `channels.plugins[].package: "@mono-agent/a2a-adapter"` plus plugin `config.provider` (including `maxRequestBytes` and `idempotency.{namespace,stateDir,retentionMs,maxRecords}`), `config.agent`, `config.skill`; `config.enabled` is canonical | `a2a.provider` |
79
80
  | A2A consumer settings (remote agent URLs, timeouts) and calls | config + code | same A2A plugin entry's `config.consumer`; calls via `sendA2AMessage({ idempotencyKey })` or `createA2AConsumerResponder({ idempotencyKeyForRequest })` | `a2a.consumer` |
80
81
  | TUI stream endpoint (operator console transport) | config | `tui.{enabled,host,port,basePath,allowNonLoopback,apiKey}`; default on, loopback | `tui.stream-endpoint` |
81
- | Live event relay (read-only run-event SSE for web) | config | `live.{enabled,host,port,basePath,allowNonLoopback,apiKey}`; default on, loopback | `live.event-relay` |
82
82
  | Cron jobs (five-field expressions, timezones, stable job-id-seeded `H`; agent-app pins overlap to skip) | config + code | `cron.jobs[]`, including per-job `model` / `effort`; single-job `MONO_AGENT_CRON_*`, or one markdown file per job in `cron.dir` / `MONO_AGENT_CRON_DIR` (default `cron/`); queue/replace controls are programmatic-only `startCronAdapter` options | `cron.scheduled-prompts` |
83
83
  | Cron per-run watchdog | config + code | `cron.jobs[].maxRunMs` or `maxRunMs` frontmatter; programmatic adapter fallback via `startCronAdapter({ maxRunMs })` | `cron.run-watchdog` |
84
84
  | Per-request runtime model and effort overrides | config + code | `cron.jobs[].{model,effort}`; `webhook.endpoints[].{model,effort}` plus request body `{model,effort}` (request wins); Telegram `/model` and `/effort`; Slack Block Kit selectors through thread-local `@agent /model` / `@agent /effort` and channel-wide `/<bot>-model` / `/<bot>-effort`, all over configured primary/fallback models | `runtime.per-trigger-model` |
@@ -90,13 +90,12 @@ Every framework capability and how a composed agent reaches it. This table is th
90
90
 
91
91
  | Capability | Coverage | Where | Registry config ids |
92
92
  | --- | --- | --- | --- |
93
- | JSONL run artifacts (events + summaries; strings capped; non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; free text is not content-scanned) | config | `artifacts.dir`, `artifacts.retention`, `artifacts.memoryRetention` | `observability.jsonl-artifacts` |
93
+ | JSONL run artifacts (events + summaries; strings capped; non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; retained free text is scanned for a closed set of high-confidence credential shapes) | config | `artifacts.dir`, `artifacts.retention`, `artifacts.memoryRetention` | `observability.jsonl-artifacts` |
94
94
  | Trace-source registry (heartbeat manifests `mono-agent status` reads) | config | `traceability.{registryDir,sourceId,sourceLabel,heartbeatMs,staleAfterMs,globalDiscovery}` | `observability.trace-registry` |
95
95
  | Phoenix trace viewer (best-effort terminal-batched OTLP exporter; independent local JSONL has bounded terminal snapshots and can lose RAM-buffered events on crash) | config | `observability.exporters` (phoenix entry) | `observability.phoenix-exporter` |
96
96
  | Operator console (live chat with thinking/tool/telemetry insight, run replay, config view) | cli | `mono-agent tui [--agent <label>]`; agents serve the `tui` stream endpoint by default (`tui.enabled`, loopback) | — |
97
97
  | Always-on multi-agent web console (persistent conversations and same-thread quotes, fixed compact/expanded rail, offline-agent filtering that always preserves pinned/selected agents, alive-page/PWA response notifications, attachments, model/effort selection, reasoning/tools, hidden telemetry-backed cumulative context usage, cancellation) | cli | `mono-agent web start\|stop\|restart\|status\|logs\|run`; bare `mono-agent web` is read-only status/help; default `0.0.0.0:5050`, `--loopback` narrows to `127.0.0.1`; notifications require explicit per-origin browser permission plus a secure context and do not use Web Push; package `@mono-agent/web`; no app authentication, so LAN/Tailnet reachability is the access boundary | — |
98
98
  | Managed proposal-only SELF-CONFIG conversation | cli + tool | macOS `mono-agent tui --configure` attaches to the authoritative background agent; persistent marker and capability map; stable configuration conversation with a fresh proposal capability after each checkpoint; host-gated `ProposeAgentConfiguration`; approval restarts and waits for readiness, failed start rolls files/agent back; only quitting exits. `--local` is ordinary chat only; off macOS configuration is manual | — |
99
- | Session Recorder web PWA (read-only run browser) | cli | Command removed — use `mono-agent tui` (recorded-run replay) or `mono-agent web` (live console); the `@mono-agent/session-web` package still ships without a CLI launcher, and `MONO_AGENT_WEB_AUTH_TOKEN` is no longer read by any code (its only reader, the removed `sessions` command, is gone) | — |
100
99
  | Setup presets (saved answer-sets: generate config + `.env.example` + checklist) | cli | `mono-agent presets list\|show <id>`, `mono-agent init --preset <id> --yes` (the `recipes` command and `--recipe` alias were removed) | — |
101
100
  | Interactive setup wizard (preset/custom; exact `IDENTITY.md` → `## Role` prompt/outcome; walks model→channels→memory→tools→sandbox→observability; Journal/BuJo explicitly choose Ollama or LM Studio service root/model/dimension/optional auth env using typed discovery and a real probe; macOS starts the background agent before persistent SELF-CONFIG) | cli | `mono-agent init` (no flags, on a TTY; `setup` alias); manual embedding entry still requires readiness probe; flags/non-TTY stay scaffold-only; unsupported platforms use manual configuration/foreground start/ordinary TUI | — |
102
101
  | Tools reporting + no-tools guardrail (allow-all → `All tools allowed`; explicit empty `allowedTools: []` → `waiting`; unknown-tool "did you mean"; send-tool/channel cross-checks) | cli | part of `mono-agent validate`/`doctor`; the wizard's tools step | — |
@@ -105,7 +105,7 @@ Communication adapters are edge packages. They accept an `AgentResponder` and ow
105
105
  | Slack | `@mono-agent/slack-adapter` | Allowed channel or DM gets the final reply |
106
106
  | WhatsApp | `@mono-agent/whatsapp-adapter` (external channel plugin) | Allowed sender/group trigger produces a reply |
107
107
  | OpenAI-compatible API | `@mono-agent/openai-api-adapter` | `curl /v1/models` and `/v1/chat/completions` |
108
- | Operator endpoints | `@mono-agent/operator-adapter` | `mono-agent tui` and `mono-agent web` connect for chat; the read-only `live` relay feeds operator tooling such as the `@mono-agent/session-web` PWA |
108
+ | Operator endpoint | `@mono-agent/operator-adapter` | `mono-agent tui` and `mono-agent web` connect for chat |
109
109
  | A2A provider/consumer | `@mono-agent/a2a-adapter` (external channel plugin) | Send text to the Agent Card URL |
110
110
  | Webhook | `@mono-agent/webhook-adapter` | `curl` the configured invocation path (with `Authorization: Bearer ...` when `apiKey` is set) |
111
111
  | Cron | `@mono-agent/cron-adapter` | One scheduled or manually triggered invocation |
@@ -116,13 +116,12 @@ Adapters must not import the harness, runtime adapter, memory package (`@mono-ag
116
116
 
117
117
  Use:
118
118
 
119
- - `@mono-agent/tui` for the pi-tui operator console (`mono-agent tui`): live chat with structured stream-event insight, recorded-run replay, and config view. Remote event frames have a strict 256 KiB UTF-8 NDJSON cap: assistant-thought/tool-call payload fields are reduced and remeasured, while another oversized variant or a reducible event whose minimal form still does not fit becomes a bounded `oversized_event` marker. Other frame kinds are unaffected, and replay contains only key-redacted, capped events that reached terminal JSONL persistence.
119
+ - `@mono-agent/tui` for the pi-tui operator console (`mono-agent tui`): live chat with structured stream-event insight, recorded-run replay, and config view. Remote event frames have a strict 256 KiB UTF-8 NDJSON cap: assistant-thought/tool-call payload fields are reduced and remeasured, while another oversized variant or a reducible event whose minimal form still does not fit becomes a bounded `oversized_event` marker. Other frame kinds are unaffected, and replay contains only sensitive-key-redacted, credential-scanned, capped events that reached terminal JSONL persistence.
120
120
  - `@mono-agent/web` for the assistant-ui always-on browser console (`mono-agent web`): persistent multi-agent conversations and same-thread quotes, fixed compact/expanded agent navigation with offline filtering, explicit alive-page/PWA response notifications, device-local file picking, streamed reasoning/tools, internal telemetry-backed cumulative context usage, cancellation, LAN-default HTTP on port 5050, and conflict-safe optional Tailscale Serve HTTPS. It has no app login; network reachability is the access boundary.
121
- - `@mono-agent/session-web` for the read-only Session Recorder PWA. Its `sessions` launcher command was removed (use `mono-agent tui` for recorded-run replay or `mono-agent web` for the live console); the package still ships without a CLI command and full retirement is pending. Local artifact paging and live relay aggregation stay on its port 4599 surface.
122
- - `@mono-agent/operator-adapter` for the loopback NDJSON stream endpoint the TUI and web chat console connect to (`tui` config section, on by default) and the read-only live SSE endpoint operator tooling observes (`live` config section, on by default).
121
+ - `@mono-agent/operator-adapter` for the loopback NDJSON stream endpoint the TUI and web chat console connect to (`tui` config section, on by default).
123
122
  - `@mono-agent/observability` for JSONL event artifacts, summaries, trace-source registration, and the `@mono-agent/observability/otel` Phoenix OTLP exporter configured via `observability.exporters`.
124
123
 
125
- Traceability is local-first. A running host registers a source manifest; `mono-agent status` reads the trace-source registry to report live sources, and artifacts are keyed by `(sourceId, runId)` so duplicate run ids do not collide. Phoenix is the recommended trace viewer when an `observability.exporters` (phoenix) entry is configured; its terminal-batched export is best-effort. Independently, the local recorder writes empty events plus a `running` summary at start and a key-redacted, capped snapshot at finish/fail. Events stay in RAM between those boundaries, so a crash can lose them. Without Phoenix, those bounded terminal JSONL snapshots are the only local run record.
124
+ Traceability is local-first. A running host registers a source manifest; `mono-agent status` reads the trace-source registry to report live sources, and artifacts are keyed by `(sourceId, runId)` so duplicate run ids do not collide. Phoenix is the recommended trace viewer when an `observability.exporters` (phoenix) entry is configured; its terminal-batched export is best-effort. Independently, the local recorder writes empty events plus a `running` summary at start and a sensitive-key-redacted, credential-scanned, capped snapshot at finish/fail. Events stay in RAM between those boundaries, so a crash can lose them. Without Phoenix, those bounded terminal JSONL snapshots are the only local run record.
126
125
 
127
126
  ## Multi-Agent Join
128
127
 
@@ -190,7 +190,7 @@ const orchestrator = await createConfiguredAgentResponder({
190
190
 
191
191
  ## 10. Phoenix-observed agent with the TUI
192
192
  **For:** an agent builder evaluating runs in a tracing dashboard.
193
- **Goal:** run locally with the TUI, attempt a best-effort terminal-batched Phoenix export, and retain a key-redacted, capped local JSONL snapshot after terminal persistence. A pre-terminal crash can omit the Phoenix batch and lose RAM-buffered JSONL events.
193
+ **Goal:** run locally with the TUI, attempt a best-effort terminal-batched Phoenix export, and retain a sensitive-key-redacted, credential-scanned, capped local JSONL snapshot after terminal persistence. A pre-terminal crash can omit the Phoenix batch and lose RAM-buffered JSONL events.
194
194
  **Features:** `observability.phoenix-exporter`, `observability.jsonl-artifacts`, `observability.trace-registry`, `tui.chat`.
195
195
 
196
196
  ```json
@@ -202,7 +202,7 @@ const orchestrator = await createConfiguredAgentResponder({
202
202
  }
203
203
  ```
204
204
  **Steps:** start Phoenix (6006) → `init` → add artifacts/traceability/exporter → `validate` (POSTs an empty protobuf) → `start` (prints the Phoenix endpoint) → `mono-agent tui`.
205
- **Smoke:** complete a TUI prompt; confirm a JSONL artifact AND a Phoenix trace with merged tool spans under the project. Artifact/export strings are capped; non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; free text is not content-scanned or scrubbed.
205
+ **Smoke:** complete a TUI prompt; confirm a JSONL artifact AND a Phoenix trace with merged tool spans under the project. Strings are capped. For local artifacts, non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; retained free text is scanned for a closed set of high-confidence credential shapes. Phoenix applies that scan only when `contentPatternRedaction` is true.
206
206
 
207
207
  ## 11. Backfill historical runs to Phoenix
208
208
  **For:** an ops engineer onboarding observability after the fact.
@@ -124,7 +124,7 @@ pnpm run test:demo
124
124
  | A2A | Send text to the Agent Card URL with `sendA2AMessage()`. |
125
125
  | Webhook | `curl` the invocation path and inspect the response body/status. |
126
126
  | Cron | Run a one-off scheduled invocation or wait for one tick. |
127
- | Observability | Confirm a run writes a JSONL artifact with strings capped: non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; free text is not content-scanned. If an `observability.exporters` Phoenix entry is set, confirm the trace appears in Phoenix. |
127
+ | Observability | Confirm a run writes a JSONL artifact with strings capped: non-numeric values under sensitive-looking object keys are redacted; numeric values under matched keys are retained; retained free text is scanned for a closed set of high-confidence credential shapes. If an `observability.exporters` Phoenix entry is set, confirm the trace appears in Phoenix. |
128
128
  | Memory recall tool | With any memory tier configured (`memory.recallTool.enabled` defaults on), ask the agent to recall an old note and confirm `MemoryRecall` appears separately from action-tool allowlists and returns it. |
129
129
  | Semantic memory search | With `memory.embeddings` set, first prove the configured provider only: Ollama model advertises `embedding` through `/api/show` and answers `/api/embed`, or LM Studio model has exact `type: "embedding"` in `/api/v1/models` and answers `/v1/embeddings`. Verify the finite vector dimension matches config, then ask a paraphrased question about an old note and confirm `MemoryRecall` returns it. Never accept a cross-provider fallback as proof. |
130
130