feat: add more ByteRover config options (#11)

* feat: more config options

* docs: add npm badge and align config defaults

* docs: commit byterover context tree updates

* docs: byterover

* docs: AGENTS.md

Author: ian-pascoe

.brv/context-tree/facts/conventions/brv_context_tree_files_must_be_committed.md

@@ -0,0 +1,49 @@
+---
+title: BRV Context Tree Files Must Be Committed
+summary: The repository convention is that .brv/context-tree files should always be committed, and they were committed in a docs-scoped commit.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:51:04.126Z'
+updatedAt: '2026-04-24T18:52:22.543Z'
+---
+## Reason
+Capture repository convention and commit outcome for durable recall
+
+## Raw Concept
+**Task:**
+Document the repository convention that .brv/context-tree files must be committed and record the related docs commit outcome
+
+**Changes:**
+- Established that .brv context-tree files are part of committed repository state
+- Established that .brv/context-tree files are always committed
+- Recorded the docs-scoped commit used for the context-tree update
+- Captured verification results and PR branch information
+
+**Flow:**
+User instruction -> commit .brv/context-tree files -> verify hooks/tests -> push to PR branch
+
+**Timestamp:** 2026-04-24
+
+**Author:** user
+
+## Narrative
+### Structure
+This knowledge belongs in the conventions domain because it defines a repository workflow rule. It also preserves the commit outcome and verification state associated with that rule.
+
+### Dependencies
+Depends on the repository practice of treating .brv/context-tree content as committed knowledge rather than transient chat context.
+
+### Highlights
+The stated convention explicitly overrides any conflicting note that says not to stage .brv/context-tree files. The recorded commit passed pre-commit verification and left the working tree clean.
+
+### Rules
+“.brv context-tree files should always be committed. just put it under a `docs:` commit”
+
+## Facts
+- **brv_context_tree_commit_policy**: .brv/context-tree files should always be committed [convention]
+- **brv_context_tree_commit_type**: The .brv/context-tree files were committed in a docs: commit [project]
+- **brv_context_tree_commit_hash**: The commit recorded for the .brv/context-tree updates was a7e757b docs: commit byterover context tree updates [project]
+- **pr_branch**: The updated PR branch is https://github.com/ian-pascoe/opencode-byterover/pull/11 [project]
+- **pre_commit_verification**: Pre-commit verification passed pnpm format:check, pnpm lint, pnpm test, and pnpm typecheck [project]
+- **working_tree_status**: The working tree was clean after the commit was pushed [project]

.brv/context-tree/facts/project/agents_md_repository_guidance.md

@@ -0,0 +1,73 @@
+---
+title: Agents Md Repository Guidance
+summary: Repository guidance for AGENTS.md covers verified commands, entrypoints, ByteRover state handling, CI/hook order differences, and release workflow conventions.
+tags: []
+related: [release_management/ci/changesets_and_github_actions_ci.md, release_management/ci/husky_pre_commit_checks.md, facts/project/context.md]
+keywords: []
+createdAt: '2026-04-24T18:54:58.460Z'
+updatedAt: '2026-04-24T18:56:11.897Z'
+---
+## Reason
+Preserve the verified repo-specific AGENTS.md guidance created for future OpenCode sessions
+
+## Raw Concept
+**Task:**
+Document compact repo-specific guidance for future OpenCode sessions
+
+**Changes:**
+- Defined the investigation order for repo sources
+- Specified what AGENTS.md should include and exclude
+- Established in-place editing for an existing AGENTS.md
+- Prioritize README, manifests, workspace config, lockfiles, CI, pre-commit, task runner config, and repo-local instruction files as investigation sources
+- Use executable sources of truth over prose when conflicts appear
+- Keep AGENTS.md compact and high-signal, focused on durable repo-specific guidance
+- Captured verified package manager, Node targets, and entrypoints
+- Recorded test runner and focused verification guidance
+- Recorded generated/local state directories and release workflow conventions
+- Captured the mismatch between Husky pre-commit order and CI order
+
+**Files:**
+- README.md
+- package.json
+- pnpm-workspace.yaml
+- pnpm-lock.yaml
+- rolldown.config.ts
+- tsconfig.json
+- .github/workflows/ci.yml
+- .husky/pre-commit
+- .opencode/opencode.jsonc
+- AGENTS.md
+- .opencode/package.json
+- src/index.ts
+- src/index.test.ts
+- .changeset/config.json
+
+**Flow:**
+investigate executable sources -> verify repo conventions -> curate durable guidance
+
+**Timestamp:** 2026-04-24
+
+**Author:** User instruction
+
+## Narrative
+### Structure
+The guidance is intentionally compact and focused on non-obvious repository behavior that future agents could miss.
+
+### Dependencies
+It draws from root manifests, CI workflow, Husky hook, entrypoint files, and changeset configuration.
+
+### Highlights
+The most important workflow detail is that Husky and CI run checks in different orders; the guidance preserves both instead of assuming one canonical sequence.
+
+### Rules
+Include only high-signal, repo-specific guidance such as exact commands and shortcuts the agent would otherwise guess wrong; architecture notes that are not obvious from filenames; conventions that differ from language or framework defaults; setup requirements, environment quirks, and operational gotchas; references to existing instruction sources that matter. Exclude generic software advice, long tutorials, exhaustive file trees, obvious language conventions, speculative claims, and content better stored in another file referenced via `opencode.json` instructions.
+
+## Facts
+- **package_manager**: The repository uses pnpm as the package manager. [project]
+- **node_versions**: The project targets Node 22 in CI and uses Node 24 in the local package config. [project]
+- **entrypoints**: The plugin entrypoints are src/index.ts and src/index.test.ts. [project]
+- **test_runner**: The repository uses Vitest for testing. [project]
+- **state_directories**: The repository keeps generated and local state in dist/, .brv/, and .changeset/. [project]
+- **pre_commit_order**: Husky pre-commit runs format:check, lint, test, and typecheck in that order. [project]
+- **ci_order**: CI runs format:check, lint, typecheck, test, and build in that order. [project]
+- **release_workflow**: The repo relies on changesets for release workflow conventions. [project]

.brv/context-tree/facts/project/byterover_context_availability.md

@@ -0,0 +1,36 @@
+---
+title: Byterover Context Availability
+summary: The assistant confirmed it can see the full <byterover-context> block in the conversation, including all 5 topics in detail.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:26:16.489Z'
+updatedAt: '2026-04-24T18:26:16.489Z'
+---
+## Reason
+Record that the assistant can see the full byterover-context block in conversation when present.
+
+## Raw Concept
+**Task:**
+Document conversation context availability behavior
+
+**Changes:**
+- Confirmed visibility of the full byterover-context block in conversation
+
+**Flow:**
+user asks about visibility -> assistant confirms full context block is present
+
+**Timestamp:** 2026-04-24
+
+**Author:** assistant
+
+## Narrative
+### Structure
+A short exchange where the user asks whether the long conversation block is visible and the assistant confirms it is.
+
+### Highlights
+The assistant explicitly states that the full <byterover-context> block is present and visible, and that the block contains all 5 topics in detail.
+
+## Facts
+- **byterover_context_availability**: The assistant can see the full <byterover-context> block in the conversation when it is present. [project]
+- **byterover_context_topics**: The conversation included a full <byterover-context> block with all 5 topics in detail. [project]

.brv/context-tree/facts/project/byterover_recall_query_echo_fix.md

@@ -0,0 +1,48 @@
+---
+title: ByteRover recall query echo fix
+summary: ByteRover recall responses are sanitized by stripping only the echoed query from the Summary header; tests, lint, typecheck, and build all passed.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:13:13.757Z'
+updatedAt: '2026-04-24T18:13:13.757Z'
+---
+## Reason
+Document the durable code change that strips echoed recall queries from ByteRover summaries while preserving retrieved context.
+
+## Raw Concept
+**Task:**
+Strip echoed ByteRover recall queries from formatted responses without removing the retrieved context.
+
+**Changes:**
+- Added stripEchoedRecallQuery(content, query) in src/index.ts
+- Added regression coverage in src/index.test.ts
+- Fixed a test harness gap by mocking tui.showToast so setup warnings do not crash tests
+
+**Files:**
+- src/index.ts
+- src/index.test.ts
+
+**Flow:**
+recall query -> ByteRover response -> sanitize summary header -> preserve details/sources/gaps -> push into system
+
+**Author:** assistant
+
+## Narrative
+### Structure
+The fix is intentionally narrow: it targets only the echoed query fragment inside the ByteRover Summary header and leaves the rest of the response intact.
+
+### Dependencies
+The test suite uses a mocked brvBridge.recall path, so the behavior is covered without contacting ByteRover directly.
+
+### Highlights
+Verification succeeded across targeted tests and repository-wide checks, confirming the sanitizer did not break formatting or type safety.
+
+### Examples
+The preserved response sections include **Summary**, **Details**, **Sources**, and **Gaps**.
+
+## Facts
+- **recall_query_sanitizer**: The project added stripEchoedRecallQuery(content, query) in src/index.ts to remove only the echoed recall query from ByteRover summary headers. [project]
+- **recall_query_sanitization_scope**: The sanitizer removes only the ` for "<full recall query>"` portion from a ByteRover `**Summary**: Found ...` header and preserves the rest of the returned context. [project]
+- **recall_query_regression_test**: A regression test was added in src/index.test.ts that simulates ByteRover echoing the full recall query. [project]
+- **verification_commands**: Repository verification passed with pnpm test -- src/index.test.ts, pnpm format:check, pnpm lint, pnpm typecheck, pnpm test, and pnpm build. [project]

.brv/context-tree/facts/project/byterover_recall_query_echo_issue.md

@@ -0,0 +1,56 @@
+---
+title: Byterover recall query echo issue
+summary: Recall results echo the full instruction/conversation because brvBridge.recall is called with the entire formatted prompt; fix by using a concise query and optionally stripping ByteRover boilerplate before injection.
+tags: []
+related: [facts/project/injected_byterover_context_availability.md]
+keywords: []
+createdAt: '2026-04-24T18:05:09.757Z'
+updatedAt: '2026-04-24T18:05:09.757Z'
+---
+## Reason
+Document the cause of query and conversation echo in recall results from src/index.ts
+
+## Raw Concept
+**Task:**
+Explain why query and conversation text appears in recall results in src/index.ts and document the relevant implementation details.
+
+**Changes:**
+- Identified that brvBridge.recall is passed a multiline prompt containing instructions and recent conversation
+- Observed that recall content is injected back into system messages via <byterover-context>
+- Noted that future recall requests can include previously injected context
+
+**Files:**
+- src/index.ts
+
+**Flow:**
+session.idle or session.compacting -> curateTurn -> brvBridge.persist; system.transform -> fetchMessagesForRecall -> brvBridge.recall -> system.push(<byterover-context>)
+
+**Timestamp:** 2026-04-24
+
+**Author:** ByteRover context engineer
+
+## Narrative
+### Structure
+The plugin curates conversation turns when a session idles or compacts, then recalls context during system transform by fetching recent messages and pushing recalled content into the system prompt.
+
+### Dependencies
+Relies on BrvBridge recall/persist behavior and the session message history returned by client.session.messages.
+
+### Highlights
+The root cause is query construction: the recall API receives the full instruction block and recent conversation rather than a narrow search query. A secondary mitigation is sanitizing known ByteRover response boilerplate before injection.
+
+### Rules
+Do not use the full formatted conversation as the recall query. Prefer a concise query derived from the latest user message. Strip known ByteRover boilerplate before pushing recalled content when needed.
+
+### Examples
+Example problematic query text begins with: Recall any relevant context that would help answer the latest user message.
+Use the recent conversation only to resolve references and intent.
+Recent conversation:
+
+---
+[user]...
+
+## Facts
+- **byterover_recall_query**: ByteroverPlugin calls brvBridge.recall with the entire recall instruction plus recent conversation as the query string. [project]
+- **byterover_recall_output**: The recall output can echo ByteRover boilerplate such as Summary, Details, Sources, and Gaps into the injected system context. [project]
+- **byterover_recall_feedback_loop**: A feedback loop can occur because injected <byterover-context> content becomes part of future session history and can be included in later recall queries. [project]

.brv/context-tree/facts/project/configurable_recall_and_persist_prompts.md

@@ -0,0 +1,42 @@
+---
+title: Configurable Recall and Persist Prompts
+summary: Recall and persist instruction text can be overridden via config fields while preserving existing message formatting and <byterover-context> injection behavior.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:27:49.316Z'
+updatedAt: '2026-04-24T18:27:49.316Z'
+---
+## Reason
+Document configurable prompt overrides for recall and persist flows
+
+## Raw Concept
+**Task:**
+Document making recall and persist prompts configurable through config options
+
+**Changes:**
+- Add optional config fields recallPrompt and persistPrompt
+- Use default hardcoded prompt text when config overrides are absent
+- Apply recallPrompt in brvBridge.recall
+- Apply persistPrompt in brvBridge.persist
+
+**Flow:**
+config options -> choose override or default prompt -> assemble instruction block -> formatted conversation messages
+
+**Timestamp:** 2026-04-24
+
+## Narrative
+### Structure
+Two optional config fields override the instruction text for recall and persist paths without changing message formatting.
+
+### Dependencies
+The prompt assembly must continue to use the existing conversation formatting and <byterover-context> injection behavior.
+
+### Highlights
+Defaults remain unchanged for existing users, and tests should cover default behavior plus custom recallPrompt and persistPrompt usage.
+
+## Facts
+- **prompt_configurability**: The recall prompt and persist prompt should be configurable via config options. [project]
+- **prompt_override_scope**: Custom prompt values override only the instruction text. [project]
+- **conversation_formatting**: Existing conversation formatting must be preserved. [project]
+- **byterover_context_injection**: The <byterover-context> injection behavior must be preserved. [project]

.brv/context-tree/facts/project/context.md

@@ -0,0 +1,10 @@
+# Topic: project
+
+## Overview
+Covers the handling of ByteRover recall responses, specifically sanitizing echoed query text before the result is injected into the system.
+
+## Key Concepts
+- ByteRover recall
+- summary-header sanitization
+- regression testing
+- test harness mocking

.brv/context-tree/facts/project/context_tree_commit_policy.md

@@ -0,0 +1,33 @@
+---
+title: Context Tree Commit Policy
+summary: .brv context-tree files should always be committed
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:50:56.318Z'
+updatedAt: '2026-04-24T18:50:56.318Z'
+---
+## Reason
+Capture durable repository convention from user instruction
+
+## Raw Concept
+**Task:**
+Document repository policy for .brv context-tree files
+
+**Changes:**
+- Established that .brv context-tree files must always be committed
+
+**Flow:**
+edit context-tree files -> commit changes
+
+**Timestamp:** 2026-04-24
+
+## Narrative
+### Structure
+Repository workflow includes committing updates to the .brv context-tree alongside relevant changes.
+
+### Highlights
+The user explicitly stated that .brv context-tree files should always be committed.
+
+## Facts
+- **context_tree_commit_policy**: .brv context-tree files should always be committed [convention]

.brv/context-tree/facts/project/conversation_context_quoting_boundary.md

@@ -0,0 +1,33 @@
+---
+title: Conversation Context Quoting Boundary
+summary: The assistant refuses to quote hidden or injected system/developer context verbatim and instead offers a concise summary or answers about its contents.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-04-24T18:19:05.394Z'
+updatedAt: '2026-04-24T18:19:05.395Z'
+---
+## Reason
+Capture the assistant boundary on hidden or injected context quoting
+
+## Raw Concept
+**Task:**
+Document the assistant boundary around quoting hidden or injected context
+
+**Changes:**
+- Recorded refusal to quote hidden or injected system/developer context verbatim
+
+**Flow:**
+user asks for quoting -> assistant refuses verbatim quote -> offers summary or targeted answer
+
+**Timestamp:** 2026-04-24T18:19:00.852Z
+
+## Narrative
+### Structure
+A brief conversation note capturing the assistant’s policy boundary on hidden/injected context.
+
+### Highlights
+The assistant explicitly offers concise summaries or specific answers instead of verbatim quotation.
+
+## Facts
+- **context_quoting_boundary**: The assistant cannot quote hidden or injected system/developer context verbatim, even when it is visible to it. [project]