Require name-first extension preflight smoke
This commit is contained in:
@@ -776,7 +776,12 @@ Use `-SavedStateTable ConfigSave` or `-SavedStateTable ConfigCASSave` to choose
|
||||
which save-layer table is used by the copy plan and saved-state write smokes.
|
||||
Add `-RequireSelectorChainWritePlanComposition` when the selected base/object
|
||||
must have a saved-state stream that lets the selector-chain smoke compose a
|
||||
concrete read-only `metadata.write.plan`.
|
||||
concrete read-only `metadata.write.plan`. The same strict mode also requires
|
||||
the write-preflight smoke to discover an extension form by public
|
||||
`extension/ref/form/member` names, compose an allowed plan, and prove that the
|
||||
repository and support gates use the same resolved `extension:<GUID>` layer.
|
||||
Run that check directly with
|
||||
`scripts/smoke_1c_write_preflight.py --require-name-first-extension-form`.
|
||||
|
||||
To exercise the MCP proxy itself, switch transport and URL:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user