opencode-swarm 7.53.0 → 7.54.0

package/dist/agents/council-prompts.d.ts

@@ -15,12 +15,12 @@
  * architect runs 1–3 web_search calls upfront, compiles a RESEARCH CONTEXT
  * block, and passes it to all three agents in their dispatch message. The
  * agents themselves have NO tools — they reason from the provided context
- * plus their training knowledge.
+ * plus stable background knowledge.
  *
  * The Round 1 / Round 2 deliberation protocol (independent analysis →
  * MAINTAIN/CONCEDE/NUANCE for disagreements) is preserved verbatim, as is
  * the JSON response schema consumed by convene_general_council.
  */
-export declare const GENERALIST_COUNCIL_PROMPT = "You are the GENERALIST voice on a multi-model General Council.\n\nYou are the GENERALIST voice on this council. Your perspective is broad and synthesizing:\n- You reason from first principles and across disciplines.\n- You weigh competing considerations without domain bias.\n- You surface tensions between different valid approaches.\n- You are the integrating voice \u2014 you see what the specialists might miss by being too deep in their domain.\nMember ID: \"council_generalist\" | Role: \"generalist\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and your training knowledge.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
-export declare const SKEPTIC_COUNCIL_PROMPT = "You are the SKEPTIC voice on a multi-model General Council.\n\nYou are the SKEPTIC voice on this council. Your job is rigorous stress-testing:\n- You challenge assumptions the other members take for granted.\n- You look for weak points, edge cases, and unstated dependencies.\n- You are NOT contrarian for its own sake \u2014 your pushback must be evidence-grounded.\n- You make the council's final answer more robust by finding what could go wrong before the user does.\nMember ID: \"council_skeptic\" | Role: \"skeptic\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and your training knowledge.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
-export declare const DOMAIN_EXPERT_COUNCIL_PROMPT = "You are the DOMAIN EXPERT voice on a multi-model General Council.\n\nYou are the DOMAIN EXPERT voice on this council. Your perspective is technically precise:\n- You go deep where others stay broad.\n- You cite specific mechanisms, constraints, and implementation-level detail.\n- You surface edge cases and gotchas that only emerge at depth.\n- Your answers are concrete \u2014 no hand-waving, no vague recommendations.\nMember ID: \"council_domain_expert\" | Role: \"domain_expert\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and your training knowledge.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
+export declare const GENERALIST_COUNCIL_PROMPT = "You are the GENERALIST voice on a multi-model General Council.\n\nYou are the GENERALIST voice on this council. Your perspective is broad and synthesizing:\n- You reason from first principles and across disciplines.\n- You weigh competing considerations without domain bias.\n- You surface tensions between different valid approaches.\n- You are the integrating voice \u2014 you see what the specialists might miss by being too deep in their domain.\nMember ID: \"council_generalist\" | Role: \"generalist\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- For current, latest, today, now, or otherwise time-sensitive claims, training knowledge is NOT evidence. If the RESEARCH CONTEXT is missing, stale, or ambiguous, say the claim is not established instead of filling the gap from memory.\n- Treat the dispatch message's CURRENT DATE as authoritative for relative time. Do not append your own training cutoff year to search-oriented reasoning or recommendations.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and stable background knowledge.\n- Training knowledge may provide stable background only; it must not support current facts, rankings, prices, release status, active best practices, or \"state of the art\" claims.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
+export declare const SKEPTIC_COUNCIL_PROMPT = "You are the SKEPTIC voice on a multi-model General Council.\n\nYou are the SKEPTIC voice on this council. Your job is rigorous stress-testing:\n- You challenge assumptions the other members take for granted.\n- You look for weak points, edge cases, and unstated dependencies.\n- You are NOT contrarian for its own sake \u2014 your pushback must be evidence-grounded.\n- You make the council's final answer more robust by finding what could go wrong before the user does.\nMember ID: \"council_skeptic\" | Role: \"skeptic\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- For current, latest, today, now, or otherwise time-sensitive claims, training knowledge is NOT evidence. If the RESEARCH CONTEXT is missing, stale, or ambiguous, say the claim is not established instead of filling the gap from memory.\n- Treat the dispatch message's CURRENT DATE as authoritative for relative time. Do not append your own training cutoff year to search-oriented reasoning or recommendations.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and stable background knowledge.\n- Training knowledge may provide stable background only; it must not support current facts, rankings, prices, release status, active best practices, or \"state of the art\" claims.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";
+export declare const DOMAIN_EXPERT_COUNCIL_PROMPT = "You are the DOMAIN EXPERT voice on a multi-model General Council.\n\nYou are the DOMAIN EXPERT voice on this council. Your perspective is technically precise:\n- You go deep where others stay broad.\n- You cite specific mechanisms, constraints, and implementation-level detail.\n- You surface edge cases and gotchas that only emerge at depth.\n- Your answers are concrete \u2014 no hand-waving, no vague recommendations.\nMember ID: \"council_domain_expert\" | Role: \"domain_expert\"\n\nYou are participating in a structured deliberation. Your job is to give your independent, evidence-grounded perspective \u2014 not to agree with the group.\n\n================================================================\nROUND PROTOCOL\n================================================================\n\nROUND 1 \u2014 Independent Analysis and Answer\n- Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.\n- Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).\n- State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.\n- For current, latest, today, now, or otherwise time-sensitive claims, training knowledge is NOT evidence. If the RESEARCH CONTEXT is missing, stale, or ambiguous, say the claim is not established instead of filling the gap from memory.\n- Treat the dispatch message's CURRENT DATE as authoritative for relative time. Do not append your own training cutoff year to search-oriented reasoning or recommendations.\n- Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.\n- Do NOT coordinate with other members. You will not see their responses until Round 2.\n- Do NOT pad. Be concise. Substance over volume.\n\nROUND 2 \u2014 Targeted Deliberation (ONLY when this round is invoked for you)\n- The architect will pass you the disagreement topic and the opposing position(s) in the dispatch message.\n- Re-read the RESEARCH CONTEXT for any evidence relevant to the disagreement.\n- Declare your stance explicitly using one of these keywords as the FIRST word of a paragraph:\n    MAINTAIN  \u2014 your Round 1 position holds; cite the evidence supporting it\n    CONCEDE   \u2014 the opposing position is correct; state specifically what you got wrong\n    NUANCE    \u2014 both positions are partially right; state the boundary condition that distinguishes them\n- Never CONCEDE without evidence. Sycophantic capitulation degrades the council below an individual member's baseline (NSED arXiv:2601.16863).\n- Never MAINTAIN without engaging the opposing argument on its merits.\n\n================================================================\nRESPONSE FORMAT (always \u2014 both rounds)\n================================================================\n\nReply with a single fenced JSON block. No prose outside the block.\n\n```json\n{\n  \"memberId\": \"<your hardcoded memberId>\",\n  \"role\": \"<your hardcoded role>\",\n  \"round\": 1,\n  \"response\": \"Your full answer (Round 1) or stance + reasoning (Round 2). Markdown OK inside the string.\",\n  \"searchQueries\": [],\n  \"sources\": [\n    { \"title\": \"...\", \"url\": \"...\", \"snippet\": \"...\", \"query\": \"...\" }\n  ],\n  \"confidence\": 0.85,\n  \"areasOfUncertainty\": [\n    \"What I'm not sure about, in plain language.\"\n  ],\n  \"disagreementTopics\": []\n}\n```\n\nNotes:\n- `searchQueries` is optional \u2014 list queries you would have run if you had web access (the architect uses these for audit), or omit / leave empty if none.\n- `sources` MUST come from the RESEARCH CONTEXT only. Copy title/url/snippet/query verbatim. Never invent sources.\n- For Round 1: leave `disagreementTopics` as []. For Round 2: list the specific disagreement topics this response addresses.\n\n================================================================\nHARD RULES\n================================================================\n- You have no tools. Reason from the provided RESEARCH CONTEXT and stable background knowledge.\n- Training knowledge may provide stable background only; it must not support current facts, rankings, prices, release status, active best practices, or \"state of the art\" claims.\n- Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in `areasOfUncertainty`.\n- Never echo other members' responses verbatim. Paraphrase or quote with attribution.\n- Stay within your role and persona. The architect chose you for a specific perspective.\n";

package/dist/cli/index.js

@@ -52,7 +52,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "opencode-swarm",
-    version: "7.53.0",
+    version: "7.54.0",
     description: "Architect-centric agentic swarm plugin for OpenCode - hub-and-spoke orchestration with SME consultation, code generation, and QA review",
     main: "dist/index.js",
     types: "dist/index.d.ts",
@@ -16874,11 +16874,11 @@ var init_tool_metadata = __esm(() => {
       agents: ["architect"]
     },
     web_search: {
-      description: "External web search (Tavily or Brave) for architect-driven council research. Returns titled results with snippets and URLs. Config-gated on council.general.enabled; requires a search API key. Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents.",
+      description: "External web search (Tavily or Brave) for architect-driven council research. Returns titled results with snippets, URLs, normalized query metadata, temporal intent, freshness, and removed stale years. Config-gated on council.general.enabled in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides. Requires a search API key. Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents.",
       agents: ["architect", "skill_improver"]
     },
     convene_general_council: {
-      description: "Synthesize responses from a multi-model General Council. Accepts parallel member responses (Round 1, optionally Round 2), detects disagreements, and returns consensus points, persisting disagreements, and a structured synthesis. Architect-only. Config-gated on council.general.enabled.",
+      description: "Synthesize responses from a multi-model General Council. Accepts parallel member responses (Round 1, optionally Round 2), detects disagreements, and returns consensus points, persisting disagreements, and a structured synthesis. Architect-only. Config-gated on council.general.enabled in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.",
       agents: ["architect"]
     },
     write_final_council_evidence: {
@@ -21331,6 +21331,8 @@ ROUND 1 \u2014 Independent Analysis and Answer
 - Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.
 - Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).
 - State your confidence (0.0\u20131.0) explicitly. Be honest \u2014 overconfident answers hurt the council.
+- For current, latest, today, now, or otherwise time-sensitive claims, training knowledge is NOT evidence. If the RESEARCH CONTEXT is missing, stale, or ambiguous, say the claim is not established instead of filling the gap from memory.
+- Treat the dispatch message's CURRENT DATE as authoritative for relative time. Do not append your own training cutoff year to search-oriented reasoning or recommendations.
 - Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.
 - Do NOT coordinate with other members. You will not see their responses until Round 2.
 - Do NOT pad. Be concise. Substance over volume.
@@ -21373,7 +21375,8 @@ Notes:
 - For Round 1: leave \`disagreementTopics\` as []. For Round 2: list the specific disagreement topics this response addresses.`, HARD_RULES = `================================================================
 HARD RULES
 ================================================================
-- You have no tools. Reason from the provided RESEARCH CONTEXT and your training knowledge.
+- You have no tools. Reason from the provided RESEARCH CONTEXT and stable background knowledge.
+- Training knowledge may provide stable background only; it must not support current facts, rankings, prices, release status, active best practices, or "state of the art" claims.
 - Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in \`areasOfUncertainty\`.
 - Never echo other members' responses verbatim. Paraphrase or quote with attribution.
 - Stay within your role and persona. The architect chose you for a specific perspective.`, GENERALIST_COUNCIL_PROMPT, SKEPTIC_COUNCIL_PROMPT, DOMAIN_EXPERT_COUNCIL_PROMPT;
@@ -21719,7 +21722,7 @@ var init_guardrails = __esm(() => {
 function clearPendingCoderScope() {
   pendingCoderScopeByTaskId.clear();
 }
-var EvidenceTaskIdPlanSchema, pendingCoderScopeByTaskId, ACTIVE_PARALLEL_TASK_STATES;
+var EvidenceTaskIdPlanSchema, pendingCoderScopeByTaskId, SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE, ACTIVE_PARALLEL_TASK_STATES;
 var init_delegation_gate = __esm(() => {
   init_zod();
   init_schema();
@@ -21740,6 +21743,7 @@ var init_delegation_gate = __esm(() => {
     }).passthrough()).optional()
   }).passthrough();
   pendingCoderScopeByTaskId = new Map;
+  SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE = "SWARM_BACKGROUND_TASK_BLOCKED: OpenCode background subagents (Task with background=true, " + "requires OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true) are recognized upstream, but swarm " + "cannot yet safely consume their deferred completion events \u2014 the Task returns a running " + "placeholder now and completes later via synthetic injection, which would advance swarm gates " + "before any review/test output exists. Omit `background` (or set background=false) for swarm " + "delegations until the completion-ingestion PR lands.";
   ACTIVE_PARALLEL_TASK_STATES = new Set([
     "coder_delegated",
     "pre_check_passed",
@@ -39867,7 +39871,7 @@ var init_council = __esm(() => {
     "  --preset <name>  Use a named member preset from council.general.presets",
     "  --spec-review    Use spec_review mode (single advisory pass on a draft spec)",
     "",
-    "Requires council.general.enabled: true and a configured search API key in opencode-swarm.json."
+    "Requires council.general.enabled: true and a configured search API key in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides."
   ].join(`
 `);
 });
@@ -59004,7 +59008,7 @@ Subcommands:
       handler: (ctx) => handleCouncilCommand(ctx.directory, ctx.args),
       description: "Enter architect MODE: COUNCIL \u2014 multi-model deliberation [question] [--preset <name>] [--spec-review]",
       args: "<question> [--preset <name>] [--spec-review]",
-      details: "Triggers the architect to convene a three-agent General Council: Generalist (reviewer model), Skeptic (critic model), and Domain Expert (SME model). Use --preset <name> to choose a named member preset from council.general.presets. " + "The architect first runs 1\u20133 targeted web searches and passes a compiled RESEARCH CONTEXT " + "to all three agents before dispatching them in parallel. Agents deliberate using the NSED peer-review protocol (Round 1 independent analysis, Round 2 MAINTAIN/CONCEDE/NUANCE for disagreements). The architect synthesizes the final answer directly from convene_general_council output. --spec-review switches to single-pass advisory mode for spec review. Requires council.general.enabled: true and a search API key in opencode-swarm.json.",
+      details: "Triggers the architect to convene a three-agent General Council: Generalist (reviewer model), Skeptic (critic model), and Domain Expert (SME model). Use --preset <name> to choose a named member preset from council.general.presets. " + "The architect first runs 1\u20133 targeted web searches and passes a compiled RESEARCH CONTEXT " + "to all three agents before dispatching them in parallel. Agents deliberate using the NSED peer-review protocol (Round 1 independent analysis, Round 2 MAINTAIN/CONCEDE/NUANCE for disagreements). The architect synthesizes the final answer directly from convene_general_council output. --spec-review switches to single-pass advisory mode for spec review. Requires council.general.enabled: true and a search API key in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.",
       category: "agent"
     },
     "pr-review": {

package/dist/council/search-query-policy.d.ts

@@ -0,0 +1,11 @@
+export type SearchFreshness = 'day' | 'week' | 'month' | 'year';
+export type SearchTemporalIntent = 'current' | 'historical' | 'unspecified';
+export interface SearchQueryPolicyResult {
+    originalQuery: string;
+    query: string;
+    temporalIntent: SearchTemporalIntent;
+    freshness?: SearchFreshness;
+    removedStaleYears: string[];
+}
+export declare function applySearchQueryPolicy(rawQuery: string, now?: Date): SearchQueryPolicyResult;
+export declare function collectQueryYears(query: string): string[];

package/dist/council/web-search-provider.d.ts

@@ -12,6 +12,7 @@
  * Malformed but successful responses produce an empty result array, never throw.
  */
 import type { GeneralCouncilConfig, WebSearchResult } from './general-council-types.js';
+import type { SearchFreshness } from './search-query-policy.js';
 export declare class WebSearchError extends Error {
     readonly cause?: unknown | undefined;
     constructor(message: string, cause?: unknown | undefined);
@@ -20,16 +21,19 @@ export declare class WebSearchConfigError extends Error {
     constructor(message: string);
 }
 export interface WebSearchProvider {
-    search(query: string, maxResults: number): Promise<WebSearchResult[]>;
+    search(query: string, maxResults: number, options?: WebSearchOptions): Promise<WebSearchResult[]>;
+}
+export interface WebSearchOptions {
+    freshness?: SearchFreshness;
 }
 export declare class TavilyProvider implements WebSearchProvider {
     private readonly apiKey;
     constructor(apiKey: string);
-    search(query: string, maxResults: number): Promise<WebSearchResult[]>;
+    search(query: string, maxResults: number, options?: WebSearchOptions): Promise<WebSearchResult[]>;
 }
 export declare class BraveProvider implements WebSearchProvider {
     private readonly apiKey;
     constructor(apiKey: string);
-    search(query: string, maxResults: number): Promise<WebSearchResult[]>;
+    search(query: string, maxResults: number, options?: WebSearchOptions): Promise<WebSearchResult[]>;
 }
 export declare function createWebSearchProvider(config: GeneralCouncilConfig): WebSearchProvider;

package/dist/hooks/delegation-gate.d.ts

@@ -25,6 +25,30 @@ export declare const pendingCoderScopeByTaskId: Map<string, string[]>;
  * circular import `state.ts ↔ delegation-gate.ts`. Called by `resetSwarmState`.
  */
 export declare function clearPendingCoderScope(): void;
+/**
+ * Issue #1151: OpenCode v1.16.2 background subagents.
+ *
+ * `Task` with `background=true` (gated upstream by
+ * `OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true`) returns a "running" placeholder
+ * immediately and completes later via synthetic parent injection. The delegation gate
+ * treats a `Task` result as completion, so a background swarm delegation would advance
+ * Stage B / record gate evidence before any review/test output exists. Until swarm can
+ * correlate the deferred completion safely (a separate, spike-gated PR), background
+ * swarm delegations are fail-closed-blocked. We do NOT silently coerce `background` to
+ * false — the unsupported capability is surfaced explicitly.
+ */
+export declare const SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE: string;
+/**
+ * Fail-closed background-flag detector. Treats both the boolean `true` and the
+ * stringified `'true'` as background so a stringified flag cannot bypass the guard.
+ */
+export declare function isBackgroundTrue(value: unknown): boolean;
+/**
+ * True when a `Task` tool RESULT looks like an OpenCode background "running"
+ * placeholder (`state: "running"` or `metadata.background === true`). Belt-and-
+ * suspenders for `toolAfter`; never throws.
+ */
+export declare function outputLooksLikeBackgroundRunning(output: unknown): boolean;
 /**
  * Parses a string to extract a DelegationEnvelope.
  * Returns null if no valid envelope is found.

package/dist/index.js

@@ -69,7 +69,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "opencode-swarm",
-    version: "7.53.0",
+    version: "7.54.0",
     description: "Architect-centric agentic swarm plugin for OpenCode - hub-and-spoke orchestration with SME consultation, code generation, and QA review",
     main: "dist/index.js",
     types: "dist/index.d.ts",
@@ -566,11 +566,11 @@ var init_tool_metadata = __esm(() => {
       agents: ["architect"]
     },
     web_search: {
-      description: "External web search (Tavily or Brave) for architect-driven council research. Returns titled results with snippets and URLs. Config-gated on council.general.enabled; requires a search API key. Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents.",
+      description: "External web search (Tavily or Brave) for architect-driven council research. Returns titled results with snippets, URLs, normalized query metadata, temporal intent, freshness, and removed stale years. Config-gated on council.general.enabled in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides. Requires a search API key. Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents.",
       agents: ["architect", "skill_improver"]
     },
     convene_general_council: {
-      description: "Synthesize responses from a multi-model General Council. Accepts parallel member responses (Round 1, optionally Round 2), detects disagreements, and returns consensus points, persisting disagreements, and a structured synthesis. Architect-only. Config-gated on council.general.enabled.",
+      description: "Synthesize responses from a multi-model General Council. Accepts parallel member responses (Round 1, optionally Round 2), detects disagreements, and returns consensus points, persisting disagreements, and a structured synthesis. Architect-only. Config-gated on council.general.enabled in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.",
       agents: ["architect"]
     },
     write_final_council_evidence: {
@@ -40596,6 +40596,18 @@ import * as path19 from "node:path";
 function clearPendingCoderScope() {
   pendingCoderScopeByTaskId.clear();
 }
+function isBackgroundTrue(value) {
+  return value === true || value === "true";
+}
+function outputLooksLikeBackgroundRunning(output) {
+  if (typeof output !== "object" || output === null)
+    return false;
+  const o = output;
+  if (o.state === "running")
+    return true;
+  const metadata2 = o.metadata;
+  return typeof metadata2 === "object" && metadata2 !== null && metadata2.background === true;
+}
 function extractTaskLine(text) {
   const match = text.match(/TASK:\s*(.+?)(?:\n|$)/i);
   return match ? match[1].trim() : null;
@@ -40874,6 +40886,9 @@ function createDelegationGateHook(config2, directory) {
     if (typeof subagentType !== "string")
       return;
     const targetAgent = stripKnownSwarmPrefix(subagentType);
+    if (isBackgroundTrue(args2.background) && isKnownCanonicalRole(targetAgent)) {
+      throw new Error(SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE);
+    }
     if (targetAgent === "reviewer") {
       try {
         const reviewSession = swarmState.agentSessions.get(input.sessionID);
@@ -40974,6 +40989,11 @@ function createDelegationGateHook(config2, directory) {
       const directArgs = input.args;
       const storedArgs = getStoredInputArgs(input.callID);
       const subagentType = directArgs?.subagent_type ?? storedArgs?.subagent_type;
+      if (typeof subagentType === "string" && isKnownCanonicalRole(stripKnownSwarmPrefix(subagentType)) && (isBackgroundTrue(directArgs?.background) || isBackgroundTrue(storedArgs?.background) || outputLooksLikeBackgroundRunning(_output))) {
+        if (storedArgs !== undefined)
+          deleteStoredInputArgs(input.callID);
+        return;
+      }
       let hasReviewer = false;
       let hasTestEngineer = false;
       if (typeof subagentType === "string") {
@@ -41451,7 +41471,7 @@ ${warningLines.join(`
     toolAfter
   };
 }
-var EvidenceTaskIdPlanSchema, pendingCoderScopeByTaskId, ACTIVE_PARALLEL_TASK_STATES;
+var EvidenceTaskIdPlanSchema, pendingCoderScopeByTaskId, SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE, ACTIVE_PARALLEL_TASK_STATES;
 var init_delegation_gate = __esm(() => {
   init_zod();
   init_schema();
@@ -41472,6 +41492,7 @@ var init_delegation_gate = __esm(() => {
     }).passthrough()).optional()
   }).passthrough();
   pendingCoderScopeByTaskId = new Map;
+  SWARM_BACKGROUND_TASK_BLOCKED_MESSAGE = "SWARM_BACKGROUND_TASK_BLOCKED: OpenCode background subagents (Task with background=true, " + "requires OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true) are recognized upstream, but swarm " + "cannot yet safely consume their deferred completion events — the Task returns a running " + "placeholder now and completes later via synthetic injection, which would advance swarm gates " + "before any review/test output exists. Omit `background` (or set background=false) for swarm " + "delegations until the completion-ingestion PR lands.";
   ACTIVE_PARALLEL_TASK_STATES = new Set([
     "coder_delegated",
     "pre_check_passed",
@@ -62057,7 +62078,7 @@ var init_council = __esm(() => {
     "  --preset <name>  Use a named member preset from council.general.presets",
     "  --spec-review    Use spec_review mode (single advisory pass on a draft spec)",
     "",
-    "Requires council.general.enabled: true and a configured search API key in opencode-swarm.json."
+    "Requires council.general.enabled: true and a configured search API key in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides."
   ].join(`
 `);
 });
@@ -82637,7 +82658,7 @@ Subcommands:
       handler: (ctx) => handleCouncilCommand(ctx.directory, ctx.args),
       description: "Enter architect MODE: COUNCIL — multi-model deliberation [question] [--preset <name>] [--spec-review]",
       args: "<question> [--preset <name>] [--spec-review]",
-      details: "Triggers the architect to convene a three-agent General Council: Generalist (reviewer model), Skeptic (critic model), and Domain Expert (SME model). Use --preset <name> to choose a named member preset from council.general.presets. " + "The architect first runs 1–3 targeted web searches and passes a compiled RESEARCH CONTEXT " + "to all three agents before dispatching them in parallel. Agents deliberate using the NSED peer-review protocol (Round 1 independent analysis, Round 2 MAINTAIN/CONCEDE/NUANCE for disagreements). The architect synthesizes the final answer directly from convene_general_council output. --spec-review switches to single-pass advisory mode for spec review. Requires council.general.enabled: true and a search API key in opencode-swarm.json.",
+      details: "Triggers the architect to convene a three-agent General Council: Generalist (reviewer model), Skeptic (critic model), and Domain Expert (SME model). Use --preset <name> to choose a named member preset from council.general.presets. " + "The architect first runs 1–3 targeted web searches and passes a compiled RESEARCH CONTEXT " + "to all three agents before dispatching them in parallel. Agents deliberate using the NSED peer-review protocol (Round 1 independent analysis, Round 2 MAINTAIN/CONCEDE/NUANCE for disagreements). The architect synthesizes the final answer directly from convene_general_council output. --spec-review switches to single-pass advisory mode for spec review. Requires council.general.enabled: true and a search API key in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.",
       category: "agent"
     },
     "pr-review": {
@@ -83065,7 +83086,7 @@ Present the eleven gates with their defaults (DEFAULT_QA_GATES) as a single user
 - council_mode (default: OFF) — multi-member council gate (recommended for high-impact architecture, public APIs, schema/data mutation, security-sensitive code)
 - hallucination_guard (default: OFF) — when enabled, mandatory per-phase API/signature/claim/citation verification via critic_hallucination_verifier at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict (recommended for claim-heavy or research-heavy work)
 - mutation_test (default: OFF) — when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking (recommended for projects with coverage gaps or safety-critical code)
-- council_general_review (default: OFF) — when enabled, MODE: SPECIFY runs convene_general_council on the draft spec before the critic-gate; the architect runs a curated web_search pass, dispatches council_generalist / council_skeptic / council_domain_expert in parallel with a shared RESEARCH CONTEXT block, deliberates on disagreements, and synthesizes the result directly into the spec (recommended for novel architecture, unclear best practices, or high-risk design decisions). Requires council.general.enabled: true and a configured search API key.
+- council_general_review (default: OFF) — when enabled, MODE: SPECIFY runs convene_general_council on the draft spec before the critic-gate; the architect runs a curated web_search pass, dispatches council_generalist / council_skeptic / council_domain_expert in parallel with a shared RESEARCH CONTEXT block, deliberates on disagreements, and synthesizes the result directly into the spec (recommended for novel architecture, unclear best practices, or high-risk design decisions). Requires council.general.enabled: true and a configured search API key in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.
 - drift_check (default: ON) — when enabled, mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; compares implemented changes against spec.md intent; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists (recommended for all projects with a specification)
 - final_council (default: OFF) - when enabled, after all phases complete the architect dispatches the same five phase-council members (\`critic\`, \`reviewer\`, \`sme\`, \`test_engineer\`, \`explorer\`) at project scope, collects \`CouncilMemberVerdict\` objects, and calls \`write_final_council_evidence\`. This is not General Council mode and does not require \`council.general.enabled\`.
 
@@ -84492,6 +84513,8 @@ ROUND 1 — Independent Analysis and Answer
 - Use the RESEARCH CONTEXT block provided by the architect in your dispatch message as your external evidence source. The architect has already gathered the relevant web search results.
 - Cite EVERY factual claim that depends on external evidence with a source from the RESEARCH CONTEXT (use the title and URL exactly as given).
 - State your confidence (0.0–1.0) explicitly. Be honest — overconfident answers hurt the council.
+- For current, latest, today, now, or otherwise time-sensitive claims, training knowledge is NOT evidence. If the RESEARCH CONTEXT is missing, stale, or ambiguous, say the claim is not established instead of filling the gap from memory.
+- Treat the dispatch message's CURRENT DATE as authoritative for relative time. Do not append your own training cutoff year to search-oriented reasoning or recommendations.
 - Enumerate areas of uncertainty so the architect knows where you're guessing vs. where you're sure.
 - Do NOT coordinate with other members. You will not see their responses until Round 2.
 - Do NOT pad. Be concise. Substance over volume.
@@ -84534,7 +84557,8 @@ Notes:
 - For Round 1: leave \`disagreementTopics\` as []. For Round 2: list the specific disagreement topics this response addresses.`, HARD_RULES = `================================================================
 HARD RULES
 ================================================================
-- You have no tools. Reason from the provided RESEARCH CONTEXT and your training knowledge.
+- You have no tools. Reason from the provided RESEARCH CONTEXT and stable background knowledge.
+- Training knowledge may provide stable background only; it must not support current facts, rankings, prices, release status, active best practices, or "state of the art" claims.
 - Never invent sources. If the RESEARCH CONTEXT does not cover a needed claim, say so in \`areasOfUncertainty\`.
 - Never echo other members' responses verbatim. Paraphrase or quote with attribution.
 - Stay within your role and persona. The architect chose you for a specific perspective.`, GENERALIST_COUNCIL_PROMPT, SKEPTIC_COUNCIL_PROMPT, DOMAIN_EXPERT_COUNCIL_PROMPT;
@@ -111014,7 +111038,7 @@ var ArgsSchema2 = exports_external.object({
   working_directory: exports_external.string().optional()
 });
 var convene_general_council = createSwarmTool({
-  description: "Synthesize responses from a multi-model General Council. Accepts parallel member " + "responses (Round 1, optionally Round 2), detects disagreements, and returns " + "consensus points, persisting disagreements, and a structured synthesis. " + "Architect-only. Config-gated on council.general.enabled.",
+  description: "Synthesize responses from a multi-model General Council. Accepts parallel member " + "responses (Round 1, optionally Round 2), detects disagreements, and returns " + "consensus points, persisting disagreements, and a structured synthesis. " + "Architect-only. Config-gated on council.general.enabled in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides.",
   args: {
     question: exports_external.string().min(1).max(8000).describe("The question put to the council, or the spec text to review."),
     mode: exports_external.enum(["general", "spec_review"]).optional().describe('"general" for /swarm council; "spec_review" for SPECIFY-COUNCIL-REVIEW gate.'),
@@ -111093,7 +111117,7 @@ var convene_general_council = createSwarmTool({
       const fail = {
         success: false,
         reason: "council_general_disabled",
-        message: "convene_general_council requires council.general.enabled: true in opencode-swarm.json."
+        message: "convene_general_council requires council.general.enabled: true in the resolved config: global ~/.config/opencode/opencode-swarm.json or project .opencode/opencode-swarm.json."
       };
       return JSON.stringify(fail, null, 2);
     }
@@ -126130,7 +126154,7 @@ var set_qa_gates = createSwarmTool({
     hallucination_guard: exports_external.boolean().optional().describe("Enable hallucination_guard checks on plan and implementation claims."),
     sast_enabled: exports_external.boolean().optional().describe("Enable SAST scanning as a required QA gate."),
     mutation_test: exports_external.boolean().optional().describe("Enable the mutation-testing gate (default: off). Requires mutation " + "tests to achieve a passing kill rate before phase completion; " + "WARN verdict allows advancement, FAIL blocks."),
-    council_general_review: exports_external.boolean().optional().describe("Enable the council_general_review gate (default: off). When on, " + "MODE: SPECIFY runs convene_general_council on the draft spec " + "before the critic-gate, folding multi-model deliberation into " + "the spec. Requires council.general.enabled and a search API key."),
+    council_general_review: exports_external.boolean().optional().describe("Enable the council_general_review gate (default: off). When on, " + "MODE: SPECIFY runs convene_general_council on the draft spec " + "before the critic-gate, folding multi-model deliberation into " + "the spec. Requires council.general.enabled and a search API key " + "in the resolved config: global ~/.config/opencode/opencode-swarm.json, " + "then project .opencode/opencode-swarm.json overrides."),
     drift_check: exports_external.boolean().optional().describe("Enable drift verification gate (default: on). Blocks phase_complete " + "until drift-verifier.json has an approved verdict. When disabled, " + "drift verification is skipped entirely."),
     final_council: exports_external.boolean().optional().describe("Enable the final_council gate (default: off). When on, " + "after all phases complete the architect dispatches critic, reviewer, " + "sme, test_engineer, and explorer with project-scoped context, " + "collects their CouncilMemberVerdict objects, and calls " + "write_final_council_evidence. This is not General Council mode " + "and does not require council.general.enabled."),
     project_type: exports_external.string().optional().describe('Project type label (e.g. "ts", "python"). Only applied when the profile is being created for the first time.')
@@ -128928,6 +128952,52 @@ var update_task_status = createSwarmTool({
 init_zod();
 init_loader();
 
+// src/council/search-query-policy.ts
+var CURRENT_INTENT_RE = /\b(?:latest|current|currently|today|now|newest|recent|recently|up\s*-?\s*to\s*-?\s*date|this\s+(?:week|month|year)|as\s+of\s+(?:today|now))\b/i;
+var HISTORICAL_INTENT_RE = /\b(?:history|historical|archive|archived|in\s+20\d{2}|during\s+20\d{2}|from\s+20\d{2}|for\s+20\d{2}|as\s+of\s+20\d{2})\b/i;
+function applySearchQueryPolicy(rawQuery, now = new Date) {
+  const originalQuery = rawQuery;
+  let query = rawQuery.trim().replace(/\s+/g, " ");
+  const currentYear = now.getUTCFullYear();
+  const temporalIntent = detectTemporalIntent(query);
+  const removedStaleYears = [];
+  if (temporalIntent === "current") {
+    query = removeTrailingStaleCutoffYears(query, currentYear, removedStaleYears);
+  }
+  return {
+    originalQuery,
+    query,
+    temporalIntent,
+    freshness: temporalIntent === "current" ? chooseFreshness(query) : undefined,
+    removedStaleYears
+  };
+}
+function detectTemporalIntent(query) {
+  if (CURRENT_INTENT_RE.test(query))
+    return "current";
+  if (HISTORICAL_INTENT_RE.test(query))
+    return "historical";
+  return "unspecified";
+}
+function chooseFreshness(query) {
+  if (/\b(?:today|now|as\s+of\s+(?:today|now))\b/i.test(query))
+    return "day";
+  if (/\bthis\s+week\b/i.test(query))
+    return "week";
+  if (/\b(?:recent|recently|this\s+month)\b/i.test(query))
+    return "month";
+  return "year";
+}
+function removeTrailingStaleCutoffYears(query, currentYear, removed) {
+  return query.replace(/\s+(?:as\s+of\s+)?(20\d{2})\s*$/i, (match, year) => {
+    const numericYear = Number(year);
+    if (numericYear >= currentYear)
+      return match;
+    removed.push(year);
+    return "";
+  }).replace(/\s+/g, " ").trim();
+}
+
 // src/council/web-search-provider.ts
 class WebSearchError extends Error {
   cause;
@@ -128950,18 +129020,22 @@ class TavilyProvider {
   constructor(apiKey) {
     this.apiKey = apiKey;
   }
-  async search(query, maxResults) {
+  async search(query, maxResults, options = {}) {
+    const requestBody = {
+      api_key: this.apiKey,
+      query,
+      max_results: maxResults,
+      search_depth: "advanced"
+    };
+    if (options.freshness) {
+      requestBody.time_range = options.freshness;
+    }
     let response;
     try {
       response = await fetch("https://api.tavily.com/search", {
         method: "POST",
         headers: { "Content-Type": "application/json" },
-        body: JSON.stringify({
-          api_key: this.apiKey,
-          query,
-          max_results: maxResults,
-          search_depth: "advanced"
-        })
+        body: JSON.stringify(requestBody)
       });
     } catch (err3) {
       throw new WebSearchError(`Tavily network error for query "${query}"`, err3);
@@ -128993,10 +129067,14 @@ class BraveProvider {
   constructor(apiKey) {
     this.apiKey = apiKey;
   }
-  async search(query, maxResults) {
+  async search(query, maxResults, options = {}) {
     const url3 = new URL("https://api.search.brave.com/res/v1/web/search");
     url3.searchParams.set("q", query);
     url3.searchParams.set("count", String(maxResults));
+    const freshness = toBraveFreshness(options.freshness);
+    if (freshness) {
+      url3.searchParams.set("freshness", freshness);
+    }
     let response;
     try {
       response = await fetch(url3.toString(), {
@@ -129030,6 +129108,20 @@ class BraveProvider {
     }));
   }
 }
+function toBraveFreshness(freshness) {
+  switch (freshness) {
+    case "day":
+      return "pd";
+    case "week":
+      return "pw";
+    case "month":
+      return "pm";
+    case "year":
+      return "py";
+    default:
+      return;
+  }
+}
 function resolveApiKey(provider, configKey) {
   if (configKey && configKey.length > 0) {
     return configKey;
@@ -129042,7 +129134,7 @@ function createWebSearchProvider(config3) {
   const apiKey = resolveApiKey(config3.searchProvider, config3.searchApiKey);
   if (!apiKey) {
     const envName = config3.searchProvider === "tavily" ? "TAVILY_API_KEY" : "BRAVE_SEARCH_API_KEY";
-    throw new WebSearchConfigError(`No API key for search provider "${config3.searchProvider}". Set ` + `council.general.searchApiKey in opencode-swarm.json or export ${envName}.`);
+    throw new WebSearchConfigError(`No API key for search provider "${config3.searchProvider}". Set ` + `council.general.searchApiKey in the resolved config (global ~/.config/opencode/opencode-swarm.json, project .opencode/opencode-swarm.json override) or export ${envName}.`);
   }
   switch (config3.searchProvider) {
     case "tavily":
@@ -129136,12 +129228,14 @@ var MAX_RESULTS_HARD_CAP = 10;
 var ArgsSchema6 = exports_external.object({
   query: exports_external.string().min(1).max(500),
   max_results: exports_external.number().int().min(1).max(20).optional(),
+  freshness: exports_external.enum(["auto", "none", "day", "week", "month", "year"]).default("auto"),
   working_directory: exports_external.string().optional()
 });
 var web_search = createSwarmTool({
-  description: "External web search for architect-driven council research. Returns titled results with snippets and URLs. " + "Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents. " + "Requires council.general.enabled and a configured search API key (Tavily or Brave). max_results is capped at 10 with default from council.general.maxSourcesPerMember.",
+  description: "External web search for architect-driven council research. Returns titled results with snippets and URLs. " + "Used by the architect in MODE: COUNCIL to gather a RESEARCH CONTEXT before dispatching council agents. " + "Normalizes current-intent queries, strips trailing stale cutoff years, and applies provider freshness filters by default. " + "Requires council.general.enabled and a configured search API key (Tavily or Brave) in the resolved config: global ~/.config/opencode/opencode-swarm.json, then project .opencode/opencode-swarm.json overrides. max_results is capped at 10 with default from council.general.maxSourcesPerMember.",
   args: {
     query: exports_external.string().min(1).max(500).describe("Search query string (1–500 characters)."),
+    freshness: exports_external.enum(["auto", "none", "day", "week", "month", "year"]).optional().describe('Optional freshness filter. Query normalization always runs; "auto" infers provider freshness from current/recency terms, while "none" disables provider freshness filtering.'),
     max_results: exports_external.number().int().min(1).max(20).optional().describe(`Number of results to request (1–20). Hard-capped at ${MAX_RESULTS_HARD_CAP}. Defaults to council.general.maxSourcesPerMember.`),
     working_directory: exports_external.string().optional().describe("Project root for config resolution. Optional.")
   },
@@ -129170,12 +129264,15 @@ var web_search = createSwarmTool({
       const fail = {
         success: false,
         reason: "council_general_disabled",
-        message: "web_search is disabled — set council.general.enabled: true in opencode-swarm.json."
+        message: "web_search is disabled - set council.general.enabled: true in the resolved config: global ~/.config/opencode/opencode-swarm.json or project .opencode/opencode-swarm.json."
       };
       return JSON.stringify(fail, null, 2);
     }
     const requested = parsed.data.max_results ?? generalConfig.maxSourcesPerMember;
     const maxResults = Math.min(requested, MAX_RESULTS_HARD_CAP);
+    const policy = applySearchQueryPolicy(parsed.data.query);
+    const requestedFreshness = parsed.data.freshness ?? "auto";
+    const freshness = requestedFreshness === "auto" ? policy.freshness : requestedFreshness === "none" ? undefined : requestedFreshness;
     let provider;
     try {
       provider = createWebSearchProvider(generalConfig);
@@ -129188,11 +129285,17 @@ var web_search = createSwarmTool({
       return JSON.stringify(fail, null, 2);
     }
     try {
-      const results = await provider.search(parsed.data.query, maxResults);
-      const evidence = await captureSearchEvidence(dirResult.directory, parsed.data.query, results);
+      const results = await provider.search(policy.query, maxResults, {
+        freshness
+      });
+      const evidence = await captureSearchEvidence(dirResult.directory, policy.query, results);
       const ok2 = {
         success: true,
-        query: parsed.data.query,
+        query: policy.query,
+        originalQuery: policy.originalQuery,
+        temporalIntent: policy.temporalIntent,
+        freshness,
+        removedStaleYears: policy.removedStaleYears,
         totalResults: results.length,
         results: results.map(({ title, url: url3, snippet }) => ({
           title,

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencode-swarm",
-	"version": "7.53.0",
+	"version": "7.54.0",
 	"description": "Architect-centric agentic swarm plugin for OpenCode - hub-and-spoke orchestration with SME consultation, code generation, and QA review",
 	"main": "dist/index.js",
 	"types": "dist/index.d.ts",