merge: sync main (3.10.1) into curation-enhancement

[danhdoan]

Summary

• Problem: to sync version 3.10.1 and resolve conflicts

User-visible changes

N/A

Evidence

N/A

Checklist

• Tests added or updated and passing (npm test)
• Lint passes (npm run lint)
• Type check passes (npm run typecheck)
• Build succeeds (npm run build)
• Commits follow Conventional Commits format
• Documentation updated (if applicable)
• No breaking changes (or clearly documented above)
• Branch is up to date with main

Risks and mitigations

None

[github-actions]

Claude finished @danhdoan's task in 4m 22s —— View job

---

PR Review — sync main (3.10.1) into curation-enhancement

• Gather PR context and changed files list
• Review core infrastructure changes (daemon, executors, task router)
• Review new files (post-work-registry, propagate-summaries, status-row-classifier)
• Review transport/handler changes
• Review test coverage
• Post inline comments for specific issues
• Post overall summary with score

---

Overall Score: 4 / 5

This is a well-executed sync that brings substantial, production-quality features into the branch. The implementation quality is high across the board.

---

What's new (summary of additions)

Area	Change
PostWorkRegistry	Per-project serialized fire-and-forget queue with bounded shutdown drain. Cleanly solves the task:completed-before-Phase-4 ordering problem.
reviewDisabled snapshot	Daemon stamps the flag once at task-create, propagates via AsyncLocalStorage and TaskExecute, so daemon (CurateLogHandler) and agent (curate-tool, dream executor) observe a single consistent value even if the user toggles mid-run.
brv review command	Clean oclif command to toggle/query the HITL review log (--enable/--disable). Wired through ReviewHandler which got GET_DISABLED and SET_DISABLED transport events.
status-row-classifier	Extracts isomorphic-git statusMatrix tuple classification into a single shared module, eliminating six call sites that were deriving their own projections. Well-documented with the encoding table.
git-error-messages	Unified working-tree-overwrite error messages across pull/merge/checkout.
propagateSummariesUnderLock	Shared Phase 4 block for FolderPackExecutor — acquires the dream lock so curate's folder-pack path doesn't race with a concurrent dream on _index.md.
Deferred stale-summary propagation	CurateExecutor now enqueues changed paths into the dream-state queue instead of calling propagateStaleness inline. DreamExecutor drains the queue and merges with its own snapshot diff (A∪B) before a single propagateStaleness walk.

---

Strengths

• Fail-open everywhere: snapshot failures, Phase 4 errors, lock-acquire failures, session persist failures — all caught and swallowed with appropriate logging. No critical path is gated on non-critical work.
• Shutdown drains work: PostWorkRegistry.drain(30_000) in agent-process shutdown prevents SIGTERM truncating _index.md mid-write.
• Clear invariant comments: The "A∪B merge before propagateStaleness" invariant in DreamExecutor, the ALS propagation comment in curate-tool-task-context.ts, and the reviewEntriesWritten double-write guard are all well-commented.
• Test coverage: New files all have corresponding unit tests (post-work-registry.test.ts, status-row-classifier.test.ts, review-handler.test.ts, review-toggle.test.ts). Integration tests for isomorphic-git-service and status-tuple-reachability are thorough.
• Outside-In design followed: Consumer (agent-process.ts) drives the interface of PostWorkRegistry and executors; no premature abstractions.

---

Issues raised (inline comments)

1. BrvConfig.withReviewDisabled — Explicit field enumeration instead of {...this, reviewDisabled} spread; will silently drop any future new fields. (brv-config.ts:261)

2. agent-process.ts folderPath! — Non-null assertion violates CLAUDE.md convention; should narrow with a guard and explicit TaskError. (agent-process.ts:576)

3. propagateSummariesUnderLock — DreamLockService instantiated internally, making the function hard to test in isolation; prefer optional injection with an internal default. (propagate-summaries.ts:40)

4. handleSetDisabled — Returns the request payload instead of the persisted value; minor divergence risk if the store normalises the input. (review-handler.ts:278)

None of these are blockers. Issues 1 and 2 are straightforward fixes; 3 and 4 are quality-of-life suggestions.

[ncnthien]

look very good, so nice man