You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upstream_support: Prime has queue, background, cancellation, reconnect, and event primitives, but no optional contract proving per-prompt ownership, delivery, provenance, terminal usage, and durable generation-scoped recovery together.
96
+
revisit_when:
97
+
- Prime upstream ships an equivalent negotiated lifecycle with exact delivery, provenance, scoped cancellation, recovery, and per-prompt usage guarantees.
98
+
- Pylon can remove the fork contract without weakening stock-Prime fallback behavior.
Copy file name to clipboardExpand all lines: .pylon/upstream-review.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,3 +34,14 @@ This ledger records Prime upstream evidence and the decision taken for each over
34
34
-`kernel-protocol-test-fixtures`: **adopt** the exact three-line repair from open Prime PR #1886 at `a97f6995d39f2cccbd33123ab246f9786fc8ac13`. Preserve that upstream commit as a merge parent rather than creating Pylon-specific behavior.
35
35
- Validation: the focused Prime Inference catalog test passed all 12 cases; the two protocol fixture suites passed all 39 cases; `npm run check` passed Biome over 937 files, the TypeScript check, installer rendering, and the browser smoke check; `git diff --check` passed.
36
36
- Revisit when Prime adopts deterministic catalog fixtures or repo-owned structural invariants, or stops regenerating vendor pricing before tests and releases.
- Reviewed Prime PRs #800, #1239, #1859, and #1861 plus the current daemon prompt, queue, cancellation, compact stream, worker recovery, update restart, and agent-connection paths. These changes provide useful primitives but no single optional contract proves exact per-prompt ownership, delivery, provenance, scoped cancellation, reconnect/recovery, generation fencing, request identity, and terminal usage.
42
+
-`correlated-prompt-lifecycle`: **hybridize**. Retain Prime's existing session and queue machinery behind Pylon's optional `correlated_prompt_lifecycle_v1` daemon/client capability. Keep protocol version 7, use additive schema revision 24, keep the capability out of default and required client capability sets, and shape lifecycle/provenance only for clients that explicitly negotiate it.
43
+
- The fork candidate adds dedicated correlated submit, cancel, and read-only lifecycle commands; exact session-generation fencing; canonical request fingerprints and conflicting retry rejection; durable command and worker recovery; delivery-aware cancellation; bounded lifecycle records/tombstones; prompt or session event provenance; per-prompt terminal usage; and fail-closed reconnect, replacement, and recovery validation. Stock clients and daemons retain their legacy prompt behavior.
44
+
- Replacement and reload are fenced at the session runtime boundary while any correlated lifecycle is nonterminal. Worker recovery replays only queued or selected actions; preparation that may already have run arbitrary extension hooks is terminalized as failed instead of being replayed.
- Validation: the post-rebase lifecycle, connection, supervisor, runtime, recovery, and ledger checkpoint passed 564 tests across 17 files. The final changed-boundary checkpoint passed 202 connection and supervisor-monitor tests; the clean supervisor process checkpoint passed 10 tests with 8 fixture-gated skips. `npm run check` passed Biome over 940 files, TypeScript, installer rendering, and browser smoke; `git diff --check` passed. Independent final and follow-up audits found no remaining P0 or P1 findings.
47
+
- Revisit when Prime upstream ships an explicitly negotiated equivalent with the same delivery, provenance, scoped cancellation, recovery, generation, retry-integrity, privacy, and per-prompt usage guarantees.
0 commit comments