Lab #3105: Docs: manual describes the old extension push path resolution (manifest argument, --extensions-dir scope, global skill fallback) after swamp-club#3018

What changed

swamp-club#3018 (swamp PR #2884, release v20261006.201943.0-sha.4830bd79) changed how swamp extension push, quality and fmt find an extension's files. It also shipped #2747 and #3031. Several manual pages now describe the old behaviour.

New behaviour:

Manifest argument. A relative path is tried against --extensions-dir (when set), then the current directory, then the repo dir. A directory argument means <dir>/manifest.yaml (then .yml, .json). A directory with no manifest fails with No manifest.yaml found in <dir>. A missing path fails with Manifest file not found: <arg> (looked in <every candidate>).
Extensions root. --extensions-dir names the directory that contains extensions/; swamp appends extensions/models (and the other typed dirs) to it. Without the flag, the root is inferred from the manifest's location (nearest ancestor holding extensions/ or .swamp.yaml, never the home directory), but only when no typed entry resolves under the repo dir. An entry found under both the repo dir and the inferred root is an error naming both paths.
Workflows and skills. --extensions-dir, or the inferred root, now covers bundled workflows and skills, not only models, vaults, datastores and reports.
Global skills removed. Skills are never looked up in the user's global skill directory (~/.claude/skills/ etc.) any more. Order: manifest dir (with paths.base: manifest), extensions root, then the project-local skill dir.
Errors. Every not-found error lists the paths searched and names --extensions-dir or paths.base: manifest as the fix.

Pages to update

content/manual/reference/extensions/manifest.md, skills field (around lines 205-215): "resolved from the project-local skill directory first, then the global skill directory" is now wrong. Describe the new order and say the global directory is not searched.
content/manual/reference/extensions/manifest.md, Path Resolution section (around line 518): the note that workflows and skills keep their own multi-base resolution should mention the extensions root as a base.
content/manual/reference/extensions/publishing.md, the --extensions-dir flag rows for push, quality and fmt (lines 32 and 109, plus quality): update to the new help text, "Extensions root: the directory that contains extensions/ (models, workflows and skills resolve from it; env: SWAMP_EXTENSIONS_DIR)". Document that the manifest argument accepts an extension directory, and give the candidate order.
content/manual/reference/repository-configuration.md, Extensions Directory section (around lines 425-435): "all content types: models, vaults, datastores, reports" should add workflows and skills for push, quality and fmt. The manifest.yaml (for extension push) row should say a relative manifest argument tries the flag's directory first, then cwd, then the repo dir.
Optional, content/manual/how-to/extensions/create-and-publish.md or use-local.md: a short section on pushing an extension that lives in a sub-directory or a sibling checkout, e.g. swamp extension push ~/src/my-ext --dry-run with no flags.

The swamp repo's own docs were updated in the same PR (design/primitives/extensions.md, and the swamp skill references extension-publish/references/publishing.md, extension/references/model/skills.md and troubleshooting.md). They can serve as source text.

Session-start 'swamp model search --json' in the AGENTS.md template is unfulfillable - wire it to a hook or drop it

Flaky property test: analyzeExpression dot/bracket agreement fails when the generated model name is a CEL keyword

Accept usernames for user subjects in grant files

Docs: enable-managed-config should say to re-run config migrate when its push fails

Docs: grant file reference shows a stale format and omits resources and subjects

Flaky property test: analyzeExpression hyphenated dot access fails when modelName generates a CEL keyword ("in")

extension quality and push crash with IsADirectory when additionalFiles lists a directory

extension push: a required global argument renders with a stray "" ("text": "string""")

Docs: extension publishing reference is stale on bare specifiers, quality output and fmt config (swamp-club#3022)

swamp-extensions: replace bare import specifiers with npm:/jsr: specifiers in first-party extensions

extension push: 'Requested visibility' line prints to stdout without the logger prefix, twice per run

A nested structural swamp that outlives the run that started it keeps skipping that run's lock while the holder writes

Show signal waits to remote clients and the dashboard

Settle expired signal waits from swamp serve

Resume signalled workflow runs automatically under swamp serve

extension push/quality: structured acceptances for agents, a clearer title than For next time, and an optional reason

extension push: the undecided private-entitlement verdict still says the registry may start a trial at publish

seed:collective cannot produce a superseded personal trial or a returned trial, so the UAT cannot cover them

Replayable state fragments: Git-reviewable desired state for resources changed by model methods

extension push: registry metadata and content hash label files relative to the repo dir, so a push with --extensions-dir records ../ paths

registry: store and show declared acceptances sent in contentMetadata.acceptances at confirm (swamp-club#3021)

extension push --dry-run: authentication verdict prints 'Signed in as .' when the credential is an API key with no username

serve --remote-only: step output from workers is never persisted to the run log (history logs always empty)

serve HA: worker enrollment on a replica that lacks the enrollment token's definition may create a second definition (unverified)

serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once

extension push: version-drift check reports 'no previously published version found' when the registry call failed

Search and list output follows directory iteration order in the definition, workflow, vault and output repositories

extension push: accept attestation-backed adversarial-review evidence (lookup by extension and content hash), generated provenance, and carry the evidence to the registry at confirm (design: Lab #3023)

Workflow load errors print the raw Zod issue dump instead of a readable message

Decide a stricter naming rule for workflow step and job names

serve: run scheduled workflows concurrently (per-workflow serialization), and report queue delay

Show expired approval gates as expired, with a Cancel action in the dashboard

digitalocean codegen leaves an orphaned security_secret.ts model file after its endpoint left the spec

extension promote accepts a yanked version and reports it promoted

Docs: doctor install reports a stale or failing autoupdate scheduler

extension push output: double-quoted adjacent interpolations, repo-relative paths, and --json emits three JSON documents

auto-resolve: the Installing line prints the extension's entire multi-line description

s3-datastore/serve: readResource without a version returns an older version; the latest marker is rewritten backwards

Publish agent-facing projections of the manual: /llms.txt, .md pages, and llms-full.txt

Let agent-runner drive more agent CLIs (Kilo Code and others)

s3-datastore: every fast-path miss re-downloads every _index shard, so a busy serve pulls the whole index every poll (~230 GB/day S3 egress)

Feedback: Swamp as an approval-gated control plane for a small fleet

extension safety analyzer's Deno.Command( warning is a plain substring match

Tell timeouts apart from cancels in method-run records, and review the hidden 30 s fallback timer for step-called model methods

Run from a git worktree: definitions from the worktree, state from the shared repo

S3/GCS datastore: a push that fails after uploading drops its recorded deletes, so the retry brings deleted data back

Tests: bring the in-memory remote's default semantics up to @swamp/s3-datastore and @swamp/gcs-datastore 2026.10.01.1

Tell the pushing client when its extension contentMetadata fails validation

Extension datastore: query still returns an item after its delete is pulled

Cancel, reject and supersede of a parent run should settle its suspended nested child runs

Relationships

#3105 Docs: manual describes the old extension push path resolution (manifest argument, --extensions-dir scope, global skill fallback) after swamp-club#3018

What changed

Pages to update

Closed