Skip to content

refactor(workflows): compaction-resilient recovery and risk-proportional validation (#4560) [DRAFT] - #4562

Draft
Yeachan-Heo wants to merge 6 commits into
devfrom
refactor/issue-4560-workflow-efficiency
Draft

refactor(workflows): compaction-resilient recovery and risk-proportional validation (#4560) [DRAFT]#4562
Yeachan-Heo wants to merge 6 commits into
devfrom
refactor/issue-4560-workflow-efficiency

Conversation

@Yeachan-Heo

@Yeachan-Heo Yeachan-Heo commented Aug 14, 2026

Copy link
Copy Markdown
Owner

Summary

Closes #4560 with the complete workflow-efficiency contract reconstructed onto current dev:

  1. Pre-consensus Ralplan intent reconciliation — a persisted intent stage resolves material objective/scope/non-goal/acceptance/verification questions before Architect/Critic consensus. Post-consensus intent verification is delta-only, and the legacy planner → architect edge remains for in-flight pre-upgrade runs.
  2. Compaction-resilient workflow recovery — active Ralplan and Ultragoal runs reload a bounded structured contract from canonical durable state. Ralplan uses durable run state, realpath-confined artifacts, mandatory matching SHA-256 receipts, strict malformed-state failure, active review/revision/reconciliation actions, and terminal planning_stuck recovery. Ultragoal restores goal progress, blockers, joined cohort generation/hash, and exact next actions. Zero-progress escalation increments once per compaction attempt, not per snapshot read.
  3. Runtime-authoritative risk-proportional validation — low-risk single-goal boundaries may omit redundant cleaner/architect work only through an exact runtime-validated lane-selection proof. QA, targeted verification, receipts, provenance, join-before-repair, recursion ceilings, and frozen-source evidence remain mandatory. Workflow enforcement, auth/security, migrations, native, SDK/public contracts, agent-wire, computer/shared registries, multi-goal, incomplete, and untrusted changes remain full-cohort high risk.
  4. Usable frozen-source evidencegjc ultragoal quality-gate source-hash --json exposes the same authoritative integration-base/merge-base/path/diff/untracked-content digest the checkpoint validator enforces. Untracked symlinks are hashed by link identity without following external targets.

Design direction credit: @HaD0Yun.

Safety invariants preserved

  • Runtime-computed sourceHash binding; model-authored equal strings cannot prove unchanged evidence.
  • QA is never omittable.
  • Cohort lanes that apply retain frozen-source binding and join-before-repair.
  • Review-blocker recursion caps and terminal-critic ceilings are unchanged.
  • Malformed, stale, tampered, paused, terminal, and unknown recovery state fails closed to inert/generic behavior.
  • No compatibility shim or second durable workflow store was added.

Verification

Frozen reconstruction:

  • Base: d332b7890ed95ff71d1a80e00bd4d31809558e69
  • Head: b488e239bb7b23f66d6e8e2d183e80fd8aebad95
  • Canonical base-to-head diff SHA-256: f6e8da7a60c4dc5e85b45c6f490cef1056e6ad8ae2e675404082e11ae46ea6aa
  • Runtime source-basis hash: sha256:21ce0fde67443802b30e2ab17c6e2daf4f589a6d39932b1c9b5a5c5a33f842d4

Executed evidence:

  • Final workflow + compaction matrix: 534 pass, 19 skip, 0 fail across 28 files (artifacts/pr4562-final-tests.xml).
  • Exact affected CI shard reproduced under representative CI_DEV_CHANGED_PATHS + GITHUB_WORKSPACE: 9 pass, 0 fail; outer-workspace paths are ignored for an independent nested Git root while canonical workspace unknown-status evidence remains fail-closed.
  • Authoritative runtime shard reproduced under representative GitHub CI environment after isolating its intentional synthetic CI fallback fixtures: 181 pass, 0 fail; related fixture suites 35 pass, scope suites 20 pass.
  • Focused final workflow matrix: 371 pass, 0 fail across 11 files.
  • Full compaction regressions: 161 pass, 19 skip, 0 fail.
  • bun --cwd=packages/coding-agent run check:types — passed.
  • Generated workflow manifest sync — passed.
  • bun scripts/check-visible-definitions.ts — passed.
  • bun scripts/rebrand-inventory.ts --strict — passed.
  • bun test packages/coding-agent/test/default-gjc-definitions.test.ts29 pass, 0 fail.
  • AI slop cleaner: PASS, zero blocking findings; fail-safe fallbacks are bounded and regression-tested.
  • Independent generation-three architecture review: CLEAR / APPROVE, no blockers or WATCH items.
  • Independent generation-three executor QA/red-team: PASSED, no blockers.

Known repository-wide external defect: bun run check:ts reaches the pre-existing scripts/telegram-daemon-generation-guard.test.ts fixture lookup failure for packages/coding-agent/test/notifications-topic-registry.test.ts; the standalone guard passes from repository root. This PR does not suppress or work around it.

Comparative / forced-compaction evidence

Deterministic regression fixtures cover low-risk lane reduction versus unchanged full-cohort high-risk paths, forced compaction during Ralplan review, Ultragoal execution, parallel review/executor work, and blocker-fix re-review. They assert durable contract/action recovery and fail-closed source/risk selection; they do not claim identical model outputs or measured live-provider latency.

Review state

The implementation cohort is clean at the exact local head. The PR remains Draft until a non-author repository reviewer approves this exact pushed head; the verdict line will be switched to merge-approved only after that GitHub review exists.

gajae.pr-review-verdict.v1 needs-human sha256:f6e8da7a60c4dc5e85b45c6f490cef1056e6ad8ae2e675404082e11ae46ea6aa reviewer:human reviewer-id:HaD0Yun evidence:Independent local cohort CLEAR/PASSED; exact-head GitHub approval requested before owner readiness and merge

@Yeachan-Heo
Yeachan-Heo force-pushed the refactor/issue-4560-workflow-efficiency branch from d85f2b5 to 5ebd709 Compare August 14, 2026 16:31
@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Exact-head CI triage (fix-forward, signed):

  • Root cause of the two red checks at event head d85f2b5a90c60adbeca226e9d13f987a29853fa2 (base 21d0a44209) was publication/order, not workflow implementation:
    1. PR contract bootstrap — the Draft body carried zero verdict lines (that record is required even while Draft).
    2. Affected path validation / plan — the PR head predated the current dev base; the branch had been rebased locally but the push was stale, so the exact event head did not contain immutable base 21d0a44209 and the evidence producer could not download the absent plan artifact.
  • gjc-state-gates (static/runtime/integrity/read) were green at that head.
  • Fix-forward applied: verified the branch contains exactly current-dev ancestry (21d0a44209) plus the single implementation commit; force-with-lease pushed, so this PR's exact head is now 5ebd709530929881fde990440b6271172d43d168; exactly one honest needs-human verdict line was added with the recomputed current base→head digest (sha256:e0906b0c7bbaeb536196705f37cc0631c4214294f771c3c61950c8e4e186c71d).
  • Revalidated on the new head before pushing: focused recovery/policy/continuation tests (19 pass), coding-agent typecheck clean, check-visible-definitions pass, default-gjc-definitions (29 pass), ultragoal runtime/review/critic-gate + state-aware compaction regressions (221 pass), biome clean on touched files.
  • Fresh CI is running on the new exact head; this Draft remains owner-controlled — not ready-for-review, no merge.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Terminal exact-head evidence for this Draft (signed):

Head 672745071871b3ea1a82ba7a06dd59fba67cc44c (base 21d0a44209805e061e8476551d2d317ed26ffe73), Dev CI run 31821932194:

  • Affected path validation / plan — exact-head ancestry verified
  • Affected path validation / check:@gajae-code/coding-agent, ts-build, cli-smoke, native-build
  • ✅ All three new suites: workflow-recovery-projection, ultragoal-validation-lanes, agent-session-workflow-recovery-continuation
  • ✅ Ultragoal runtime, session-manager resident-cache, notifications-live-stream, docs-index-lazy regressions
  • Affected path validation / evidence producer + Affected path validation + Virtual integration validation
  • gjc-state-gates (static / runtime / integrity / read)
  • PR contract bootstrapintentional: the gate rejects the honest needs-human verdict line ("Verdict needs-human intentionally blocks merge"). This is the merge-blocker working as designed; this Draft must not merge, so the check is expected to stay red until an independent exact-head review records merge-approved (only possible after the owner marks it ready).

The earlier event-head failures (d85f2b5a: missing verdict line, stale push) and the mid-flight cancellation were triaged and fixed forward earlier in this thread; two adversarial self-review fixes landed as 6727450718 (dead policy input removed; ralplan run selection by recency) and revalidated locally before push (37 focused/regression tests, typecheck, biome).

This Draft remains owner-controlled: not ready-for-review, not merged, no release/tag/publish. Next step is independent exact-head review and an owner readiness decision.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Draft hold maintained — owner-controlled reconcile receipt (signed):

Submitted state (recorded before any action, unchanged): head 672745071871b3ea1a82ba7a06dd59fba67cc44c, base dev @ 21d0a44209805e061e8476551d2d317ed26ffe73, DRAFT/OPEN. No push, no force-push, no ready-mark performed by this lane.

Owner-readiness check (pre-mutation): no owner-ready evidence exists. Latest signed evidence on this PR (2026-08-14T17:26:46Z) states the Draft "remains owner-controlled: not ready-for-review, not merged" with next step "an owner readiness decision"; the PR contract bootstrap check is intentionally red on the honest needs-human verdict line. No merge-approved verdict, no ready transition, no owner direction since. Hold therefore continues.

Delta reconciliation against current dev 64c15281691280be7854dac04baeb05188328ef4:

  • PR touches 9 files; dev moved 27 files since base 21d0a44209. Overlap: packages/coding-agent/CHANGELOG.md and packages/coding-agent/src/session/agent-session.ts only.
  • agent-session.ts: dev hunks (~1929, 4312–5320: admission gating from fix(sdk): run initial attachment replay off the reconcile tail (#4527) #4542-adjacent fixes) vs PR hunks (~177–509, 5817, 11273–11507: compaction recovery projection) — no textual collision; no changed workflow contract conflicts detected.
  • Trial merge of the submitted head into dedicated worktree branch owner/pr-4562-current-dev-0215 (local commit cef7aae9b9e1ff3699674e117d65c60e9878870a, never pushed): clean ort merge, zero conflicts.

Bounded validation on the merged tree: 19 pass (3 new PR suites: workflow-recovery-projection, ultragoal-validation-lanes, agent-session-workflow-recovery-continuation), 258 pass/7 skip (ultragoal-runtime + compaction suites + sdk-kind-aware-reconciliation + notifications-inbound-acceptance), 55 pass (dev-side admission suites: contended-terminal-capture, midrun-maintenance, pre-admission-artifact-spill, sdk-steer-reconciliation, notifications-turn-ordering) — 0 fail; coding-agent typecheck clean (tsc -p tsconfig.json --noEmit); biome clean on all 7 PR-touched source/test files.

Hold decision: DRAFT HOLD continues. This PR stays draft and owner-controlled. A rebase onto current dev is validated as clean but intentionally not pushed — exact-head discipline means a push would stale all existing CI/verdict evidence at 6727450. Blocker: owner readiness decision (mark ready → independent exact-head review → merge-approved) is the only remaining gate.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Stale-evidence notice + recomputed draft hold (signed):

Base movement: current dev advanced 64c15281691280be7854dac04baeb05188328ef496e718a2b0f2a46cad4876bf922886966c6fd0e3 via merged #4540 (fix(session): fence SDK queued prompt ingress, fence-deferred continuations, pre-fence recovery in scoped idle drains). All trial-merge, diff-digest, review, and CI claims previously bound to 64c15281 — including the clean ort trial merge (cef7aae9) and its validation receipts posted at #issuecomment-5300063584 — are now stale for terminal merge. This Draft remains unpushed and owner-controlled; the submitted head is unchanged (672745071871b3ea1a82ba7a06dd59fba67cc44c, base dev @ 21d0a44209).

#4540 overlap inspection: the 64c15281..96e718a2 delta touches 10 files; intersected with PR #4562's 9 touched files the overlap is again packages/coding-agent/CHANGELOG.md + packages/coding-agent/src/session/agent-session.ts. #4540 lands ~40 hunks in agent-session.ts concentrated in the 5400–6300 fence/admission region and the 11000+ region; the PR's hunk at @@ -5817 (compaction recovery projection) sits directly inside #4540's @@ -5815/@@ -5851 territory, so the prior clean-merge result was at genuine textual risk, not merely procedurally stale.

Recomputed onto exact 96e718a2: trial merge of the submitted head into the dedicated worktree branch (local commit 56d8b2ec2c2e9a8012555d56e18edd3d92995ced, never pushed) is again a clean ort merge, zero conflicts.

Bounded validation on the recomputed tree (all fresh): 19 pass (3 new PR suites: workflow-recovery-projection, ultragoal-validation-lanes, agent-session-workflow-recovery-continuation), 258 pass/7 skip (ultragoal-runtime + compaction + sdk-kind-aware-reconciliation + notifications-inbound-acceptance), 57 pass/1 skip (#4540-side: agent-session-auto-compaction-continue, before-agent-start-attribution, manual-retry, sdk/host/session-runtime), 55 pass (admission/reconciliation suites: contended-terminal-capture, midrun-maintenance, pre-admission-artifact-spill, sdk-steer-reconciliation, notifications-turn-ordering) — 0 fail; coding-agent typecheck clean (tsc -p tsconfig.json --noEmit + biome 2845 files OK); biome clean on all 7 PR-touched files.

Hold decision: DRAFT HOLD continues at unchanged submitted head. No push, no ready-mark, no merge, no release mutation. Blocker remains the owner readiness decision; per exact-head discipline, any future rebase push would stale CI/verdict evidence at 6727450 and require a fresh independent exact-head review recording merge-approved.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Owner census — exact live state (2026-08-15):

  • PR refactor(workflows): compaction-resilient recovery and risk-proportional validation (#4560) [DRAFT] #4562 is OPEN and DRAFT: refactor/issue-4560-workflow-efficiencydev.
  • Remote PR head is 672745071871b3ea1a82ba7a06dd59fba67cc44c (matches the supplied head).
  • GitHub's recorded base OID is 21d0a44209805e061e8476551d2d317ed26ffe73; freshly fetched live origin/dev is cd51365cc270e27dceccfc2c184fadc9c1ddbe18.
  • The PR head is 59 commits behind and 2 commits ahead of live dev; merge base remains 21d0a44209805e061e8476551d2d317ed26ffe73.
  • GitHub reports CONFLICTING / DIRTY.
  • Review decision is unset. Current CI includes a failing PR contract bootstrap; the stale run also contains cancelled jobs. The public-surface sync check shown on the PR passed.
  • The dedicated census worktree is clean and checked out at live dev (cd51365cc270e27dceccfc2c184fadc9c1ddbe18), not at the stale PR head.
  • Draft rationale remains valid only as a safety boundary while the compaction-recovery/risk-proportional refactor is audited and reconstructed against current dev; it is not merge-ready in its present state.

Disposition in progress: reconstruct the intended change onto current dev, audit overlap and safety invariants, fix-forward, validate, push the existing PR branch, then drive review/CI/merge and close #4560. No terminal hold has been declared.


[repo owner's gaebal-gajae (clawdbot) 🦞]

Yeachan Heo and others added 4 commits August 15, 2026 15:11
…validation (#4560)

Long ralplan -> ultragoal runs compacted mid-flight with only a thin
state projection (goal objective/status, phase, todos) plus a generic
continuation prompt, losing the precise accepted scope/progress/evidence
contract and inviting drift, duplicate review generations, and
zero-progress continuation loops. Boundary validation also applied the
full review cohort unconditionally, inflating token cost and failure
surface on low-risk single-goal work.

Add a structured workflow recovery projection derived from canonical
durable state (Ralplan final/index.jsonl and Ultragoal
goals.json/ledger.jsonl): bounded objective, accepted scope, non-goals,
acceptance criteria, unresolved decisions, current goal, measurable
progress, exact next action class, and digest. Compaction renders it
into the state-aware context and the post-compaction auto-continue for
active recognized workflows consumes it with scope-reload,
user-intent-supremacy, no-silent-scope-expansion, unchanged-basis
rerun-avoidance, and bounded zero-progress escalation rules. Malformed,
stale, or tampered state degrades safely to the previous behavior, and
paused/terminal/unknown workflows stay inert.

Add a deterministic Ultragoal validation-applicability policy computed
from durable facts (trusted change set, plan shape, open review
blockers, joined-cohort source hash). Low-risk single-goal boundaries
may omit redundant cleaner/architect ceremony and the duplicate
terminal-critic read only through a validationLaneSelection proof that
must exactly mirror the runtime-computed selection; QA, sourceHash
binding, receipts, provenance, and join-before-repair stay mandatory.
High-risk, multi-goal, computer/shared-registry, migration, and
public-contract paths keep the full heavyweight cohort, and an
unchanged immutable source/evidence basis permits reusing verified
boundary evidence instead of forcing a full rerun.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>
Lore-id: 4a5f19c2
Constraint: preserve executor and cleaner||architect||qa cohort parallelism (#3473/#3474)
Constraint: runtime-authoritative lane selection, never free-form model self-exemption
Constraint: compaction reloads the durable contract; scope expansion must be classified, never silently accepted
Rejected: model-declared lane skipping | prose cannot be validated fail-closed
Rejected: second durable workflow-state store | projection is read-only over existing canonical state
Confidence: high
Scope-risk: moderate
Reversibility: trivial
Tested: 19 focused tests across projection, policy, gate selection, and compaction continuation
Tested: regression suites for compaction, ultragoal runtime, review, critic gate, batch release (327 pass)
Not-tested: live multi-run dogfood latency deltas (documented as follow-up evidence)
… recency (#4560)

Adversarial exact-head self-review findings: priorVerifiedGeneration was
declared on the applicability input but never consumed (dead contract
surface), and the ralplan recovery run selection used a lexicographic
name sort, which is arbitrary for non-monotonic run ids — recovery must
project the run the session actually touched last, so select by newest
run-directory mtime.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>
Lore-id: 77c3e8b1
Constraint: no dead contract surface on the validation policy input
Confidence: high
Scope-risk: narrow
Reversibility: trivial
Tested: focused recovery/policy/continuation + state-aware compaction suites (37 pass); coding-agent typecheck + biome clean
The reconstructed workflow refactor still trusted unconstrained plan paths, counted snapshot reads as separate compactions, and allowed self-authored cohort hashes to satisfy unchanged-basis critic reuse. It also left material intent reconciliation until after expensive Ralplan consensus.

Confine and digest-check Ralplan artifacts, recover active consensus actions from durable state, bind cohort hashes to the captured source basis, classify workflow enforcement and credential surfaces as high risk, add a pre-consensus intent stage, and cover forced-compaction and blocker re-review paths.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>

Lore-id: 9e4b6c2a

Constraint: QA, sourceHash, receipts, provenance, join-before-repair, recursion caps, and critic ceilings remain mandatory

Constraint: workflow enforcement changes classify themselves as high risk

Rejected: self-declared unchanged source hashes | cannot prove evidence freshness

Rejected: post-consensus-only intent interview | spends review before resolving material scope

Confidence: high

Scope-risk: wide

Reversibility: migration-needed

Tested: 366 workflow tests plus 180 compaction tests; coding-agent typecheck; manifest/default/rebrand gates

Not-tested: live multi-model latency distribution
Generation-two review found that the authoritative cohort digest was required but unavailable through a supported command, making honest quality-gate construction impossible. Recovery also still accepted Ralplan rows that omitted their recorded digest.

Expose a read-only quality-gate source-hash command, require digest-bearing confined Ralplan rows, reject tampered mode/index state, hash untracked symlinks by link identity, preserve the legacy planner-to-architect edge, and make planning-stuck recovery terminal.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>

Lore-id: 3d8f7a11

Constraint: the leader must obtain sourceHash from the runtime on the frozen snapshot

Constraint: current Ralplan writer receipts require matching SHA-256 provenance

Rejected: diagnostic-only hash discovery | forces an edit/retry loop at the terminal gate

Confidence: high

Scope-risk: moderate

Reversibility: trivial

Tested: 147 focused workflow tests; coding-agent typecheck; live source-hash CLI invocation
@Yeachan-Heo
Yeachan-Heo requested a review from HaD0Yun August 15, 2026 15:42
@Yeachan-Heo
Yeachan-Heo force-pushed the refactor/issue-4560-workflow-efficiency branch from 6727450 to 59b3cd6 Compare August 15, 2026 15:42
@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

Owner-state update:

  • Published reconstructed exact head 59b3cd6acab91b437041587c7a73b2fdeadd169e onto refactor/issue-4560-workflow-efficiency with force-with-lease.
  • Exact current dev base is d332b7890ed95ff71d1a80e00bd4d31809558e69; canonical diff digest is a4989bc8958c11b31e1028aa51e2f147936117ca38b1c43fd4d5042cd6248bad.
  • Final local evidence: 532 pass / 19 skip / 0 fail across 28 workflow+compaction files; coding-agent typecheck and public-definition/rebrand gates pass; architect CLEAR; executor red-team PASSED.
  • Repository-wide check:ts still reaches the pre-existing cwd-relative missing-fixture failure in telegram-daemon-generation-guard.test.ts; the standalone guard passes 75/75 from the repo root.
  • Replacement CI is running. Exact-head GitHub review is requested from @HaD0Yun; the PR remains Draft and the verdict remains needs-human until that non-author approval exists. No owner-authorized hold has been declared.


[repo owner's gaebal-gajae (clawdbot) 🦞]

Affected-task CI exports repository-wide CI_DEV_CHANGED_PATHS into every test process. Standalone temporary git repositories inherited those unrelated unknown-status paths, so the authoritative source-hash command correctly failed closed even though their own change sets were complete.

Bind CI changed-path evidence only when the inspected repository is inside GITHUB_WORKSPACE, preserve known Git status over duplicate CI pathname-only rows, and cover both independent-repository isolation and canonical-workspace fail-closed participation.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>

Lore-id: 61af32d9

Constraint: unknown-status paths remain fail-closed in the authoritative workspace

Rejected: deleting CI_DEV_CHANGED_PATHS only in the test | leaves production nested-repository hashing environment-dependent

Confidence: high

Scope-risk: narrow

Reversibility: trivial

Tested: validation-lanes under representative CI_DEV_CHANGED_PATHS/GITHUB_WORKSPACE; change-set tests; ultragoal runtime/review; coding-agent typecheck
@Yeachan-Heo
Yeachan-Heo requested review from HaD0Yun and removed request for HaD0Yun August 15, 2026 16:03
The production workspace binding correctly ignored outer CI_DEV_CHANGED_PATHS for independent repositories, but several Ultragoal suites intentionally use that variable as synthetic change-set input for temporary repositories. GitHub's outer GITHUB_WORKSPACE made those fixtures indistinguishable from accidental environment leakage and caused the authoritative runtime shard to fail.

Clear and restore GITHUB_WORKSPACE only around the suites that explicitly simulate CI_DEV_CHANGED_PATHS fallback, leaving production unknown-status and canonical-workspace behavior unchanged.

Co-authored-by: DoYunHa <102889891+HaD0Yun@users.noreply.github.com>

Lore-id: 7b149ac0

Constraint: test isolation must not alter production fail-closed hashing

Rejected: weakening workspace equality in production | reintroduces the original nested-repository leak

Confidence: high

Scope-risk: narrow

Reversibility: trivial

Tested: ultragoal-runtime under representative GitHub CI env 181 pass; related synthetic CI suites 35 pass; scope suites 20 pass; coding-agent typecheck
@Yeachan-Heo
Yeachan-Heo requested review from HaD0Yun and removed request for HaD0Yun August 15, 2026 16:20
@Yeachan-Heo

Copy link
Copy Markdown
Owner Author

@HaD0Yun exact-head review is now the only merge gate.

Authoritative head/base: b488e239bb7b23f66d6e8e2d183e80fd8aebad95 / d332b7890ed95ff71d1a80e00bd4d31809558e69. Canonical diff digest: f6e8da7a60c4dc5e85b45c6f490cef1056e6ad8ae2e675404082e11ae46ea6aa. Authoritative CI run https://github.com/Yeachan-Heo/gajae-code/actions/runs/31895238136 is product-green: native build, package check/type build, all affected workflow tests, evidence producer/aggregate, state gates, and virtual integration passed. Only PR contract bootstrap is red because the single verdict is intentionally needs-human.

Please submit an APPROVED review on this exact head. After the review exists, the owner lane will switch the existing single verdict to merge-approved, mark ready, rerun bootstrap, and squash-merge immediately.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo
Yeachan-Heo requested a review from snowykr August 17, 2026 16:59
@Yeachan-Heo

Yeachan-Heo commented Aug 17, 2026

Copy link
Copy Markdown
Owner Author

Exact-head disposition — owner-controlled hold with third-party review gate (signed):

Exact live state (recomputed 2026-08-17):

  • Head b488e239bb7b23f66d6e8e2d183e80fd8aebad95 (remote branch ref matches exactly), base dev @ recorded d332b7890ed95ff71d1a80e00bd4d31809558e69. OPEN/DRAFT, 6 commits.
  • Canonical diff digest recomputed with the CI contract algorithm (git diff --binary --full-index --no-ext-diff BASE...HEAD → sha256): f6e8da7a60c4dc5e85b45c6f490cef1056e6ad8ae2e675404082e11ae46ea6aamatches the declared verdict digest exactly. 24 files, +2522/−119.
  • Exact-head CI (run 31895238136) is product-green: native-build, package check, ts-build, cli-smoke, evidence producer/aggregate, state gates, virtual integration, and all affected workflow suites. The single red PR contract bootstrap is the intentional needs-human verdict line (job log verified: error: Verdict needs-human intentionally blocks merge.), not a product failure.
  • Reviews: none exist (0). Mergeability: mergeable:true (UNSTABLE only due to the red bootstrap check). dev is not branch-protected.

Base movement & fresh trial merge (owner verification, this lane):

  • Live dev is now 8711c555da490ad36475f94368bcdd8d8f01048e — 76 commits past the recorded base (0.13.3/0.14.0 cuts landed). Prior trial-merge receipts bound to older dev tips are stale.
  • Trial merge of the exact head onto live dev resolves clean with ort → f3ee9e6ac7d3dacfb76b11eb2c50254e3af33ff6, diffstat identical (24 files, +2522/−119). Only 2 files overlap between the PR and dev's 76 commits: CHANGELOG.md (append-only) and agent-session.ts, where dev's sole change is adding the "omlx" provider to an unrelated provider list ~1100 lines away from this PR's recovery changes — no semantic conflict.
  • On the merged tree, this lane re-verified: check (biome+tsc) clean; 402 tests pass / 0 fail across all 15 affected suites (workflow-recovery-projection, agent-session-workflow-recovery-continuation, ultragoal-validation-lanes, ultragoal-runtime/change-set/review/critic-gate/dogfood/durable-completion-release, ralplan-runtime, ralplan-decision-artifacts, workflow-manifest-phase-sets, docs-index-lazy, notifications-live-stream, session-manager-resident-cache); G002, state-writer, visible-definitions, rebrand-inventory gates pass; default-gjc-definitions 29/29.

Blocker (owner-only, exact):
The PR contract posted by this lane — and enforced by dev-ci.yml — requires an APPROVED review from a non-author write+ collaborator at this exact head before the verdict line may be switched to merge-approved. The author (repo owner Yeachan-Heo) cannot self-approve (contract explicitly rejects it). HaD0Yun (write) has been the requested reviewer since 2026-08-15T16:20:27Z with the explicit ask posted at 2026-08-15T16:37:03Z; no review has arrived (2 days). This lane has now also requested maintainer snowykr (write) as an alternate reviewer so the gate is not single-threaded.

Why no fix-forward push: the exact head is green and merge-clean against live dev; any new push would invalidate the verified exact-head CI/digest/evidence chain without fixing anything. Rebase would be pure churn.

Terminal disposition: hold as owner-controlled DRAFT pending the exact-head APPROVED review from HaD0Yun or snowykr. On that review: switch the single verdict line to merge-approved (same digest — head unchanged), let PR contract bootstrap go green, then merge to dev or close per the reviewer's outcome. No merge, no close, no verdict change is performed before the review exists.


[repo owner's gaebal-gajae (clawdbot) 🦞]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant