Problem
The suggest-flow gate behavior is correctly implemented and intentionally differs between Core (gate off by default) and Alliance (gate on by default, escapable via PINECONE_DISABLE_SUGGEST_FLOW=true). This is not a code defect.
There is a minor inconsistency within ALLIANCE_INSTRUCTIONS_APPENDIX in src/constants.ts:
- Line 71 documents the escape hatch: "...mandatory gate unless
PINECONE_DISABLE_SUGGEST_FLOW=true."
- Line 74 (Alliance usage step 4) says only "mandatory flow gate" with no escape clause.
An LLM reading only step 4 may infer the gate is unconditional, contradicting line 71 and docs/TOOLS.md.
Acceptance Criteria
Implementation Notes
References
src/constants.ts — ALLIANCE_INSTRUCTIONS_APPENDIX lines 71 and 74
src/core/config.ts — Core disableSuggestFlow default true
src/alliance/config.ts — Alliance disableSuggestFlow default false
docs/TOOLS.md — suggest-flow gate documentation
Problem
The suggest-flow gate behavior is correctly implemented and intentionally differs between Core (gate off by default) and Alliance (gate on by default, escapable via
PINECONE_DISABLE_SUGGEST_FLOW=true). This is not a code defect.There is a minor inconsistency within
ALLIANCE_INSTRUCTIONS_APPENDIXinsrc/constants.ts:PINECONE_DISABLE_SUGGEST_FLOW=true."An LLM reading only step 4 may infer the gate is unconditional, contradicting line 71 and
docs/TOOLS.md.Acceptance Criteria
unless PINECONE_DISABLE_SUGGEST_FLOW=trueescape clause, consistent with line 71 anddocs/TOOLS.mddisableSuggestFlowdefaults remain Coretrue, Alliancefalse)src/constants.test.tsif the appendix structure changes in issue De-duplicate Alliance usage section numbering in MCP instructions #194 — coordinate so both issues land cleanlyImplementation Notes
References
src/constants.ts—ALLIANCE_INSTRUCTIONS_APPENDIXlines 71 and 74src/core/config.ts— CoredisableSuggestFlowdefaulttruesrc/alliance/config.ts— AlliancedisableSuggestFlowdefaultfalsedocs/TOOLS.md— suggest-flow gate documentation