docs(core): regenerate the cordis catalog for the recompose binding contract

The re-link now runs through the mount-time binding, and the method's
JSDoc says so; the generated core surface and the runtime API catalog
follow it.
This commit is contained in:
Yichen Jiang
2026-08-10 11:42:06 +08:00
parent c9eee0302d
commit 0d9b97bf7b
4 changed files with 11 additions and 5 deletions

View File

@@ -444,7 +444,10 @@ serviceFor<K extends string & keyof Context>(agent: { ctx: Context }, name: K):
* and permanent, so the old composition stays for its other agents and the
* new one is ensured BEFORE the link moves. An unknown or unusable preset
* therefore throws with the agent exactly as it was — there is no torn-down
* state to restore.
* state to restore. The re-link runs through the binding this roster kept
* from the agent's mount — dsh-scope's only re-link authority. An agent
* that never composed one has nothing to re-link: the switch is then the
* agent's first bind, exactly a mount.
* @param agentCtx - the agent's scope context.
* @param id - the preset to compose the agent from instead.
* @returns the preset now installed.