|
|
@@ -18,7 +18,7 @@ The `ptc` preset also declares `workflow-worker-thread` disabled. That preset ke
|
|
|
|
|
|
Each disabled row carries its restore recipe in a local comment. An overlay row re-enables the capability for a base-backed profile from `$DSH_HOME/cordis.patch.yml` or a `--patch` file. Preset files take no patches (`packages/preset/agent-presets/README.md`), so a Web session that wants `ralph` duplicates the preset under a **new id** into `$DSH_HOME/.agent-presets` and drops `disabled`; a copy reusing the shipped id is shadowed by the shipped root, which wins duplicate ids (`packages/preset/agent-presets/src/index.ts`), and `copy()` refuses an id any root already supplies. In `ptc` the duplicate drops `disabled` from the tool row and the engine row together, because `tool-ralph` injects `ctx.workflowEngine`.
|
|
|
|
|
|
-`packages/bundle/web-app/cordis.patch.yml` keeps its own `tool-ralph` disable even though `base` now ships the row off. `validatePresetPlaneSeparation` in `scripts/verify-cordis-config.ts` collects declared row ids without regard to `disabled`, so deleting that row would return `tool-ralph` to the Web host plane and collide with the same id in every preset.
|
|
|
+`packages/bundle/web-app/cordis.patch.yml` restates that disable for its own layer. `validatePresetPlaneSeparation` in `scripts/verify-cordis-config.ts` collects declared row ids without regard to `disabled`, so deleting that row would return `tool-ralph` to the Web host plane and collide with the same id in every preset.
|
|
|
|
|
|
`snapshots/session/ralph-loop` becomes the owner of a `ralph` composition whose `cordis.yml` and `cordis.snapshot.yml` re-enable the row, so the one recorded scenario that exercises the tool keeps its evidence. A sibling composition does not inherit `text-turn/cordis.snapshot.yml`, so the new replay patch restates those swaps alongside the `ralph` row.
|
|
|
|