artdag: note scheduler re-merged to architecture (fdd0c8f7)
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 43s

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-06-28 18:02:59 +00:00
parent 4d5bf47f4a
commit e1fe5ab552

View File

@@ -38,12 +38,12 @@ Base roadmap (Phases 16) COMPLETE + Phase 7 (maude rule-based optimization) C
## Integration / merge status (2026-06-28) ## Integration / merge status (2026-06-28)
**MERGED to architecture (Phase 7) at `b0d845bb`** — local `architecture` now carries **MERGED to architecture, fully up to date.** Phase 7 merged at `b0d845bb`; the miniKanren
`lib/maude` + artdag Phase 7, conformance green there (198/198 at merge time). The merge CLP(FD) scheduler re-merged at `fdd0c8f7` (architecture HEAD). Local `architecture` now
was clean/additive; `architecture` itself was NOT pushed (pushing it triggers a large dev carries `lib/maude` + the complete artdag engine, conformance green there (213/213). Both
reload — a deliberate separate call). **NOTE: re-merge needed**`loops/artdag` has since merges were clean/additive (only artdag-scoped files). `architecture` itself was NOT pushed
added `lib/artdag/schedule.sx` (miniKanren CLP(FD) scheduler, 213/213), not yet on to origin — pushing it triggers a large dev reload, a deliberate separate call left to a
architecture. maintainer.
(Historical, for the Phase 7 merge above:) `origin/architecture`'s `lib/artdag/` (Historical, for the Phase 7 merge above:) `origin/architecture`'s `lib/artdag/`
is stale — it predates the maude-bridge, so it is missing ALL of Phase 7 is stale — it predates the maude-bridge, so it is missing ALL of Phase 7