同步homunculus观察记录与instinct文件

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.claude/homunculus/instincts/personal/batch-verification-after-all-fixes.md

@@ -0,0 +1,20 @@
+---
+id: batch-verification-after-all-fixes
+trigger: "when the user is reviewing and approving multiple related problems one by one"
+confidence: 0.9
+domain: "workflow"
+source: "explicit-user-correction"
+---
+
+# Verify Only After the Whole Batch Is Finished
+
+## Action
+
+When several related issues are being confirmed and fixed one by one, only edit code, tests, and specifications during the individual issue steps. Do not run Maven, compilation, unit tests, or other build verification after each small fix. After the user confirms that all issues in the batch have been handled, run the agreed verification suite once, followed by the final diff check.
+
+If a static read-only inspection is needed while editing, it may be used, but it must not start a build or test process.
+
+## Evidence
+
+- On 2026-08-12, the user explicitly corrected repeated per-fix Maven runs and required: "完成所有后再测试".
+- A Maven retry was stopped immediately after the correction.

.claude/homunculus/instincts/personal/resume-omg-attempt-lifecycle-review.md

@@ -0,0 +1,26 @@
+---
+id: resume-omg-attempt-lifecycle-review
+trigger: "when resuming the OMG payment review after 2026-08-12"
+confidence: 0.9
+domain: "project-status"
+source: "explicit-user-request"
+---
+
+# Resume OMG Payment Attempt Lifecycle Review
+
+## Action
+
+Resume from `specs/016-omg-payment/tasks.md` T066 before continuing T065 or lower-priority OMG fixes. Reassess the payment-attempt lifecycle because the current three-minute reuse rule can create multiple simultaneously payable OMG transactions.
+
+The known open items are:
+
+- T066 P0: remove the unsupported three-minute payment-attempt expiry assumption; persist real deferred-payment `ExpireDate`; only rotate after a conclusive gateway failure or real expiry; never reuse one `MerchantTradeNo` with a newly generated request unless OMG explicitly guarantees that contract.
+- T067 P1: make query throttling fair and do not consume the ddId slot when no query is sent.
+- T065: after the attempt lifecycle is settled, complete durable refund recovery for payments that succeed after order cancellation.
+
+Do not run Maven or tests while these issues are being handled one by one. Run one unified verification only after the user confirms the batch is complete.
+
+## Evidence
+
+- User requested on 2026-08-12: "记录起来我们明天再继续".
+- Static review found `reuse-fresh-minutes=3` is not an OMG payment lifetime; official documentation applies three minutes to QueryTradeInfo `TimeStamp` validity.

.claude/homunculus/instincts/personal/verify-confirmed-decisions-with-subagents.md

@@ -0,0 +1,31 @@
+---
+id: verify-confirmed-decisions-with-subagents
+trigger: "after implementing decisions that the user and Codex explicitly confirmed"
+confidence: 0.9
+domain: "workflow"
+source: "user-directive-2026-08-12"
+---
+
+# Verify Confirmed Decisions With Subagents
+
+## Action
+
+After implementing explicitly confirmed discussion decisions, assign subagents to check every confirmed item against the specification, code, tests, migrations, and user-facing behavior. Report each omission and resolve it before claiming completion.
+
+Do not ask the user to approve every verification item. Use the confirmed decisions as the review checklist.
+
+Use milestone-based batch reviews instead of fragmented "find one, fix one, review again" loops:
+
+1. **Design review before implementation**: give each subagent the same frozen, complete specification and a distinct review scope. Require each reviewer to finish its whole checklist and return all Critical/Important findings in one report, even after finding a blocker.
+2. **Implementation review after a complete milestone**: first compile and run the relevant tests, then freeze the workspace snapshot. Have subagents review the complete implementation and collect findings in one consolidated issue list. Batch-fix the list instead of interrupting implementation for every incoming finding.
+3. **Final confirmation before delivery**: after all fixes and verification pass, have each relevant subagent confirm its previously reported items and state whether the final snapshot has any remaining Critical/Important issues.
+
+For an ordinary localized fix, only the subagent that raised the issue performs a targeted confirmation. Repeat a full multi-subagent review only when a fix materially changes a payment/refund state machine, database uniqueness or transaction boundary, external financial side-effect ordering, order completion/cancellation/refund mutual exclusion, or when preparing final delivery.
+
+Subagents performing a review should be read-only and should not review a workspace that is still being edited. The main agent owns consolidation, implementation, and user communication.
+
+## Evidence
+
+- The user explicitly required this workflow for future confirmed discussions on 2026-08-12.
+- The current LINE Pay implementation must receive this item-by-item subagent verification after implementation.
+- After the LINE Pay retrospective, the user explicitly required future subagent reviews to use staged, complete reports rather than repeated one-finding-at-a-time loops on 2026-08-12.