woods 2.0.0.beta3 → 2.0.0.beta4

data/plugin/skills/woods-diagnose/SKILL.md

@@ -16,7 +16,7 @@ This skill describes the Woods 2.x line; the authoritative minimum version lives
 
 ## Managed configuration availability
 
-`woods-agent-config` (#407) is unreleased after `2.0.0.beta2`. First record the
+`woods-agent-config` (#407) is available in Woods `2.0.0.beta3`. First record the
 installed version and test `bundle exec woods-agent-config --help` in the
 selected application bundle. When supported, use its saved setup/update/remove
 plan and explicit client/scope/root selection; apply the reviewed plan within
@@ -46,9 +46,22 @@ For versions documenting environment-boot snapshots, confirm that the command is
 `bundle exec rake woods:watch`, with no preceding `environment` task, and check
 whether boot inputs keep changing during initialization or catch-up.
 
+### Watch retains facts from an initializer deleted while stopped
+
+Record the installed revision. Unreleased after `2.0.0.beta3`, startup preserves
+registered deleted boot inputs as full-extraction obligations. On earlier builds,
+stop watch, run a successful full extraction in a fresh process, then restart
+standalone `woods:watch`. See the installed version's watch guide.
+
+### A cleaned index directory still exists
+
+Unreleased after `2.0.0.beta3`, `woods:clean` retains the output directory and
+hidden extraction guard for concurrent writer coordination. Verify published
+artifacts are gone; do not remove that guard while writers may be running.
+
 ### Watch misses edits under a shared directory alias
 
-Check the installed version: logical alias preservation (#445) is unreleased.
+Check the installed version: logical alias preservation (#445) is available in Woods `2.0.0.beta3`.
 Older polling/catch-up walkers could visit an irrelevant alias first and suppress
 `app/models` when both point to the same physical directory. Compare the logical
 path with the extraction input path; a running daemon alone does not prove coverage.
@@ -58,8 +71,8 @@ See the installed version's watch guide before assuming this behavior.
 
 ### Session trace reports ambiguous identity
 
-The `session_trace` `ambiguous_identity` error (#213) is unreleased after
-`2.0.0.beta2`; check the installed gem before expecting it. It names a dependency
+The `session_trace` `ambiguous_identity` error (#213) is available in Woods `2.0.0.beta3`;
+check the installed gem before expecting it. It names a dependency
 with multiple published extraction types, so no partial session context is
 returned. Use `depth: 0` for the timeline or inspect the named candidates with
 explicit `lookup` types. Do not choose one by index order or suggest that a full
@@ -72,7 +85,7 @@ For a `same-type identifier collision`, inspect both named source files and the
 Rails loader before suggesting source edits. Wrapper-nested class naming needs
 Zeitwerk mode and Zeitwerk >= 2.6.9; an older loader or classic mode can produce
 the collision even when the namespace wrappers are valid. The expanded error
-guidance (B-149) is unreleased after `2.0.0.beta2`; check the installed version
+guidance (B-149) is available in Woods `2.0.0.beta3`; check the installed version
 first. Follow the [loader compatibility guidance](https://github.com/lost-in-the/woods/blob/main/docs/UPGRADING_TO_2.md#check-the-loader-for-wrapper-nested-classes).
 
 ```bash
@@ -82,7 +95,7 @@ bin/rails woods:stats
 
 If missing or stale, run the narrow maintenance path justified by the evidence: `woods:incremental` for known file changes or `woods:extract` for first run, broad change, upgrade, or drift. Woods tasks understand `generation.json`; do not assume `manifest.json` is at the root.
 
-Semantic graph validation (#413) is unreleased after `2.0.0.beta2`; verify the
+Semantic graph validation (#413) is available in Woods `2.0.0.beta3`; verify the
 installed gem before expecting these errors. Supporting versions check typed
 unit identity, graph/index agreement and forward/reverse/file/type memberships
 within one pinned generation. Preserve the failing generation and exact error,
@@ -95,7 +108,7 @@ an external name from an internal unit omitted everywhere. Follow the
 
 If external targets such as `http_api` lose dependents after incremental
 extraction, check whether the installed Woods version includes B-193.
-The fix is unreleased; installing this plugin does not upgrade the gem.
+The fix is available in Woods `2.0.0.beta3`; installing this plugin does not upgrade the gem.
 Affected indexes need one full extraction after upgrading to a fixed version.
 Follow the [recovery guide](https://github.com/lost-in-the/woods/blob/main/docs/TROUBLESHOOTING.md#external-dependency-targets-lose-dependents-after-incremental-extraction).
 
@@ -107,7 +120,7 @@ Confirm the installed release and filesystem support retention locks before
 using the pinning examples; flat layouts need writers stopped for a consistent copy.
 
 A host reader can report a container daemon dead because foreign-host records
-are rejected by default. Foreign heartbeat trust (#321) is unreleased: first
+are rejected by default. Foreign heartbeat trust (#321) is available in Woods `2.0.0.beta3`: first
 check the installed Woods version and that version's release notes. Only for a
 supporting version, offer `WOODS_WATCH_TRUST_FOREIGN_HOST=1` in every relevant
 task/MCP reader and follow [cross-host liveness](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md#cross-host-liveness).
@@ -115,12 +128,18 @@ Fresh `degraded` still means incremental work is needed; a fresh `running`
 record can outlive a crashed foreign daemon by up to 15 minutes. Older versions
 need their status check run in the daemon's own container.
 
-Writer-version provenance (#323) is unreleased: verify the installed gem version's
-release notes before expecting it. If `index.woods_version` exists, compare it
+Writer-version provenance (#323) is available in Woods `2.0.0.beta3`: verify the installed
+gem version's release notes before expecting it. If `index.woods_version` exists, compare it
 with `server.version`; missing/null is unknown, not a failure. A validator
 major-version warning calls for full extraction and upgrade review, while a match
 does not certify retained units were migrated. See [writer provenance](https://github.com/lost-in-the/woods/blob/main/docs/PUBLISHED_INDEX.md#manifest-writer-provenance).
 
+Unreleased after `2.0.0.beta3`: incremental/refresh handled source errors keep
+the previous generation active and leave watch batches pending. Repair the
+logged source error and retry the complete batch; see
+[handled source errors](https://github.com/lost-in-the/woods/blob/main/docs/INCREMENTAL_EXTRACTION.md#handled-source-errors-and-retry).
+Check the installed revision before relying on this behavior.
+
 If a one-shot extraction raises `Could not publish generation`, the candidate
 payload was written but never made visible; readers still serve the previous
 complete generation. Fix the named filesystem, permission, space, or mount
@@ -139,12 +158,12 @@ tracks current source.
 For volatile-dependency reports dominated by one target, compare the full
 `stats.volatile_dependency_count` with the persisted array and use the
 [ratio tuning guidance](https://github.com/lost-in-the/woods/blob/main/docs/CONFIGURATION_REFERENCE.md#pipeline-options).
-The optional per-target cap (B-188) is unreleased after 2.0.0.beta2; check the
+The optional per-target cap (B-188) is available in Woods `2.0.0.beta3`; check the
 installed gem before suggesting `volatile_dependency_limit_per_target`.
 Re-extract to publish configuration changes; the report remains informational.
 
 For a shallow-checkout git-enrichment warning, the shallow guard (B-189) is
-unreleased after `2.0.0.beta2`; check the installed version first. Fetch complete
+available in Woods `2.0.0.beta3`; check the installed version first. Fetch complete
 history with `git fetch --unshallow` or `actions/checkout` `fetch-depth: 0`, then
 run full extraction. Depth two only enables a two-commit diff; it does not
 restore complete churn history. See the
@@ -152,7 +171,7 @@ restore complete churn history. See the
 
 For `Git enrichment omitted: history could not be read completely`, first check
 whether the installed Woods release documents the new streamed-history policy;
-it is unreleased after 2.0.0.beta2. Supporting versions require Git 2.31 or newer.
+it is available in Woods `2.0.0.beta3`. Supporting versions require Git 2.31 or newer.
 Check `git --version` in the extraction container and repository/object-store
 access with its `WOODS_GIT_DIR` setting. A failed history stream is discarded;
 repair git access and run full extraction to refresh retained metadata. See the
@@ -162,14 +181,14 @@ After a bundle change or removal of a dynamically defined job, incremental
 extraction can retain stale runtime units. Use a fresh process with the updated
 bundle for full extraction, then validate. For missing external gem paths,
 first distinguish an upgraded bundle from a reader on a different host/mount.
-The more explicit `woods:validate` bundle-update remedy (B-166) is unreleased
-after `2.0.0.beta2`; the full-extraction recovery works on older versions too.
+The more explicit `woods:validate` bundle-update remedy (B-166) is available in Woods
+`2.0.0.beta3`; the full-extraction recovery works on older versions too.
 See [runtime removals and bundle updates](https://github.com/lost-in-the/woods/blob/main/docs/INCREMENTAL_EXTRACTION.md#runtime-removals-and-bundle-updates).
 
 ### Export identity checks
 
-For Notion or Unblocked exports, typed selection checks (#213) are unreleased
-after `2.0.0.beta2`; check the installed gem before expecting them. A missing or
+For Notion or Unblocked exports, typed selection checks (#213) are available in Woods
+`2.0.0.beta3`; check the installed gem before expecting them. A missing or
 mismatched export identity calls for index validation and a fresh extraction,
 not a force flag. An `ambiguous export URI` means two types share an identifier
 and source file: preserve existing documents and report the collision; do not
@@ -186,26 +205,35 @@ Compare the client config with the exact command, absolute `cwd`, bundle, and in
 bundle exec woods-mcp-start ./tmp/woods
 ```
 
+If startup says `Could not resolve a published Woods index` (unreleased after
+`2.0.0.beta3`) or names a missing `manifest.json` on older versions, first check
+the selected index path: an atomic index uses `generation.json` to locate its
+payload manifest. The new headline does not change index validation or recovery.
+Point at an existing index before suggesting a new extraction. Prefer the
+explicit path above; `WOODS_DIR` is also supported. An unreleased change after
+`2.0.0.beta3` adds `WOODS_OUTPUT` after those two choices, so verify the installed
+version's configuration guide before relying on that fallback.
+
 Then reconnect through the MCP client and call `woods_status`. Use client-native tool inspection after initialization. Expect 14 packaged Index tools, not all conditional schemas.
 
 For Docker-only bundles, test the configured container command instead, for example `docker compose exec -T app bundle exec woods-mcp /app/tmp/woods`. Use the container path for a container process and a host path only for a host process.
 
 For corrupt pipeline cooldown state, first confirm this is a custom server
 with `pipeline_repair` registered; packaged `woods-mcp` does not wire it.
-Recovery through `reset_cooldowns` (B-159) is unreleased after `2.0.0.beta2`.
+Recovery through `reset_cooldowns` (B-159) is available in Woods `2.0.0.beta3`.
 Check the installed version before attempting it and follow the
 [corrupt cooldown recovery guide](https://github.com/lost-in-the/woods/blob/main/docs/TROUBLESHOOTING.md#corrupt-pipeline-cooldown-state).
 
 ## Deferred refresh hooks
 
-Expanded hook coverage and `woods:hook_refresh` (#408) are unreleased after
-Woods 2.0.0.beta2. Verify the installed task through the configured host/container
+Expanded hook coverage and `woods:hook_refresh` (#408) are available in Woods
+`2.0.0.beta3`. Verify the installed task through the configured host/container
 command before diagnosing this plugin's queue. Read `<output>/hook.log` and
 `hook-pending/`; status 75 means an active daemon deferred work, not that it was
 consumed. Fix task availability, boot/publication failures or a stalled command,
 then retry with the same output and command prefix. Preserve pending events.
 For mkdir fallback locks, inspect the recorded owner PID before manual removal.
-The concurrent dead-owner recovery fix is unreleased after plugin 2.3.35.
+The concurrent dead-owner recovery fix is included in plugin `2.3.36`.
 If competing hooks leave an empty lock without a drain, preserve the queued
 events and follow the canonical recovery guide below.
 A Docker timeout does not prove the application process stopped. Prefer a
@@ -214,8 +242,8 @@ resident watcher for sustained edits and follow the
 
 ## Partial dependency answers
 
-Traversal budgets (`max_nodes`/`max_edges`, #311) are unreleased in Woods
-2.0.0.beta2. Check the installed gem version and connected tool schema before
+Traversal budgets (`max_nodes`/`max_edges`, #311) are available in Woods `2.0.0.beta3`.
+Check the installed gem version and connected tool schema before
 using them; installing this plugin does not upgrade the gem. On a supporting
 server, `partial`/`partial_reason` means the walk stopped early, independently
 of page truncation. Do not claim an exhaustive blast radius or treat empty
@@ -225,7 +253,7 @@ paging alone only visits the discovered prefix. See the
 
 ## 4. Check semantic retrieval
 
-Configured retrieval defaults (#446) are unreleased after beta2. For an installed
+Configured retrieval defaults (#446) are available in Woods `2.0.0.beta3`. For an installed
 version that supports them, an omitted tool budget uses the serving retriever's
 configured default; an explicit budget overrides it. Standalone MCP does not
 inherit the host initializer's token setting from the embedding snapshot.
@@ -233,7 +261,7 @@ Do not tune relevance with similarity_threshold: it is inert and deprecated.
 Use query/type/scope selection and inspect ranking evidence instead. See
 [retrieval tuning](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#tuning).
 
-Native embedding completeness checks (#442/#444) are unreleased after beta2;
+Native embedding completeness checks (#442/#444) are available in Woods `2.0.0.beta3`;
 confirm the installed version first. If embedding reports `Embedding input
 incomplete`, repair the named published extraction artifact or rebuild extraction
 before retrying. Do not use `WOODS_ALLOW_PURGE=1` to bypass an integrity failure;
@@ -241,7 +269,7 @@ it only permits intentional mass deletion. Source-empty units deliberately retai
 metadata without vectors. See the canonical
 [input-integrity guide](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#input-integrity-and-source-empty-units).
 
-Only diagnose this layer when structural tools work and `codebase_retrieve` fails. First check `woods_status.retriever.mode`. For lexical mode, validate the published extraction index and follow the capability check below. For semantic mode, check the configured provider/model/vector store, provider reachability, and whether `woods:embed` completed.
+Only diagnose this layer when structural tools work and `codebase_retrieve` fails. If a no-provider message recommends only embeddings or `search`, check the lexical capability below: beta3 supports explicit `WOODS_RETRIEVAL_MODE=lexical` even though that error omits it. Put the setting in the MCP process environment and restart; never silently change retrieval modes. First check `woods_status.retriever.mode`. For lexical mode, validate the published extraction index and follow the capability check below. For semantic mode, check the configured provider/model/vector store, provider reachability, and whether `woods:embed` completed.
 
 - OpenAI: verify the key exists without printing it.
 - Ollama: verify the service and configured model locally.
@@ -252,7 +280,7 @@ Only diagnose this layer when structural tools work and `codebase_retrieve` fail
 For metadata appearing in another index or worktree, compare `WOODS_OUTPUT`,
 `config.output_dir`, and any explicit `metadata_store_options[:database]`.
 The default SQLite path following `WOODS_OUTPUT` during embedding (B-156) is
-unreleased after `2.0.0.beta2`; check the installed version before relying on it.
+available in Woods `2.0.0.beta3`; check the installed version before relying on it.
 An explicit database path still wins. See the
 [SQLite path contract](https://github.com/lost-in-the/woods/blob/main/docs/CONFIGURATION_REFERENCE.md#sqlite-metadata)
 for isolation and upgrade steps.
@@ -261,7 +289,7 @@ for isolation and upgrade steps.
 
 For repeated missing-token boot warnings on a stdio-only host, check whether
 its installed version supports `console_mcp_http_enabled = false` before
-suggesting it; this option is unreleased in Woods 2.0.0.beta2. The default
+suggesting it; this option is available in Woods `2.0.0.beta3`. The default
 preserves HTTP enablement, so selecting stdio as a client alone does not
 suppress HTTP token validation. Never disable authentication on an HTTP
 endpoint to silence this warning.
@@ -270,6 +298,8 @@ Console failures are live Rails/config/security failures, not Index failures. Ve
 
 For MySQL SQL refusals, inspect the executing session's `sql_mode` and the installed version's Console guide. Do not change quote modes to bypass a security refusal.
 
+For SQLite SQL refusals on `2.0.0.beta4` or a reviewed revision containing its Console corrections, consult the installed Console guide for supported identifier and table-reference syntax. Simplify the query to supported syntax; never relax the blocked-table or function policy. These builds also check resolved default scopes and scan normalized response values. Confirm a patched gem is published before recommending it, and check the installed version’s canonical Console guide; do not infer release availability from this plugin.
+
 Nine tools are normal. Eleven appear only with `console_embedded_read_tools`. Do not chase Tier 2/3 or `console_eval`; they do not register in supported packaged modes. Never work around redaction, credential scanning, SQL validation, or a block.
 
 ## Report
@@ -280,7 +310,7 @@ Canonical guide: [TROUBLESHOOTING.md](https://github.com/lost-in-the/woods/blob/
 
 ## Lexical retrieval capability check
 
-This is a development capability. Before proposing it, verify the installed gem
+Lexical retrieval is available from `2.0.0.beta3`. Before proposing it, verify the installed gem
 exposes `Woods::Configuration#retrieval_mode` and its matching guide documents
 `WOODS_RETRIEVAL_MODE`. Keep the installed-version preflight; do not infer support
 from the plugin version or an unreleased checkout.
@@ -303,7 +333,7 @@ query. Scoping can hide relevant cross-boundary relationships, so broaden the
 request deliberately when the task needs them. See the
 [scope contract](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#explicit-package-and-source-path-scopes).
 
-## Source-content freshness (unreleased #405)
+## Source-content freshness (Woods 2.0.0.beta3; #405)
 
 Check installed-version support before using `woods-extract` or the optional
 `woods_status.source_check` argument. With support, inspect
@@ -326,7 +356,7 @@ coordinates are not physical file offsets; unknown generation remains unknown.
 Keep full-source access available. See the canonical
 [evidence contract](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#compact-published-evidence-and-api-outlines).
 
-## Explicit edit adapters (unreleased #409)
+## Explicit edit adapters (Woods 2.0.0.beta3; #409)
 
 Check the installed gem exposes `woods:hook_refresh` before enabling hooks.
 Claude's registered wrapper covers one documented edit path; OpenCode 1.18.27
@@ -341,7 +371,7 @@ user's setup request. Follow [client hooks](https://github.com/lost-in-the/woods
 ## Optional context hints
 
 Check installed `bundle exec woods-hook-context --help` before enabling
-`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is unreleased after beta2 and the
+`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is available in Woods `2.0.0.beta3` and the
 plugin does not upgrade the gem. Context and refresh opt-ins are independent;
 `WOODS_HOOKS_DISABLED=1` disables both. Native Claude context is synchronous and
 bounded, with served-generation and pre-refresh/unknown labels. Verify candidate
@@ -352,7 +382,8 @@ for output/time limits, container root mapping and emitted-hint suppression.
 
 ### Obsidian destination conflicts
 
-Destination ownership preflight (#441) is unreleased; first check the installed Woods version and
+Destination ownership preflight (#441) is available in Woods `2.0.0.beta3`; first check
+the installed Woods version and
 its matching guide. On versions with this check, `refusing <path>: unmanaged or modified destination`
 means the export preserved a conflicting note, setting, or sidecar and skipped the stale-note sweep.
 A `.woods-vault` sentinel or force-purge flag does not authorize overwriting it. Inspect and back up

data/plugin/skills/woods-investigate/SKILL.md

@@ -10,7 +10,7 @@ Woods is runtime evidence: resolved routes, schema, associations, callbacks, inl
 ## Preflight
 
 Supporting servers include concise MCP initialization/discovery guidance without
-this plugin. That feature (#402) is unreleased after `2.0.0.beta2`; check the
+this plugin. That feature (#402) is available in Woods `2.0.0.beta3`; check the
 installed server version, and do not require it from protocol `2024-11-05`.
 Follow the [agent guide](https://github.com/lost-in-the/woods/blob/main/docs/AGENT_GUIDE.md)
 when instructions are absent. A registered tool does not establish retrieval
@@ -41,7 +41,7 @@ The normal packaged Index Server registers 14 tools; conditional schemas registe
 
 ## Partial search answers
 
-Search completeness (#410) is unreleased after `2.0.0.beta2`. Verify the installed
+Search completeness (#410) is available in Woods `2.0.0.beta3`. Verify the installed
 server version and response before relying on it; this plugin does not upgrade
 the gem. On supporting versions, `result_count` counts returned rows, while
 `completeness.reason: exhausted` establishes an exact total for the requested
@@ -52,10 +52,33 @@ Artifact errors have unknown completeness. Missing metadata on older servers,
 a full page, and an empty partial result never establish exhaustive absence.
 See the [search contract](https://github.com/lost-in-the/woods/blob/main/docs/MCP_SERVERS.md#search-completeness).
 
+## Graph coverage
+
+Dependency tools report published relationships, not exhaustive source-reference
+or call coverage. Selective method-body scanning can miss references to generic
+PORO and library targets. No dependents or test-only dependents do not establish
+absence of production callers; check source before making that claim.
+
+The response `graph_coverage` notice, `total_is_exact` field, and human label
+`witness types unambiguous` (#470/#471) are unreleased after Woods `2.0.0.beta3`.
+Verify the installed server version and actual response fields; this plugin does
+not add them. Apply these limits to older servers even without the notice.
+Supporting stdio and HTTP servers expose the paginated traversal payload in
+`structuredContent.data` independently of the text renderer (#481, also
+unreleased after `2.0.0.beta3`). Check the installed response; older default
+responses may carry only text. Do not pass an unsupported `format` argument.
+
+`total_is_exact: false` means a budget-limited prefix; a true value describes only
+the requested root, depth, filters and published generation. Pagination alone
+does not change exactness. On older responses inspect `partial` directly.
+Treat partial `nodes_total` as a root-inclusive lower bound, including on the
+last page, an empty page or an unpaged answer. See the
+[coverage contract](https://github.com/lost-in-the/woods/blob/main/docs/MCP_SERVERS.md#dependency-graph-coverage).
+
 ## Partial dependency answers
 
-Traversal budgets (`max_nodes`/`max_edges`, #311) are unreleased in Woods
-2.0.0.beta2. Check the installed gem version and connected tool schema before
+Traversal budgets (`max_nodes`/`max_edges`, #311) are available in Woods `2.0.0.beta3`.
+Check the installed gem version and connected tool schema before
 using them; installing this plugin does not upgrade the gem. On a supporting
 server, `partial`/`partial_reason` means the walk stopped early, independently
 of page truncation. Do not claim an exhaustive blast radius or treat empty
@@ -65,25 +88,38 @@ paging alone only visits the discovered prefix. See the
 
 ## Explain recorded relationships
 
-`explain: true` on `dependencies`/`dependents` (#414) is unreleased after
-2.0.0.beta2. Verify the installed gem and connected tool schema before using it;
+`explain: true` on `dependencies`/`dependents` (#414) is available in Woods `2.0.0.beta3`.
+Verify the installed gem and connected tool schema before using it;
 installing this plugin does not add server capabilities. Supporting servers
 preserve original source-to-target direction and labels in both traversal
 modes. Follow shared `parent`/`edge_id` witnesses, distinguish direct records
 from transitive inferred impact, and treat `context: true` ancestors as page
 context. Null attributes and candidate type ambiguities remain unknown;
-`typed_path_complete: false` never establishes a uniquely typed path. Budget
+`typed_path_complete: false` never establishes a uniquely typed path; true means
+only that witness identities have unambiguous types, not complete source coverage.
+Budget
 cutoffs still apply. Verify important conclusions in source and tests, since
 recorded reachability does not establish observed execution. See the
 [explanation contract](https://github.com/lost-in-the/woods/blob/main/docs/MCP_SERVERS.md#traversal-explanations).
 
+## Graph-analysis pages
+
+Pass explicit `limit` and `offset` when paging `graph_analysis`. Enforcing the
+advertised default of 20 rows per section and preserving total/offset on last
+and empty pages (#519) are unreleased after `2.0.0.beta3`; check the installed
+response rather than inferring support from the plugin version. On supporting
+servers, read `<section>_total` and `<section>_offset` in JSON, or the human
+pagination notice. An empty later page does not mean no findings. Totals count
+the published report array, which may already be bounded during extraction.
+See the [page contract](https://github.com/lost-in-the/woods/blob/main/docs/MCP_SERVERS.md#graph-analysis-pages).
+
 ## Volatile dependency reports
 
 Read `stats.volatile_dependency_count` before judging the top-20 array: it
 counts all qualifying edges. A frequently changed dependency can occupy most
 rows. Use the installed version's ratio tuning guidance; the optional
-`volatile_dependency_limit_per_target` setting (B-188) is unreleased after
-2.0.0.beta2, so verify gem support before recommending it. Supporting versions
+`volatile_dependency_limit_per_target` setting (B-188) is available in Woods
+`2.0.0.beta3`, so verify gem support before recommending it. Supporting versions
 can cap each typed target before selecting the global top 20 and expose the
 cap plus `volatile_dependency_reported_count` in stats. Re-extract after
 configuration changes. Treat the report as candidates for source review, never
@@ -104,8 +140,11 @@ exposes `Woods::Configuration#retrieval_mode` and its matching guide documents
 from the plugin version or an unreleased checkout.
 
 When status reports lexical mode, use the matching fields/terms as discovery
-evidence and verify key units with `lookup`. The ranked top 20 is not exhaustive;
-no lexical match does not establish absence. Continue using `budget`, not `limit`.
+evidence and verify key units with `lookup`. At most 20 eligible matching
+candidates are considered; fewer source entries may fit the budget. This is not
+exhaustive, and no lexical match does not establish absence. When the installed
+server reports considered/included counts, compare them; older versions may
+only describe the shortlist limit. Continue using `budget`, not `limit`.
 See the [retrieval guide](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#embedding-free-lexical-retrieval)
 for the supported contract, checked against the installed gem version.
 
@@ -135,7 +174,7 @@ Keep full-source access available. See the canonical
 ## Optional context hints
 
 Check installed `bundle exec woods-hook-context --help` before enabling
-`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is unreleased after beta2 and the
+`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is available in Woods `2.0.0.beta3` and the
 plugin does not upgrade the gem. Context and refresh opt-ins are independent;
 `WOODS_HOOKS_DISABLED=1` disables both. Native Claude context is synchronous and
 bounded, with served-generation and pre-refresh/unknown labels. Verify candidate

data/plugin/skills/woods-mcp-config/SKILL.md

@@ -7,7 +7,7 @@ description: Configure Woods MCP connections with the exact client JSON shapes a
 
 ## Managed configuration availability
 
-`woods-agent-config` (#407) is unreleased after `2.0.0.beta2`. First record the
+`woods-agent-config` (#407) is available in Woods `2.0.0.beta3`. First record the
 installed version and test `bundle exec woods-agent-config --help` in the
 selected application bundle. When supported, use its saved setup/update/remove
 plan and explicit client/scope/root selection; apply the reviewed plan within
@@ -30,7 +30,7 @@ This skill describes the Woods 2.x line; the authoritative minimum version lives
 
 Default to Index-only. It reads generated code context and exposes 14 tools. Console MCP boots Rails and reads live data; ask before enabling it.
 
-Initialization guidance (#402) is unreleased after `2.0.0.beta2`; check the
+Initialization guidance (#402) is available in Woods `2.0.0.beta3`; check the
 installed gem before expecting MCP `instructions`. Supporting servers provide
 a short workflow through initialization or modern discovery; protocol
 `2024-11-05` omits it. Missing instructions alone are not a connection failure.
@@ -55,8 +55,8 @@ when unavailable. See the
 
 Use this shape for any stdio-capable MCP client, adapted to the client's configuration location. `woods-mcp-start` validates and launches; it does not install or auto-restart.
 
-Writer-version provenance (#323) is unreleased; check the installed gem version's
-release notes before expecting `index.woods_version` in `woods_status`. It reports
+Writer-version provenance (#323) is available in Woods `2.0.0.beta3`; check the installed
+gem version's release notes before expecting `index.woods_version` in `woods_status`. It reports
 the last manifest publisher, independently of `server.version`. Treat missing/null
 as unknown and see [writer provenance](https://github.com/lost-in-the/woods/blob/main/docs/PUBLISHED_INDEX.md#manifest-writer-provenance).
 
@@ -74,12 +74,12 @@ When Woods is installed only in Docker, prefer running the server through the ap
 }
 ```
 
-Use a host-side bundle only after verifying Ruby, the application bundle, and the index are available on the host. Always pass the path visible to the process that runs `woods-mcp`.
+Use a host-side bundle only after verifying Ruby, the application bundle, and the index are available on the host. Always pass the path visible to the process that runs `woods-mcp`. Prefer an explicit index path on all versions. After `2.0.0.beta3`, an unreleased change adds `WOODS_OUTPUT` as a fallback after the positional path and `WOODS_DIR`; check the installed version's configuration guide before relying on it. `woods-mcp-start` still refuses a missing path rather than selecting its working directory.
 
 A read-only index mount is sufficient for structural tools. The `reload` tool for in-memory semantic retrieval also takes Woods' shared on-disk writer lock, so the MCP process needs write access to the index directory. Without it, reload returns a typed degraded error and keeps serving the previous aligned generation. Either grant that access or restart the MCP process after publishing a new embedded index.
 
 For host MCP reading a container daemon's shared index, foreign heartbeat trust
-(#321) is unreleased. Verify the installed gem version's release notes before
+(#321) is available in Woods `2.0.0.beta3`. Verify the installed gem version's release notes before
 offering `WOODS_WATCH_TRUST_FOREIGN_HOST=1` in the MCP environment. It makes
 `woods_status.watch.alive` use the same bounded freshness policy as task readers;
 see [cross-host liveness](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md#cross-host-liveness).
@@ -97,8 +97,8 @@ end
 
 The token authenticates HTTP requests and is not sent by a stdio client.
 Before suggesting `console_mcp_http_enabled = false`, verify that the installed
-version supports it: the option is unreleased in Woods 2.0.0.beta2. Supported
-stdio-only hosts can set it to `false` and omit the HTTP token; existing
+version supports it: the option is available in Woods `2.0.0.beta3`. Supported
+stdio-only hosts can set it to `false` and omit the HTTP token; older
 versions require the token at production boot whenever Console is enabled.
 For HTTP, retain a strong token, allowed origins and TLS. Use installed-version
 tagged documentation; the [canonical Console guide](https://github.com/lost-in-the/woods/blob/main/docs/CONSOLE_MCP_SETUP.md)
@@ -142,14 +142,14 @@ Canonical guide: [MCP_SERVERS.md](https://github.com/lost-in-the/woods/blob/main
 
 ## Lexical retrieval capability check
 
-This is a development capability. Before proposing it, verify the installed gem
+Lexical retrieval is available from `2.0.0.beta3`. Before proposing it, verify the installed gem
 exposes `Woods::Configuration#retrieval_mode` and its matching guide documents
 `WOODS_RETRIEVAL_MODE`. Keep the installed-version preflight; do not infer support
 from the plugin version or an unreleased checkout.
 
 When supported, put `WOODS_RETRIEVAL_MODE=lexical` in the environment of the
 process launching Index MCP (stdio or HTTP). A Rails initializer alone is not
-loaded by that process. Confirm `woods_status.retriever.mode` reports `lexical`.
+loaded by that process. Restart the MCP server after changing its environment, then confirm `woods_status.retriever.mode` reports `lexical`. A beta3 no-provider error may omit this option; it does not mean embeddings are required for explicit lexical mode.
 See the [retrieval guide](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#embedding-free-lexical-retrieval)
 for the supported contract, checked against the installed gem version.
 
@@ -165,7 +165,7 @@ query. Scoping can hide relevant cross-boundary relationships, so broaden the
 request deliberately when the task needs them. See the
 [scope contract](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#explicit-package-and-source-path-scopes).
 
-## Source-content freshness (unreleased #405)
+## Source-content freshness (Woods 2.0.0.beta3; #405)
 
 Check installed-version support before using `woods-extract` or the optional
 `woods_status.source_check` argument. With support, inspect

data/plugin/skills/woods-setup/SKILL.md

@@ -9,7 +9,7 @@ Install a structural Index Server first. Embeddings and Console MCP are separate
 
 ## Managed configuration availability
 
-`woods-agent-config` (#407) is unreleased after `2.0.0.beta2`. First record the
+`woods-agent-config` (#407) is available in Woods `2.0.0.beta3`. First record the
 installed version and test `bundle exec woods-agent-config --help` in the
 selected application bundle. When supported, use its saved setup/update/remove
 plan and explicit client/scope/root selection; apply the reviewed plan within
@@ -74,8 +74,8 @@ bin/rails woods:stats
 
 If extraction fails, reproduce Rails boot and eager loading first. Do not inspect internal payload files when Woods tasks provide the check.
 
-Writer-version provenance (#323) is unreleased; check the installed gem version's
-release notes before expecting `woods_status.index.woods_version`. When present,
+Writer-version provenance (#323) is available in Woods `2.0.0.beta3`; check the installed
+gem version's release notes before expecting `woods_status.index.woods_version`. When present,
 it names the last manifest publisher; `server.version` names the MCP reader.
 Missing/null means unknown. A matching version after an incremental run never
 replaces a required full upgrade extraction. See [writer provenance](https://github.com/lost-in-the/woods/blob/main/docs/PUBLISHED_INDEX.md#manifest-writer-provenance).
@@ -112,7 +112,8 @@ Reconnect and call `woods_status`, then `search`, `lookup`, and `dependents` for
 
 Offer to add `bundle exec rake woods:watch` to the existing development process manager. When authorized, it catches up missed changes and automatically maintains the structural index; the Index Server refreshes on its next call, so ordinary edits need no manual extraction or MCP restart. Use the standalone watch command; do not prepend the `environment` task. Check the installed version's watch guide before relying on automatic startup reconciliation. State that live boot-captured changes require supervisor restart, Docker may need `WOODS_WATCH_POLL=1`, and semantic vectors still need `woods:embed_incremental`.
 
-Foreign-host heartbeat trust (`WOODS_WATCH_TRUST_FOREIGN_HOST=1`, #321) is unreleased.
+Foreign-host heartbeat trust (`WOODS_WATCH_TRUST_FOREIGN_HOST=1`, #321) is available in
+Woods `2.0.0.beta3`.
 Check the installed gem version against its release notes before offering it;
 do not assume installing this plugin upgrades the gem. For a supporting version,
 follow [cross-host liveness](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md#cross-host-liveness)
@@ -120,14 +121,14 @@ and set the opt-in in each task/MCP reader of a shared container index. Explain
 the 15-minute crash-detection delay and preserve one supervisor per daemon.
 
 For slow bind mounts, check whether the installed version documents
-`WOODS_WATCH_POLL_INTERVAL` before suggesting it; this setting is unreleased
-in Woods 2.0.0.beta2. Where supported, a positive value such as `2.5` reduces
+`WOODS_WATCH_POLL_INTERVAL` before suggesting it; this setting is available in Woods
+`2.0.0.beta3`. Where supported, a positive value such as `2.5` reduces
 polling frequency at the cost of detection latency. Use the installed preflight version to select tagged documentation; the
 [canonical watch guide](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md)
 tracks current source and may describe unreleased behavior.
 
 The plugin ships opt-in refresh and session-start hooks. The expanded refresh
-contract (#408) is unreleased after Woods 2.0.0.beta2: first verify the installed
+contract (#408) is available in Woods `2.0.0.beta3`: first verify the installed
 gem exposes `woods:hook_refresh` through the actual application command. Do not
 infer support from the plugin version. With support, edits to standard services,
 controllers, jobs, views, concerns, locales, supported tests/lib files, routes,
@@ -146,7 +147,7 @@ The refresh worker's deadline starts after the complete event input has been
 collected, validated, and queued; it does not bound input collection. It includes
 subsequent batches, but cancelling Docker exec does not prove its container
 process stopped. See the [hook deadline and retry contract](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md#hooks-for-agent-sessions).
-Source freshness (#405) is unreleased after beta2: verify the installed command
+Source freshness (#405) is available in Woods `2.0.0.beta3`: verify the installed command
 exposes `woods:source_status` and `woods-extract` before using it. Supporting
 SessionStart hooks check source content and report missing/failed evidence as
 unknown; silence does not acknowledge queued refresh work. Follow the [hook guide](https://github.com/lost-in-the/woods/blob/main/docs/WATCH_DAEMON.md#hooks-for-agent-sessions)
@@ -154,6 +155,8 @@ for transport, retry and custom-root limits.
 
 ## Ask before expanding scope
 
+For pgvector, match the provider output and migration dimensions within 1–2,000. Default `text-embedding-3-large` output (3,072) needs an explicit smaller provider width or another backend; never silently truncate vectors. Early adapter/generator refusal is unreleased after `2.0.0.beta3`, so check the installed revision. See the [dimension contract](https://github.com/lost-in-the/woods/blob/main/docs/CONFIGURATION_REFERENCE.md#pgvector-postgresql).
+
 Require explicit approval before adding Ollama/OpenAI, pgvector/Qdrant, secrets, Console MCP/live-data access, HTTP transport, or purge overrides. The `:local` preset avoids cloud keys but requires the `sqlite3` gem, an installed/running Ollama service, and a pulled model (`ollama pull nomic-embed-text` by default); `:shared_filesystem` avoids sqlite3 but still uses Ollama. Recommend `gem "tokenizers", "~> 0.5"` for exact counting on dense Ruby source, while stating that it is optional.
 
 ## Handoff
@@ -164,7 +167,7 @@ Canonical runbook: [AGENT_SETUP.md](https://github.com/lost-in-the/woods/blob/ma
 
 ## Lexical retrieval capability check
 
-This is a development capability. Before proposing it, verify the installed gem
+Lexical retrieval is available from `2.0.0.beta3`. Before proposing it, verify the installed gem
 exposes `Woods::Configuration#retrieval_mode` and its matching guide documents
 `WOODS_RETRIEVAL_MODE`. Keep the installed-version preflight; do not infer support
 from the plugin version or an unreleased checkout.
@@ -175,7 +178,7 @@ remains the default; setting up embeddings is a separate choice.
 See the [retrieval guide](https://github.com/lost-in-the/woods/blob/main/docs/RETRIEVAL_GUIDE.md#embedding-free-lexical-retrieval)
 for the supported contract, checked against the installed gem version.
 
-## Explicit edit adapters (unreleased #409)
+## Explicit edit adapters (Woods 2.0.0.beta3; #409)
 
 Check the installed gem exposes `woods:hook_refresh` before enabling hooks.
 Claude's registered wrapper covers one documented edit path; OpenCode 1.18.27
@@ -190,7 +193,7 @@ user's setup request. Follow [client hooks](https://github.com/lost-in-the/woods
 ## Optional context hints
 
 Check installed `bundle exec woods-hook-context --help` before enabling
-`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is unreleased after beta2 and the
+`WOODS_HOOK_CONTEXT_ENABLED=1`; this capability is available in Woods `2.0.0.beta3` and the
 plugin does not upgrade the gem. Context and refresh opt-ins are independent;
 `WOODS_HOOKS_DISABLED=1` disables both. Native Claude context is synchronous and
 bounded, with served-generation and pre-refresh/unknown labels. Verify candidate