Merge adapter lifecycle safeguards
This commit is contained in:
commit
15a913003c
11 changed files with 541 additions and 11 deletions
|
|
@ -38,6 +38,11 @@ returns the complete fixed binding, active index path, proposal and application
|
|||
recommended workflow. `docforge_sync` exposes the same idempotent synchronization explicitly.
|
||||
Neither operation changes canonical sources.
|
||||
|
||||
Adapter-backed servers also validate their process-start implementation fingerprint before every
|
||||
tool. `adapter_restart_required` is stale but not synchronizable. Its remediation is
|
||||
`restart_project_server`; the current process does not reload project code, update Git staging, or
|
||||
continue with a newly changed validator.
|
||||
|
||||
The normal command binds the generic project loader. An explicit project integration may instead
|
||||
construct the same read-only surface from a validated `ProjectService` and project-owned context
|
||||
provider. This form cannot register proposal tools. Project discovery, session selection, family
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue