Preserve no-AST adapter bindings
This commit is contained in:
parent
bb13258861
commit
6c05607b14
7 changed files with 209 additions and 13 deletions
|
|
@ -656,6 +656,25 @@ traversal.
|
|||
See [Incremental Adapter Indexing](INCREMENTAL_INDEXING.md) for the complete contract, cache
|
||||
invalidation rules, manual-application lifecycle, and lazy Logic boundary.
|
||||
|
||||
### Preserving an older non-AST adapter
|
||||
|
||||
Use `--no-ast` on the MCP binding when the project owner wants the existing adapter preserved
|
||||
without AST, Tree-sitter, compiler-AST, or function-Logic upgrades:
|
||||
|
||||
```bash
|
||||
docforge-mcp --project-root /absolute/project --no-ast
|
||||
```
|
||||
|
||||
For a project-owned server, pass `no_ast=True` to `create_project_server()` or
|
||||
`create_read_only_server()`. Bootstrap and contract responses then expose
|
||||
`mode=preserve-no-ast`. The Logic tool is blocked, and DocForge refuses to publish nonempty Logic
|
||||
projections.
|
||||
|
||||
This policy does not disable the Release 1 `load_projection()` path. It also permits incremental
|
||||
fingerprinting and caching when those mechanisms do not add AST analysis. The adapter can
|
||||
therefore benefit from current synchronization, proposals, application, rendering, and graph tools
|
||||
without a source-analysis rewrite.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### `stale_index` or `visualization_stale`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue