advise-session — a conversation with every harness, not a one-shot

Purpose

/advise asks each harness one question from a cold start: no memory, no repo. This opens a real session per harness instead. Each one can read the project and remember the last turn, so you can drill in — "why?", "what about the error path?", "you said X, show me where" — instead of re-pasting context.

You get back one researchkit session id. Hold that; it maps to the five per-vendor session ids so you never touch them.

When to use / when NOT to use

Use when the question has follow-ups, or when the answer depends on this codebase. NOT for: a single self-contained question (/advise is cheaper), one decisive verdict (/council), or web research (/explore).

Workflow