Address review comments: clarify decisions, add context indicator

1 files changed, 3 insertions, 1 deletions

diff --git a/research.md b/research.md
index 0496f29..b7d0897 100644
--- a/research.md
+++ b/research.md
@@ -111,7 +111,7 @@ for await (const message of query({
 
 **Critical for our workflow:**
 - **Research/Plan/Annotate phases**: Use `plan` mode or restrict `allowedTools` to read-only
-- **Implement phase**: Use `acceptEdits` or `bypassPermissions`
+- **Implement phase**: Use `acceptEdits` or `bypassPermissions` // REVIEW: make a user toggle
 
 ### System Prompts
 
@@ -307,6 +307,7 @@ const enforcePhaseHook: HookCallback = async (input, toolUseID, { signal }) => {
 - Con: More complex, may lose SDK internal state
 
 **Recommendation:** Use **Option A** (SDK persistence) with session ID in SQLite. We can still store messages for display/search, but rely on SDK for actual context.
+// REVIEW: option a
 
 ### Artifact Management
 
@@ -318,6 +319,7 @@ The blog workflow uses `research.md` and `plan.md` as persistent artifacts.
 3. **Both** — Files as source of truth, sync to SQLite for search
 
 **Recommendation:** Store as **files in the project directory** (e.g., `.claude-flow/research.md`, `.claude-flow/plan.md`). This matches the blog workflow where the human edits the plan.md directly.
+// REVIEW: recommendation is great
 
 ### IPC Architecture