luna/oh-my-opencode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(known-issues): document delegate-task PR #3825 revert deferral

Browse Source 
PR #3825 added a shared bootstrap context to capture delegated
child-session retry payloads before the first prompt dispatch, so
empty-history failures could still retry through the fallback chain.
The PR's own regression test failed on clean root bun test after merge
(6828 pass / 1 fail). PR #4044 reverted the merge to keep dev green.

Ship v4.2.0 with the bug documented and a workaround so users have an
explicit story for the unfixed delegated child-session early-failure
path. Reland targets v4.2.1 once the regression test is stabilized.

Closes BLOCKER-4 (Path B - documentation, reland deferred to v4.2.1)
This commit is contained in:
YeonGyu-Kim
2026-05-16 01:36:21 +09:00
parent c096a596eb
commit f8d6f2a2ec
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/known-issues.md
+5 -5
View File
@@ -2,7 +2,7 @@
Tracks bugs that are present in the current release but have been intentionally deferred. Each entry should explain the symptom, the history, any workaround, and the planned resolution. Tracks bugs that are present in the current release but have been intentionally deferred. Each entry should explain the symptom, the history, any workaround, and the planned resolution.
## v4.2.0 - Delegate-task early-failure-fallback (BLOCKER-4, deferred from PR #3825) ## v4.2.0 - Delegated child-session early-failure fallback (PR #3825 deferred)
### Symptom ### Symptom
@@ -12,9 +12,9 @@ This affects subagents launched via the delegate-task tool (background or sync)
### History ### History
PR #3825 (`tw-yshuang/fix/delegated-child-session-early-failure-fallback`, commit `fac90d69f`, author `tw-yshuang`, merged on 2026-05-15) introduced a shared bootstrap context (`src/shared/delegated-child-session-bootstrap.ts`) to capture the retry payload before the first prompt dispatch, so empty-history failures could still retry with the fallback chain. PR #3825 (`tw-yshuang/fix/delegated-child-session-early-failure-fallback`, merged as commit `fac90d69f` on 2026-05-07) introduced a shared bootstrap context (`src/shared/delegated-child-session-bootstrap.ts`) to capture the retry payload before the first prompt dispatch, so empty-history failures could still retry with the fallback chain.
After the merge landed on `dev`, the PR's own regression test (`delegated child-session empty-history fallback retries with captured bootstrap prompt` in `src/hooks/runtime-fallback/index.test.ts`) failed on a clean root `bun test --timeout 30000` run (6828 pass / 1 fail). PR #4044 (`code-yeongyu/revert/3825-delegated-bootstrap`, commit `3c7d1299a`, merged on 2026-05-15) reverted the merge to keep `dev` green (6823 pass / 0 fail / 6 skip across 709 files). After the merge landed on `dev`, the PR's own regression test (`delegated child-session empty-history fallback retries with captured bootstrap prompt` in `src/hooks/runtime-fallback/index.test.ts`) failed on a clean root `bun test --timeout 30000` run (6828 pass / 1 fail). PR #4044 (`code-yeongyu/revert/3825-delegated-bootstrap`, merged on 2026-05-15) reverted the merge to keep `dev` green (6823 pass / 0 fail / 6 skip across 709 files).
The original failure-mode the PR targets remains in v4.2.0. The original failure-mode the PR targets remains in v4.2.0.
@@ -24,6 +24,6 @@ The original failure-mode the PR targets remains in v4.2.0.
- Configure fallback models conservatively in `categories[].fallback_models` and accept that the very first failure may not auto-retry. - Configure fallback models conservatively in `categories[].fallback_models` and accept that the very first failure may not auto-retry.
- The existing runtime-fallback persisted-history retry path still works after the subagent produces any history. - The existing runtime-fallback persisted-history retry path still works after the subagent produces any history.
### Tracking ### Planned Resolution
Issue #4059 tracks the reland with stabilized regression coverage. The reland is deferred to a follow-up release and should account for current schema-shape changes plus prompt-async-gate semantics. Reland will target v4.2.1 once the regression test is stabilized against the post-#4032 schema-compatible synthetic tool result shape and the prompt-async-gate's dispatch timeout + post-dispatch hold semantics. A follow-up issue will be filed to track this work.