#2505 Failed pulled-extension sources are attributed to @local/model, producing a nonsensical 'extension pull @local/model --force' hint

Summary

When a source file inside a pulled extension fails to bundle (for example after a local edit introduces a syntax error), the catalog row records the failure under the pulled path but with extension_name '@local/model' and version 0.0.0 instead of the owning pulled extension. The broken-bundles warning then names the wrong extension and suggests a command that cannot work.

Reproduce

1. swamp repo init; swamp extension trust add magistr
2. swamp extension pull @magistr/telegram-send@2026.09.24.1
3. Append a syntax error (for example the line: const broken = ;) to .swamp/pulled-extensions/@magistr/telegram-send/models/extensions/models/telegram_send.ts
4. rm -rf .swamp/bundles
5. swamp model create @magistr/telegram/send inst1

Actual

WRN swamp·model·loader: Extension "@local/model" has broken bundles and is not available. Run 'swamp doctor extensions --repair' or 'swamp extension pull "@local/model" --force' to fix.

The catalog (bundle_types) row for the pulled source has state BundleBuildFailed, extension_name @local/model, extension_version 0.0.0.

Expected

The failure is attributed to @magistr/telegram-send at its installed version, and the hint names that extension.

Notes

Likely the cold-start failure path in ExtensionLoader.buildIndex: when the failing source is not found in repository.loadAll() it falls back to makeLocalExtension({ basename: kind }). Found while triaging swamp-club#2476, which avoids relying on extension_name for this reason.