Rongsong Shen 48b4dba700 docs(raft-apply-decoupling): reconcile design.md deviations, retroactive boundary tag ... Closes the two non-blocking follow-ups from the 2026-07-07 validate-impl audit: - design.md had 3 sections describing the original plan rather than what landed, each already self-disclosed in tasks.md's Implementation Notes but never reconciled back: repl.c's planned repl_submit_majority_commit() was never built (task 3.2 calls commit_submit_async() directly instead); the apply pump is wired via commit_resolve_pending() in commit.c, not ha.c's on_commit_advanced; fact hooks fire one generic HOOK_DETAIL_JOB_UPDATE, not per-type hooks (verified safe -- sched.c's subscribers already consume the generic form). - task 5.3 touched ha.c (two promotion/fence call sites) without a formal _Boundary:_ exception the way task 1.4 got one for its own out-of-file touch -- added retroactively, no behavior change.		2026-07-07 08:48:57 +00:00
..
settings	finalize configuration replication	2026-06-09 16:40:13 +08:00
specs	docs(raft-apply-decoupling): reconcile design.md deviations, retroactive boundary tag	2026-07-07 08:48:57 +00:00
steering	docs: mark raft-apply-decoupling done, fix raft-drive-async header checkboxes	2026-07-07 08:43:03 +00:00