Goal
Make the existing implementation simpler through bounded, independently reviewable PRs. This tracks the remaining September 2026 architecture proposals, concretized against main commit 96a8a60ab5df71447b30db1826d4da2d6677c42b. Each child specifies a chosen implementation, deletion target, behavior boundaries and validation. It is a work sequence, not permission for a broad rewrite.
Already complete
These are completed baselines and must not be implemented again. Existing #380 is reused for source preservation. #790 remains the separate BIGQUERY typed-result contract; #738 and #538 are completed background work, not reopened tasks.
Independently startable work
Work with prerequisites
Sequence and implementation boundaries
- Export-writer inputs + explicit query-cache publication → query rendering overrides → explicit operation output. Progress stop/join also precedes explicit operation output.
- Fixed session construction identity → candidate validation and adoption.
- Direct pending transition + completed heartbeat investigation → stable logical transaction lifetime → automatic-DML queue ownership.
- Source-envelope changes land before parser-mapping cleanup. Result-body migration lands before the broad explicit-output signature migration. Both orders are recorded as blocked-by links so implementations do not overlap in the shared files; these are sequencing prerequisites, not semantic contract dependencies.
- Use separate worktrees per PR. Parallelize independent preparation; serialize heavy gates and integrate changes against refreshed main. Keep each issue's old path removal in the same PR as its replacement.
The heartbeat item is an unreproduced scheduling hypothesis with a deterministic investigation plan. It is not a confirmed bug or a reason to rewrite locking. The query-cache item identifies a source-backed behavior discrepancy and requires a red/green regression before its fix. Other items are structural refactors except the explicitly documented SOURCE/batch echo and pre-output progress improvements.
Completion criteria
No package extraction campaign, single-implementation interfaces, provider-neutral result framework, dependency upgrades, release or external-repository issue creation is included.
Goal
Make the existing implementation simpler through bounded, independently reviewable PRs. This tracks the remaining September 2026 architecture proposals, concretized against main commit
96a8a60ab5df71447b30db1826d4da2d6677c42b. Each child specifies a chosen implementation, deletion target, behavior boundaries and validation. It is a work sequence, not permission for a broad rewrite.Already complete
These are completed baselines and must not be implemented again. Existing #380 is reused for source preservation. #790 remains the separate BIGQUERY typed-result contract; #738 and #538 are completed background work, not reopened tasks.
Independently startable work
Work with prerequisites
Sequence and implementation boundaries
The heartbeat item is an unreproduced scheduling hypothesis with a deterministic investigation plan. It is not a confirmed bug or a reason to rewrite locking. The query-cache item identifies a source-backed behavior discrepancy and requires a red/green regression before its fix. Other items are structural refactors except the explicitly documented SOURCE/batch echo and pre-output progress improvements.
Completion criteria
No package extraction campaign, single-implementation interfaces, provider-neutral result framework, dependency upgrades, release or external-repository issue creation is included.