@adhdev/daemon-core 1.0.18-rc.20 → 1.0.18-rc.4

package/src/providers/cli-provider-instance-types.ts

@@ -66,15 +66,6 @@ export type CompletedFinalizationBlock = {
     // preamble summary (evidenceLevel=insufficient) into the append-only ledger before the
     // worker's next approval turn resumes. Independent of valley length.
     holdForTranscript?: boolean;
-    // (CANON-C EARLY-EMIT FLOOR) Set on a missing_final_assistant block whose provider has NO
-    // external transcript source to trail — a PTY-parsed provider (codex-cli) or one that merely
-    // requires a final assistant before idle. For those the CANON-C decoupled-immediate emit is a
-    // pure timing guess (no separate transcript will land to upgrade it), so it must observe the
-    // CANON_C_MISSING_ASSISTANT_MIN_ELAPSED_MS floor rather than fire at the ~13s first-poll
-    // waitedMs. A native-source block (claude-cli external-native, where the transcript legitimately
-    // trails the idle transition by a write) deliberately does NOT set this — its immediate emit is
-    // correct and is upgraded by the transcript reconcile.
-    noExternalTranscriptSource?: boolean;
 };
 
 export type CompletionFinalAssistantEvidence = {
@@ -96,25 +87,6 @@ export type ExternalTranscriptProbe = {
 
 export const COMPLETED_FINALIZATION_RETRY_MS = 1000;
 export const COMPLETED_FINALIZATION_MAX_WAIT_MS = 30_000;
-// (CANON-C EARLY-EMIT FLOOR) Minimum elapsed time before the CANON-C transcript-evidence
-// gate (allowTimeout blocks) may fire its decoupled-immediate completion for a block that
-// has NO final-assistant evidence (missing_final_assistant, finalAssistantPresent=false).
-//
-// CANON-C deliberately decouples the idle NOTIFICATION from the transcript's final-assistant
-// turn: for a native-source worker whose transcript write merely trails the idle transition,
-// emitting immediately (weak, later upgraded) is correct. But the SAME allowTimeout path also
-// carries codex/antigravity PLAIN terminal blocks whose on-screen "final" assistant never
-// landed — there the immediate emit fires at whatever tiny waitedMs the first completion-gate
-// poll observed (~13s live), stamping evidenceLevel=insufficient and racing the transcript
-// before it can catch up or the 180s mesh-worker stall watchdog can arm. Requiring a minimum
-// dwell gives the transcript a window to land (clearing the block for a GENUINE emit) and lets
-// the stall watchdog own long turns, while still emitting a weak completion promptly once the
-// floor is met so a genuinely-answerless turn is never wedged. A block WITH final-assistant
-// evidence present is unaffected (it takes the normal emit path, not this floor). Scoped (at
-// the call site) to the missing_final_assistant transcript-evidence gate on mesh workers.
-// Sized so a short transcript-write lag resolves under it while staying well below the 30s
-// COMPLETED_FINALIZATION_MAX_WAIT_MS cap that force-releases the weak completion regardless.
-export const CANON_C_MISSING_ASSISTANT_MIN_ELAPSED_MS = 20_000;
 // (FALSEIDLE-BGCHILD-a) Minimum generating→idle settle window for native-history mesh worker
 // sessions. Native-history providers (e.g. claude-cli) normally flush the completion with
 // flushDelay=0 — the transcript is authoritative, so there is no reason to wait. But a worker
@@ -148,31 +120,6 @@ export const NATIVE_HISTORY_MESH_IDLE_SETTLE_MS = 4000;
 // met. Scoped (at the call site) to autonomous mesh sessions, so interactive sessions are
 // untouched.
 export const PTY_PARSED_FINAL_ASSISTANT_QUIET_DWELL_MS = 1200;
-// (ANTIGRAVITY-30S-CAP-PREMATURE) Minimum PTY quiet dwell required before the
-// COMPLETED_FINALIZATION_MAX_WAIT_MS (30s) cap may RELEASE an antigravity `holdForTranscript`
-// block into the forced weak completion. Antigravity is a native-source provider: its
-// idle/generating verdict is PTY-screen-derived, but its assistant answer lands in
-// native-history and can legitimately lag past 30s on a long turn (tool phase + slow reply).
-// The 30s cap releases on ELAPSED TIME, not proof-of-idle — so on a long turn it fired a
-// premature completed/idle to the coordinator while the PTY was still generating (live-repro:
-// a routed RCA task emitted "completed" in 10s with no result). Require instead that the PTY
-// has been quiet (no raw output) for at least this long AND the adapter reports no pending
-// response before the cap may force-emit. A genuinely quiescent tool-only turn (no assistant
-// bubble) has a stable screen well past this bound and still finalizes; a turn whose PTY is
-// still producing output keeps holding past 30s (up to ANTIGRAVITY_HOLD_HARD_CAP_MS). Scoped
-// (at the call site) to antigravity-cli holdForTranscript blocks, so claude-cli/codex-cli
-// completion timing is untouched.
-export const ANTIGRAVITY_HOLD_QUIET_DWELL_MS = 3000;
-// (ANTIGRAVITY-30S-CAP-PREMATURE) Absolute upper bound on how long an antigravity
-// `holdForTranscript` block may be held once the 30s cap is reached but the PTY is still
-// active. The quiet-dwell gate above keeps holding while the PTY keeps emitting output, so a
-// truly runaway turn (PTY never falls quiet) must still eventually release rather than wedge
-// the session in generating forever — strictly worse than the original premature-emit bug.
-// Once a pending completion has been held this long we force-emit regardless of PTY activity.
-// Sized generously (5 min) so realistic long antigravity turns (multi-tool + slow reply)
-// finish and let the transcript land / the PTY fall quiet naturally, while still guaranteeing
-// eventual release. Mirrors BACKGROUND_TASK_HOLD_MAX_MS's escape-hatch rationale.
-export const ANTIGRAVITY_HOLD_HARD_CAP_MS = 5 * 60_000;
 // (FALSE-IDLE-BACKGROUND-CMD) Hard cap on how long a pending completion may be HELD
 // solely because the claude-cli transcript still shows an unresolved run_in_background
 // bash job (backgroundTaskActive). The hold is the correct behaviour while the job is