refactor: registry caplets

.brv/.gitignore

@@ -21,18 +21,6 @@ _index.md
 # END opencode-byterover
 
 
-
-
-
-
-
-
-
-
-
-
-
-
 # Review backups
 
 # Generated files

.brv/context-tree/architecture/remote_control/remote-control-boundaries-are-enforced-by-server-owned-state-and-sanitized-input.md

@@ -0,0 +1,23 @@
+---
+confidence: 0.9
+sources: [facts/_index.md, facts/_index.md, project/_index.md]
+synthesized_at: '2026-05-26T19:23:43.123Z'
+type: synthesis
+title: Remote control boundaries are enforced by server-owned state and sanitized inputs
+summary: Both facts and project docs frame remote control as a boundary where local-only fields are stripped and server-owned secrets stay protected.
+tags: [remote-control, security, sanitization, completion, server-owned]
+related: []
+keywords: [boundary, sanitization, server-owned, redaction, routing, local-only, remote, auth]
+createdAt: '2026-05-26T19:23:43.123Z'
+updatedAt: '2026-05-26T19:23:43.123Z'
+---
+
+# Remote control boundaries are enforced by server-owned state and sanitized inputs
+
+Across facts and project, remote-control behavior is consistently constrained by a trust boundary: local-only add fields are stripped before remote requests, routing uses only server-owned variables, and completion/remote operations must not leak auth diagnostics or other secret state.
+
+## Evidence
+
+- **facts**: Remote mutation routing confirmed request sanitization, server boundary checks, response parsing, and error redaction; local-only add fields `global`, `print`, `output`, and `destinationRoot` are stripped before remote requests.
+- **facts**: Nested `request.operation` validation is confirmed, and remote routing uses only `CAPLETS_MODE` and `CAPLETS_SERVER_URL`.
+- **project**: The completion/remote-control workflow distinguishes backend IDs vs tool names by prefix and degrades safely on failures/timeouts, while local hidden completion routes through `CapletsEngine.completeCliWords`.

.brv/context-tree/docs/plans/active_caplets_planning_documents.md

@@ -2,7 +2,7 @@
 title: Active Caplets Planning Documents
 summary: Active caplets planning notes covering backend, remote control, CLI, HTTP actions, GraphQL, hot reload, XDG paths, and release-related work.
 tags: []
-related: [architecture/remote_control/context.md, architecture/auth/context.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/context.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [architecture/remote_control/context.md, architecture/auth/context.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/context.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: []
 createdAt: '2026-05-21T10:20:40.246Z'
 updatedAt: '2026-05-21T10:21:06.053Z'

.brv/context-tree/docs/plans/completion_discovery_refactor_implementation_plan.md

@@ -2,7 +2,7 @@
 title: Completion Discovery Refactor Implementation Plan
 summary: Plan for shared CLI completion metadata, cache-backed discovery, completion config defaults, remote completion routing, and final verification.
 tags: []
-related: [architecture/remote_control/remote_control_api_shape.md, architecture/remote_control/cli_remote_mode_selection.md, docs/plans/active_caplets_planning_documents.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/context.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [architecture/remote_control/remote_control_api_shape.md, architecture/remote_control/cli_remote_mode_selection.md, docs/plans/active_caplets_planning_documents.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/context.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: []
 createdAt: '2026-05-21T17:14:24.407Z'
 updatedAt: '2026-05-21T17:14:24.407Z'

.brv/context-tree/docs/plans/completion_local_discovery_and_split_targets.md

@@ -2,7 +2,7 @@
 title: Completion Local Discovery and Split Targets
 summary: Plan saved for fixing local live discovery of existing caplet.tool completions and adding split <caplet> <tool> targets, with formatting verified.
 tags: []
-related: [docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/context.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/context.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: []
 createdAt: '2026-05-21T23:07:39.925Z'
 updatedAt: '2026-05-21T23:07:39.925Z'

.brv/context-tree/docs/plans/context.md

@@ -1,5 +1,5 @@
 ---
-related: [docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 ---
 # Topic: plans
 

.brv/context-tree/docs/plans/docker_image_publishing_for_release_pipeline.md

@@ -2,7 +2,7 @@
 title: Docker Image Publishing for Release Pipeline
 summary: 'Release workflow should publish GHCR Docker images only after Changesets publishes npm packages, with packages: write permission and Docker build/login steps gated on published releases.'
 tags: []
-related: [architecture/remote_control/release_workflow.md, docs/plans/active_caplets_planning_documents.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [architecture/remote_control/release_workflow.md, docs/plans/active_caplets_planning_documents.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: []
 createdAt: '2026-05-21T09:58:44.922Z'
 updatedAt: '2026-05-21T09:58:44.922Z'

.brv/context-tree/docs/plans/lsp_registry_caplet_plan.md

@@ -0,0 +1,51 @@
+---
+title: LSP Registry Caplet Plan
+summary: A plan was created and saved for the LSP registry caplet, with execution options presented for either subagent-driven or inline implementation.
+tags: []
+related: []
+keywords: []
+createdAt: '2026-05-27T09:12:01.444Z'
+updatedAt: '2026-05-27T09:12:01.444Z'
+consolidated_at: '2026-05-27T10:03:41.871Z'
+consolidated_from: [{date: '2026-05-27T10:03:41.871Z', path: docs/plans/lsp_registry_caplet_plan.abstract.md, reason: 'These three files describe the same LSP registry caplet planning outcome with near-duplicate content in three formats (full entry, abstract, and overview). They are redundant and should be consolidated into the richest file while preserving the unique phrasing and metadata details from the other two.'}, {date: '2026-05-27T10:03:41.871Z', path: docs/plans/lsp_registry_caplet_plan.overview.md, reason: 'These three files describe the same LSP registry caplet planning outcome with near-duplicate content in three formats (full entry, abstract, and overview). They are redundant and should be consolidated into the richest file while preserving the unique phrasing and metadata details from the other two.'}]
+---
+## Reason
+Persist the plan completion outcome and user-visible decision point from the conversation
+
+## Raw Concept
+**Task:**
+Record the completion of the LSP registry caplet planning step
+
+**Changes:**
+- Created an implementation plan
+- Saved the plan to the plans directory
+- Presented two execution approaches
+
+**Files:**
+- docs/plans/2026-05-26-lsp-registry-caplet.md
+
+**Flow:**
+plan creation -> plan saved -> execution options presented
+
+**Timestamp:** 2026-05-27T09:11:49.118Z
+
+## Narrative
+### Structure
+This captures the outcome of a planning interaction for the LSP registry caplet.
+
+### Highlights
+The plan was completed and saved, then the user was offered a choice between subagent-driven execution and inline execution.
+
+## Facts
+- **plan_creation**: An implementation plan was created using the writing-plans skill. [project]
+- **plan_file**: The plan was saved to docs/plans/2026-05-26-lsp-registry-caplet.md. [project]
+- **execution_options**: Two execution options were presented: subagent-driven or inline execution. [project]
+
+## Overview
+This document records the outcome of a planning step for the LSP registry caplet.
+The plan was created using the writing-plans skill and saved to the project plans directory.
+A user-visible decision point was presented after planning: choose between subagent-driven execution or inline execution.
+The stated flow is: plan creation → plan saved → execution options presented.
+The plan file is identified as docs/plans/2026-05-26-lsp-registry-caplet.md.
+The document emphasizes persistence of the plan completion outcome and the interaction narrative, rather than implementation details.
+Notable entities/patterns: "LSP registry caplet," "subagent-driven" vs "inline" execution, and the structured metadata fields for reason, raw concept, narrative, and facts.

.brv/context-tree/docs/plans/pr_71_completion_fix_outcome.md

@@ -2,7 +2,7 @@
 title: PR 71 Completion Fix Outcome
 summary: Completion-related PR review fixes were implemented and verified with focused tests and pnpm verify, with no unresolved outside-diff review threads found.
 tags: []
-related: [docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+related: [docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: []
 createdAt: '2026-05-22T10:56:26.474Z'
 updatedAt: '2026-05-22T10:56:26.474Z'

.brv/context-tree/docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md

@@ -0,0 +1,23 @@
+---
+confidence: 0.94
+sources: [docs/_index.md, facts/_index.md, project/_index.md]
+synthesized_at: '2026-05-26T19:23:43.121Z'
+type: synthesis
+title: Release and completion work is governed by verification, not optimistic success signals
+summary: Planning and outcomes both emphasize gating behavior on explicit verification rather than workflow success alone.
+tags: [release, completion, verification, fallback, automation]
+related: [docs/plans/context.md, docs/plans/active_caplets_planning_documents.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md]
+keywords: [gated, publish, fallback, auth, discovery, candidate, workflow, verification]
+createdAt: '2026-05-26T19:23:43.121Z'
+updatedAt: '2026-05-26T19:23:43.121Z'
+---
+
+# Release and completion work is governed by verification, not optimistic success signals
+
+Across docs and facts/project, the repository repeatedly treats completion and release behavior as verification-gated: completion falls back to safe candidates when discovery/auth is blocked, and release publishing waits for a verified publish state rather than assuming workflow success means it is safe to publish.
+
+## Evidence
+
+- **docs**: The release pipeline publishes GHCR Docker images only after Changesets publishes npm packages, and Docker publication is gated on verified publish state rather than workflow success alone.
+- **facts**: Completion must not trigger interactive auth; if discovery is blocked, return stale cached results first, otherwise use static/config fallback only, and completion output remains candidate-only.
+- **project**: The completion contract says failures and timeouts must degrade to safe fallbacks, and hidden `__complete` uses `CapletsEngine.completeCliWords`.

.brv/context-tree/docs/plans/release-automation-is-gated-by-verified-publish-state-not-just-workflow-success.md

@@ -6,7 +6,7 @@ type: synthesis
 title: Release automation is gated by verified publish state, not just workflow success
 summary: The release pipeline only publishes Docker images after Changesets confirms a real npm publish, with validation checkpoints documented alongside it.
 tags: [release, docker, changesets, verification]
-related: [docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md]
+related: [docs/plans/context.md, docs/plans/completion_local_discovery_and_split_targets.md, docs/plans/completion_discovery_refactor_implementation_plan.md, docs/plans/active_caplets_planning_documents.md, docs/plans/docker_image_publishing_for_release_pipeline.md, docs/plans/pr_71_completion_fix_outcome.md, docs/plans/release-and-completion-work-is-governed-by-verification-not-optimistic-success-s.md]
 keywords: [publish, changesets, ghcr, docker, gating, workflow, validation, release]
 createdAt: '2026-05-21T23:23:26.220Z'
 updatedAt: '2026-05-21T23:23:26.220Z'

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

@@ -1,3 +1,6 @@
+---
+related: [facts/project/context.md]
+---
 # Topic: conventions
 
 ## Overview

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

@@ -2,7 +2,7 @@
 title: Task 3 Spec Review Fix
 summary: 'Task 3 fix: IPv6 loopback serve URLs now bind with ::1, CLI help text updated, focused tests passed, commit cdde479'
 tags: []
-related: [facts/conventions/task_5_regression_test_update.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md]
+related: [facts/conventions/task_5_regression_test_update.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md, facts/project/remote_control_review_outcome.md]
 keywords: []
 createdAt: '2026-05-20T12:56:28.017Z'
 updatedAt: '2026-05-20T12:56:28.017Z'

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

@@ -2,7 +2,7 @@
 title: Task 5 Regression Test Update
 summary: Added regression tests for remote add rejecting server-owned fields; tests passed and commit 089542d was created with a note about unrelated worktree changes.
 tags: []
-related: [facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md]
+related: [facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md, facts/project/remote_control_review_outcome.md]
 keywords: []
 createdAt: '2026-05-20T13:52:39.382Z'
 updatedAt: '2026-05-20T13:52:39.382Z'

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

@@ -2,7 +2,7 @@
 title: Task 6 Review Outcome
 summary: Task 6 review approved; nested engine request envelope validation is correct, old CAPLETS_REMOTE_* docs belong to Task 10, and source/test verification passed.
 tags: []
-related: [facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_5_regression_test_update.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md]
+related: [facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_5_regression_test_update.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_7_remote_mutation_routing_review.md, facts/conventions/task_9_remote_config_test_fix.md, facts/project/remote_control_review_outcome.md]
 keywords: []
 createdAt: '2026-05-20T14:17:40.238Z'
 updatedAt: '2026-05-20T14:17:40.238Z'

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

@@ -2,7 +2,7 @@
 title: Task 7 Remote Mutation Routing Review
 summary: Task 7 remote mutation routing review was approved; remote add/init/install flows, server-side boundary validation, response parsing, and redaction were verified, with tests and typecheck passing.
 tags: []
-related: [architecture/remote_control/context.md, architecture/remote_control/remote_control_api_shape.md, facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_5_regression_test_update.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_9_remote_config_test_fix.md]
+related: [architecture/remote_control/context.md, architecture/remote_control/remote_control_api_shape.md, facts/conventions/task_3_spec_review_fix.md, facts/conventions/task_5_regression_test_update.md, facts/conventions/task_6_review_outcome.md, facts/project/task_6_spec_review_after_envelope_fix.md, facts/conventions/task_7_review_outcome.md, facts/conventions/task_9_remote_config_test_fix.md, facts/project/remote_control_review_outcome.md]
 keywords: []
 createdAt: '2026-05-20T14:35:11.652Z'
 updatedAt: '2026-05-20T14:35:11.652Z'