#1432 Extension docs still ship the Driver extension type, which the binary refuses (rejectRemovedDriverFields) after #535

The extension documentation shipped with swamp still presents Driver as one of the five extension types, with a full worked example. Execution drivers were replaced by the orchestrator/worker fan-out in #535, and the binary now refuses the wiring: a drivers: manifest entry produces nothing, and a model-level driver: field is rejected by rejectRemovedDriverFields.

Following the current documentation produces an extension that type-checks, bundles nothing, raises no error, and cannot be attached to anything.

Environment

• swamp 20260727.000815.0-sha.db74fcac
• macOS 15 (darwin-aarch64)

The documentation is current, not stale on disk

swamp update to 20260727.000815.0 rewrote both files:

$ ls -la ~/.claude/skills/swamp/references/extension/
-rw-r--r--  6041  Jul 27 14:13  guide.md
-rw-r--r-- 14512  Jul 27 14:13  reference.md

guide.md line 13:

| Control where/how model methods execute | Driver | `export const driver` | `extensions/drivers/*/mod.ts` |

reference.md carries a complete export const driver example with configSchema and createDriver, and the bundle-output table lists extensions/drivers/**/*.ts → .swamp/driver-bundles/.

Observed

Following that documentation:

1. A mod.ts with a valid export const driver type-checks cleanly under ~/.swamp/deno/deno check.

2. Declaring it in a local extension source manifest produces no bundle and no error. swamp doctor extensions --repair reports pass with zero warnings:

   drivers:
     - state/mod.ts

   $ ls .swamp/driver-bundles/*/
   # three directories, all empty

3. swamp doctor extensions --verbose reconciles model, vault, datastore and report. driver is absent from the list.

4. Adding a driver: field to a model definition fails inside rejectRemovedDriverFields (src/domain/removed_driver_fields.ts), after which the definition no longer loads at all — the model disappears from swamp model list and swamp model method run <name> reports Model not found.

Steps 1–3 are silent. The only signal that the extension point is gone arrives at step 4, and it arrives as a definition that stops loading.

Expected

The extension documentation reflects #535: Driver removed from the extension-type table and the bundle-output table, the worked example dropped or replaced with a pointer to remote execution via workers.

Also

Four extensions are still published to the registry with contentTypes: ["drivers"]:

• @webframp/nix (updated 2026-07-18)
• @webframp/agentcore
• @webframp/dry-run
• @mccormick/aurae

Related

• #535 (shipped) — Remote execution: orchestrator/worker fan-out (replaces execution drivers)
• #159, #170 (shipped) — repo-level defaultDriver / defaultDriverConfig