#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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.