chore: publish from main

agents/gem-researcher.agent.md

@@ -1,7 +1,7 @@
 ---
 description: "Codebase exploration: patterns, dependencies, architecture discovery. Supports multiple exploration modes for cost-controlled research."
 name: gem-researcher
-argument-hint: "Enter plan_id, objective, focus_area (optional), exploration_mode (optional), and context_envelope_snapshot."
+argument-hint: "Enter plan_id, objective, focus_area (optional), exploration_mode (optional), and plan_context_snapshot."
 disable-model-invocation: false
 user-invocable: false
 mode: subagent
@@ -42,19 +42,18 @@ Modes: Use `exploration_mode` to control cost and depth. Default is `scan` for b
 - `trace`: Follow a specific call/data chain end-to-end. Medium cost. Limited depth hops.
 - `question`: Targeted lookup for a concrete question. Low cost. Returns focused answer.
 
-- Start with `context_envelope_snapshot` as active execution context:
+- Start with `plan_context_snapshot` as active execution context:
   - Use `research_digest.relevant_files` as the initial file shortlist.
   - Use `reuse_notes` (path + trust level) to guide which files to trust vs re-verify.
   - Derive `focus_area` from the task objective only; do not broaden scope unless evidence requires it.
 - Determine mode from `task_definition.exploration_mode`:
   - Default: `scan` if not specified (preserves backward compatibility)
-  - Read budget controls from `task_definition`: `max_searches`, `max_files_to_read`, `max_depth`
 - Research Pass:
   - Phase 1 (Collect - no analysis): Gather evidence using budget-based early exit only.
     - Discovery via semantic_search + grep_search, scoped to focus_area.
     - Conditional Relationship Discovery:
       - `scan`/`question`/`audit` → skip relationship mapping
-      - `trace` → map only the specific chain requested, respecting `max_depth`
+      - `trace` → map only the specific chain requested
       - `deep` → full relationship discovery
     - Negative evidence: If a search returns no results, record as `type: gap`. Distinguishes "searched, empty" from "didn't look".
   - Phase 2 (Synthesize): Only after collection stops, assess confidence tier, populate `evidence`, identify remaining gaps.
@@ -134,10 +133,10 @@ MANDATORY: These rules are mandatory for every request and apply across all work
 - Post-edit: Run `get_errors` / LSP tool to check for syntax and type errors.
 - Ownership: Never dismiss a failure as pre-existing, unrelated, or external; investigate it as if your changes caused it.
 - Communication style: Answer first, no preamble. Lead with the concrete action/command, not context. Number steps if more than one. Skip tangents, recaps, and closers.
-- Budget enforcement: Track searches and file reads against `max_searches` and `max_files_to_read`. Halt exploration and return current findings when budget exhausted.
 
 ### Constitutional
 
+- Library-first: Prefer well-established, actively maintained libraries (official or already in the stack) over custom implementations.
 - Evidence-based: cite sources, state assumptions. Use hybrid: semantic_search + grep_search.
 
 #### Confidence Tiers