Merge pull request #196 from pylon-code/fix/prime-planning-capability

fix(server): report Prime plan observation

Author: rynfar

apps/server/src/provider/prime/PrimeAgentFeatureCapabilities.test.ts

@@ -30,6 +30,11 @@ describe("PrimeAgentFeatureCapabilities", () => {
       runtimeModes: ["approval-required", "full-access"],
       enforcement: "host-gated",
     });
+    expect(capabilities.planning).toMatchObject({
+      support: "read-only",
+      operations: ["observe"],
+    });
+    expect(capabilities.planning?.reason).toContain("formal Plan interaction mode");
     expect(capabilities.agents).toMatchObject({
       support: "read-write",
       operations: ["observe", "hierarchy", "live-activity", "message", "cancel", "set-depth"],
@@ -143,6 +148,11 @@ describe("PrimeAgentFeatureCapabilities", () => {
       runtimeModes: ["full-access"],
       enforcement: "none",
     });
+    expect(capabilities.planning).toMatchObject({
+      support: "read-only",
+      operations: ["observe"],
+    });
+    expect(capabilities.planning?.reason).toContain("standard ACP PlanUpdated");
     expect(capabilities.model?.operations).toEqual(["select"]);
     expect(capabilities.agents?.support).toBe("unavailable");
     expect(capabilities.goals?.support).toBe("unavailable");

apps/server/src/provider/prime/PrimeAgentFeatureCapabilities.ts

@@ -17,7 +17,12 @@ const shared = {
       "Pylon reports whether Prime Agent has a configured model provider; sign-in and sign-out remain owned by the Prime Agent CLI.",
     operations: ["status"] as const,
   },
-  planning: unavailable("Prime Agent does not expose a Pylon-compatible plan mode."),
+  planning: {
+    support: "read-only" as const,
+    reason:
+      "Pylon shows bounded Prime plan progress from the managed daemon bridge or standard ACP PlanUpdated events. Prime does not expose a compatible formal Plan interaction mode.",
+    operations: ["observe"] as const,
+  },
   goals: unavailable("Goal state is not projected into Pylon yet."),
   gates: unavailable("Autonomous gate mutation is not exposed by the loaded Prime Agent runtime."),
   automation: unavailable("Prime Agent automations are not projected into Pylon yet."),

docs/internals/prime-agent-daemon-parity.md

@@ -194,7 +194,10 @@ unavailable, and when custom Prime launch arguments are configured. Prime Agent
 the managed bridge and drops custom tool-result `details`, so those sessions retain only Prime's standard
 ACP `PlanUpdated` handling. Matching managed-tool parity in ACP requires a separately reviewed bounded
 content envelope and credible extension verifier, or another scoped transport; it is not implied by this
-ledger's daemon support.
+ledger's daemon support. The provider feature snapshot advertises planning as read-only `observe` in both
+modes because bounded plan progress reaches Pylon. It does not advertise `propose`, `update`, or
+`select-mode`; Prime has no compatible formal Plan interaction mode, and Pylon keeps that composer control
+hidden instead of synthesizing one with a hidden prompt.
 
 Any transcript mismatch, incomplete streaming snapshot, MCP reattachment failure, or unvalidated barrier
 fails the canonical turn once and disposes the uncertain native session. This recovery is in-memory only;

docs/user/providers-prime-agent.md

@@ -273,10 +273,12 @@ access off withholds both the tools and their instructions; it does not affect b
 - Prime Agent 0.8.1 has no daemon-native or operating-system sandbox policy. Supervised mode gates
   tool admission but does not restrict an approved tool.
 - Authentication is managed in Prime Agent, not Pylon.
-- Plan mode, provider-conversation rollback, and general per-item queue editing or reordering are
-  not supported yet. Pylon integrates Prime Agent 0.8.1's mutation API only for removing a lane's
-  sole item. With multiple count-only items, clients cannot identify a
-  specific target safely without exposing queued text, and ambiguous mutations are never retried.
+- Formal Plan interaction mode is not supported. Pylon still shows bounded plan progress during Build
+  turns through its managed daemon integration or plan updates from ACP compatibility mode.
+- Provider-conversation rollback and general per-item queue editing or reordering are not supported yet.
+  Pylon integrates Prime Agent 0.8.1's mutation API only for removing a lane's sole item. With multiple
+  count-only items, clients cannot identify a specific target safely without exposing queued text, and
+  ambiguous mutations are never retried.
 - Pylon does not present live Prime reasoning streams, durable or historical child-session transcripts,
   cost breakdowns, goal mutations, heartbeats, saved-session history, or native package or MCP catalogs as first-class features. Active children have only the bounded **Live activity** view described above.
 - Heartbeat creation remains unavailable even though Prime Agent 0.8.1 exposes heartbeat methods. Prime does not identify a scheduled run in a way Pylon can safely match to a durable conversation turn and filesystem checkpoint. Clearing a heartbeat also does not return its underlying session to the normal lifecycle, so stopping or deleting the Pylon thread could otherwise leave invisible work behind. Pylon will not offer creation until recovery, clearing, stopping, and deletion can be made authoritative.