gsxdsm
|
bb17baaacf
|
FN-8768: recover planning handoffs after dependency reseeds
Prevent dependency reseeds from leaving completed planning work without a dispatchable continuation.
- Serialize dependency invalidation with workflow claims and retire only pending continuations.
- Persist dispatch-deduplication state and recover legacy reseeded planning handoffs safely.
- Add PostgreSQL migration, integration coverage, architecture guidance, and a patch changeset.
Files changed:
.changeset/fn-8768-planning-reseed.md | 7 ++
docs/architecture.md | 10 +-
.../core/src/__test-utils__/pg-test-harness.ts | 8 ++
.../__tests__/postgres/backend-resolver.test.ts | 5 +
.../src/__tests__/postgres/schema-applier.test.ts | 17 ++-
.../postgres/task-dependency-mutation.pg.test.ts | 42 ++++++-
.../__tests__/task-update-lanes-resolved.test.ts | 20 +++-
packages/core/src/postgres/advisory-locks.ts | 122 +++++++++++++++++++++
packages/core/src/postgres/backend-resolver.ts | 13 ++-
packages/core/src/postgres/data-layer.ts | 4 +
packages/core/src/postgres/embedded-lifecycle.ts | 6 +
.../migrations/0043_fn8768_dispatch_dedupe.sql | 17 +++
packages/core/src/postgres/schema-applier.ts | 13 ++-
packages/core/src/postgres/schema/project.ts | 15 +++
packages/core/src/store.ts | 56 +++++++++-
packages/core/src/task-store/audit-ops.ts | 49 +++++++++
.../core/src/task-store/branch-and-pr-entities.ts | 30 +++++
packages/core/src/task-store/project-store-ops.ts | 55 ++++++++--
packages/core/src/task-store/task-update.ts | 30 ++++-
packages/core/src/task-store/update-task-deps.ts | 30 ++++-
packages/engine/src/__tests__/triage.test.ts | 66 ++++++++++-
packages/engine/src/execution/hold-release.ts | 45 ++++++++
packages/engine/src/scheduler.ts | 3 +-
packages/engine/src/triage.ts | 87 ++++++++++++++-
24 files changed, 713 insertions(+), 37 deletions(-)
Fusion-Task-Id: FN-8768
Fusion-Task-Lineage: 539ef649-5a13-4eaa-a695-bc68370fed22
Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
|
2026-08-03 19:31:03 -07:00 |
|
gsxdsm
|
cb57093d03
|
refactor: domain folder layout (types, API, core, engine) (#2398)
## Summary
Wave 17 organizes Fusion into **domain folders** (stacks on #2397).
### Layout
- **core/types/** — board, task, agents, settings, merge, workflow,
mesh, …
- **core/src/** — agents, ai, async-stores, workflows, tasks, config,
db, …
- **dashboard/app/api/** — client, tasks, agents, git, missions,
planning, …
- **engine/src/** — agents, auth, execution, merge, missions, overseer,
worktree, …
Root keepers retained for large entrypoints (`store.ts`, `executor.ts`,
`merger.ts`, …).
Public barrels (`@fusion/core`, `@fusion/engine`, `app/api.ts` → legacy)
stay stable.
## Test plan
- [x] `@fusion/core` typecheck
- [x] `@fusion/engine` typecheck (pre-existing playwright-core noise
only)
- [ ] CI merge gate
**Stack:** #2394 → #2397 → **this PR**
|
2026-08-03 00:20:53 -07:00 |
|