aiwg 2026.7.2 → 2026.7.3

package/CLAUDE.md

@@ -111,13 +111,13 @@ All 10 providers receive all 4 artifact types (agents, commands, skills, rules).
 
 ## Installation
 
-### Claude Code Plugin (Recommended)
+### Claude Code Marketplace (Recommended)
 
 ```bash
 # Add AIWG marketplace (one-time)
 /plugin marketplace add jmagly/ai-writing-guide
 
-# Install plugins (13 published in marketplace.json)
+# Install marketplace packages (13 published in marketplace.json)
 /plugin install sdlc@aiwg                  # Full SDLC framework
 /plugin install marketing@aiwg             # Marketing operations framework
 /plugin install forensics@aiwg             # Digital forensics & incident response
@@ -221,7 +221,7 @@ AIWG uses a unified extension system for all extension types:
 | **Catalog** (1) | catalog (list, info, search) |
 | **Toolsmith** (1) | runtime-info |
 | **Utility** (3) | prefill-cards, contribute-start, validate-metadata |
-| **Plugin** (5) | install-plugin, uninstall-plugin, plugin-status, package-plugin, package-all-plugins |
+| **Marketplace packaging** (5) | install-plugin, uninstall-plugin, plugin-status, package-plugin, package-all-plugins |
 | **Scaffolding** (7) | add-agent, add-command, add-skill, add-template, scaffold-addon, scaffold-extension, scaffold-framework |
 | **Orchestration** (1) | mc (start, dispatch, status, watch, abort, pause, resume, stop, list) |
 | **Ralph** (8) | ralph, ralph-status, ralph-abort, ralph-resume, ralph-attach, agent-loop-ext, ralph-memory, ralph-config |
@@ -249,10 +249,11 @@ aiwg list                    # List installed frameworks
 aiwg remove sdlc             # Remove framework
 aiwg remove my-bundle        # Remove project-local bundle (source preserved; --force, --dry-run supported)
 
-# Project-local bundles (.aiwg/{extensions,addons,frameworks,plugins}/<name>/)
+# Project-local content bundles (.aiwg/{extensions,addons,frameworks}/<name>/)
 aiwg new-bundle my-rules --type extension --starter rule    # Scaffold project-local bundle
 aiwg new-extension my-ext                                   # Alias: --type extension implied
 aiwg new-addon my-pack                                      # Alias: --type addon implied
+aiwg new-plugin my-wrapper                                  # Marketplace delivery wrapper only
 aiwg use my-rules                                           # Deploy a single project-local bundle
 aiwg list --project-local                                   # Show project-local inventory
 aiwg doctor --project-local                                 # Health check (counts, validation, drift, matrix)

package/README.md

@@ -6,7 +6,7 @@
 
 **Multi-agent AI framework for Claude Code, Copilot, Cursor, Warp, and 6 more platforms**
 
-200+ agents, 67+ CLI commands, 400+ deployable agent/skill/command/rule artifacts, 8 core frameworks + training marketplace plugin, 27 addons. SDLC workflows, digital forensics, research management, marketing operations, media curation, ops infrastructure, knowledge base, and fine-tuning dataset curation — all deployable with one command.
+200+ agents, 67+ CLI commands, 400+ deployable agent/skill/command/rule artifacts, 8 core frameworks, 27 addons, and a training marketplace package. SDLC workflows, digital forensics, research management, marketing operations, media curation, ops infrastructure, knowledge base, and fine-tuning dataset curation — all deployable with one command.
 
 ```bash
 npm i -g aiwg        # install globally
@@ -453,7 +453,7 @@ The orchestration pattern: **Primary Author → Parallel Reviewers → Synthesiz
 - **35 enforcement rules** — anti-laziness detection, token security, citation integrity, executable feedback, failure mitigation across 6 LLM archetypes
 - **334 artifact templates** — progressive disclosure templates for requirements, architecture, testing, security, deployment, and more
 - **8 platform support** — deploy to Claude Code, Copilot, Cursor, Warp, Factory AI, OpenCode, Codex, and Windsurf
-- **8 core frameworks + training marketplace plugin** — SDLC, Digital Forensics, Marketing Operations, Research Management, Media Curation, Ops Infrastructure, Knowledge Base, Security Engineering, plus [`aiwg-training`](https://github.com/jmagly/aiwg-training) for fine-tuning dataset curation (corpus-to-dataset pipeline with DPO/KTO/ORPO/SimPO export)
+- **8 core frameworks + training marketplace package** — SDLC, Digital Forensics, Marketing Operations, Research Management, Media Curation, Ops Infrastructure, Knowledge Base, Security Engineering, plus [`aiwg-training`](https://github.com/jmagly/aiwg-training) for fine-tuning dataset curation (corpus-to-dataset pipeline with DPO/KTO/ORPO/SimPO export)
 - **27 addons** — semantic-memory kernel, llm-wiki (Obsidian-native knowledge base), RLM recursive decomposition, voice profiles, testing quality, mutation testing, UAT automation, and more
 - **Agent Loop** — iterative task execution with automatic error recovery and crash resilience (6-8 hour sessions)
 - **RLM addon** — recursive context decomposition for processing 10M+ tokens via sub-agent delegation
@@ -503,8 +503,9 @@ aiwg doctor
 ### Customize Without Forking
 
 Author project-specific rules, skills, agents, addons, or frameworks
-directly under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`.
-No fork, no rebuild. Discovered automatically by `aiwg use`.
+directly under `.aiwg/{extensions,addons,frameworks}/<name>/`. Use
+`.aiwg/plugins/<name>/` only when you are wrapping a bundle for marketplace
+delivery. No fork, no rebuild. Discovered automatically by `aiwg use`.
 
 ```bash
 aiwg new-bundle my-team-rules --type extension --starter rule
@@ -519,7 +520,7 @@ The bundle is **byte-identical** in shape to its upstream form, so
 [customization guide](docs/customization/README.md) for the three paths
 (project-local, fork, corpus).
 
-### Claude Code Plugin (Alternative)
+### Claude Code Marketplace (Alternative)
 
 ```bash
 /plugin marketplace add jmagly/ai-writing-guide
@@ -1275,7 +1276,7 @@ All 8 platforms receive agents, commands, skills, and rules. Deployment adapts t
 | **Workspace** | `status`, `migrate-workspace`, `rollback-workspace` | Workspace health and migration |
 | **MCP** | `mcp serve`, `mcp install`, `mcp info` | Model Context Protocol server |
 | **Catalog** | `catalog list`, `catalog info`, `catalog search` | Browse available extensions |
-| **Plugins** | `install-plugin`, `uninstall-plugin`, `plugin-status`, `package-plugin`, `package-all-plugins` | Plugin management |
+| **Marketplace packaging** | `install-plugin`, `uninstall-plugin`, `plugin-status`, `package-plugin`, `package-all-plugins` | Install and package delivery wrappers |
 | **Scaffolding** | `add-agent`, `add-command`, `add-skill`, `add-template`, `scaffold-addon`, `scaffold-extension`, `scaffold-framework` | Create new extensions |
 | **Ralph** | `ralph`, `ralph-status`, `ralph-abort`, `ralph-resume`, `ralph-external`, `ralph-memory`, `ralph-config` | Iterative execution engine |
 | **Metrics** | `cost-report`, `cost-history`, `metrics-tokens` | Token usage and cost tracking |

package/agentic/code/addons/aiwg-utils/agents/aiwg-steward.md

@@ -58,9 +58,9 @@ Route these intents directly:
 
 | User intent | Primary route | Notes |
 |---|---|---|
-| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates source under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`; deploy with `aiwg use <name>`. |
+| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates content source under `.aiwg/{extensions,addons,frameworks}/<name>/`; deploy with `aiwg use <name>`. |
 | Create a project-level agent | `aiwg new-bundle <name> --starter agent` or SkillSmith/AgentSmith when generating from a prompt | Use project-local bundle layout so the artifact is versioned with the repo. |
-| Choose extension/addon/framework/plugin shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. |
+| Choose extension/addon/framework shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. Plugins are marketplace delivery wrappers. |
 | Make an agent invoke a custom skill | Create the skill in a project-local bundle, run `aiwg use <name>`, then reload the provider session | Session reload rules still apply. |
 
 Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.

package/agentic/code/addons/aiwg-utils/skills/aiwg-language-map/SKILL.md

@@ -305,14 +305,14 @@ When you don't know which domain a need falls into:
 
 ## Project-local extensions (pilot → promote)
 
-Addons and extensions don't all have to come from upstream. Users can pilot their own bundles per-project under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`, validate them, then promote to upstream when mature. Curated phrases:
+Addons, extensions, and frameworks don't all have to come from upstream. Users can pilot content bundles per-project under `.aiwg/{extensions,addons,frameworks}/<name>/`, validate them, then promote to upstream when mature. Use `.aiwg/plugins/<name>/` only when wrapping a bundle for marketplace delivery. Curated phrases:
 
 ```bash
 aiwg new-bundle <name>                         # scaffold; auto-builds project graph
 aiwg new-extension <name> --starter rule       # extension with starter rule
 aiwg new-addon <name>                          # addon
 aiwg new-framework <name>                      # framework
-aiwg new-plugin <name>                         # plugin
+aiwg new-plugin <name>                         # marketplace delivery wrapper
 aiwg new-bundle <name> --dry-run               # preview without writing
 aiwg list --project-local                      # inventory + validation status
 aiwg doctor --project-local                    # health check (counts, drift, shadows)

package/agentic/code/addons/aiwg-utils/skills/aiwg-status/SKILL.md

@@ -52,7 +52,7 @@ When triggered:
 3. **What the dashboard shows**:
    - Installed frameworks and addons from `.aiwg/frameworks/registry.json` (name, version, install date)
    - Deployed provider artifact directories (e.g., `.claude/`, `.github/`, `.cursor/`)
-   - Project-local bundles under `.aiwg/{extensions,addons,frameworks,plugins}/`
+   - Project-local content bundles under `.aiwg/{extensions,addons,frameworks}/` and delivery wrappers under `.aiwg/plugins/`
    - `.aiwg/` artifact counts per subdirectory (`requirements/`: 4 files, `architecture/`: 2 files, etc.)
    - Last sync timestamp
    - Overall health indicator (OK / WARN / ERROR)

package/agentic/code/addons/aiwg-utils/skills/aiwg-utils-quickref/SKILL.md

@@ -204,7 +204,7 @@ aiwg discover "scaffold a project"             # → new-project (+ new-bundle f
 
 ### Project-local extensions (pilot → promote)
 
-AIWG supports authoring rules/skills/agents per-project under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/` — pilot here, promote upstream when mature.
+AIWG supports authoring rules/skills/agents per-project under `.aiwg/{extensions,addons,frameworks}/<name>/` — pilot here, promote upstream when mature. Use `.aiwg/plugins/<name>/` only for marketplace delivery wrappers.
 
 ```bash
 aiwg new-bundle <name>                         # scaffold; auto-builds project graph

package/agentic/code/addons/aiwg-utils/skills/index/SKILL.md

@@ -23,7 +23,7 @@ Alternate expressions and non-obvious activations (primary phrases are matched a
 - "how many artifacts are indexed" → stats
 - "is the index healthy" → status
 - "export the index for Fortemi" → export --format fortemi
-- "sync the Fortemi cache" → sync --backend fortemi-core
+- "sync the Fortemi cache" → sync
 - "refresh the index" → build --force
 
 ## Trigger Patterns Reference
@@ -41,7 +41,7 @@ Alternate expressions and non-obvious activations (primary phrases are matched a
 | Health/status | "is the index stale?" | Run `aiwg index status --json` |
 | JSON output | "get index stats as JSON" | Run `aiwg index stats --json` |
 | Fortemi export | "export this index for Fortemi" | Run `aiwg index export --format fortemi --schema-version v2` |
-| Fortemi cache | "sync the Fortemi Core index" | Run `aiwg index sync --backend fortemi-core` |
+| Fortemi cache | "sync the Fortemi Core index" | Run `aiwg index sync` |
 
 > **`.aiwg/.index/` is a regenerable build artifact, not committed.** It is gitignored by default (`aiwg use` / `aiwg regenerate` / scaffolding add it to `.gitignore`), so a fresh clone has no index — `aiwg index build --all` is the standard bootstrap. `aiwg doctor` flags a missing index (`info`, when an `index` block is declared in `.aiwg/aiwg.config` — the canonical home as of #1491 — or legacy `.aiwg/config.yaml`) or a stale one (`warn`, when recorded source files changed) and points back to `aiwg index build`.
 
@@ -69,12 +69,12 @@ When triggered:
    # Machine-readable search results
    aiwg index query "<text>" --json
 
-   # Opt-in Fortemi Core static-cache query
-   aiwg index query "<text>" --backend fortemi-core --json
+   # default Fortemi Core static-cache query
+   aiwg index query "<text>" --json
 
    # Fortemi static semantic and filtered hybrid query modes
-   aiwg index query "<text>" --semantic --backend fortemi-core --json
-   aiwg index query "<text>" --hybrid --backend fortemi-core --type adr --tags search --json
+   aiwg index query "<text>" --semantic --json
+   aiwg index query "<text>" --hybrid --type adr --tags search --json
 
    # Show dependency graph for an artifact
    aiwg index deps <artifact-path>
@@ -95,20 +95,19 @@ When triggered:
    # Health/status, including optional Fortemi Core cache state
    aiwg index status --json
 
-   # Export and sync the opt-in Fortemi Core static cache
+   # Export and sync the default Fortemi Core static cache
    aiwg index export --format fortemi --schema-version v2
-   aiwg index sync --backend fortemi-core
+   aiwg index sync
    ```
 
 3. **Report the result** — surface the relevant matches, dependencies, or counts.
 
 ### Fortemi Core Backend
 
-The local `.aiwg/.index` backend remains the default. Use
-`--backend fortemi-core` only when the project has already run
-`aiwg index sync --backend fortemi-core`. If the Fortemi cache is missing or
-stale, rerun the same command without `--backend fortemi-core` to fall back to
-the local index. A valid synced Fortemi cache with zero items is not stale:
+Fortemi Core is the default artifact search backend after `aiwg index sync`.
+Use `--backend local` only for the legacy local fallback during the phase-out
+window. If the Fortemi cache is missing or stale, run `aiwg index sync`.
+A valid synced Fortemi cache with zero items is not stale:
 query/fulltext return empty results, discover reports a Fortemi static-cache
 no-match hint, and show does not fall back to the local AIWG corpus when the
 Fortemi backend was explicit.

package/agentic/code/addons/aiwg-utils/skills/install-plugin/SKILL.md

@@ -2,12 +2,12 @@
 namespace: aiwg
 name: install-plugin
 platforms: [all]
-description: Install plugins into Claude Code from the AIWG marketplace with registry lookup, download, and local deployment
+description: Install Claude Code marketplace plugins with registry lookup, download, and local deployment
 ---
 
 # Install Plugin
 
-You install a plugin into Claude Code from the AIWG marketplace. Plugins are pre-packaged bundles of agents, skills, commands, and rules. You handle registry lookup, download, and local deployment.
+You install a Claude Code marketplace plugin. In AIWG vocabulary, a plugin is a delivery wrapper around an extension, addon, or framework, not a separate content type. You handle registry lookup, download, and local deployment.
 
 ## Triggers
 
@@ -57,11 +57,11 @@ When triggered:
    aiwg install-plugin sdlc@aiwg --force
    ```
 
-3. **Report the result** — confirm which agents, skills, commands, and rules were installed and where.
+3. **Report the result** — name the installed marketplace wrapper and confirm which agents, skills, commands, and rules were deployed and where.
 
-## Available Plugins (AIWG Marketplace)
+## Available Marketplace Packages
 
-| Plugin | Contents | Use Case |
+| Package | Payload | Use Case |
 |--------|----------|----------|
 | `sdlc@aiwg` | 58 agents, 42 commands, SDLC workflows | Full software development lifecycle |
 | `voice@aiwg` | Voice profiles, soul system | Content style and persona management |
@@ -70,12 +70,12 @@ When triggered:
 
 ## What Happens on Install
 
-1. Plugin manifest fetched from marketplace
+1. Delivery manifest fetched from marketplace
 2. Agents deployed to `.claude/agents/`
 3. Commands deployed to `.claude/commands/`
 4. Skills deployed to `.claude/skills/`
 5. Rules deployed to `.claude/rules/`
-6. Plugin registered in local plugin registry
+6. Delivery wrapper registered in local plugin registry
 
 ## Examples
 

package/agentic/code/addons/aiwg-utils/skills/package-all-plugins/SKILL.md

@@ -2,12 +2,12 @@
 namespace: aiwg
 name: package-all-plugins
 platforms: [all]
-description: Batch package every AIWG/Codex plugin in the workspace into distributable plugin archives — runs package-plugin for all plugins at once
+description: Batch package every AIWG/Codex marketplace wrapper in the workspace into distributable plugin archives — runs package-plugin for all wrappers at once
 ---
 
 # Package All Plugins
 
-You run `package-plugin` for every plugin in the workspace in a single batch operation. This is **plugin packaging** — it produces AIWG/Codex plugin archives. It is **not** native/language-toolchain release packaging (Rust crates, `.deb`/`.rpm`, container images, GHCR, or release-asset checksums). For native or full release-pipeline work use `flow-release` / `release-publication-verify`, not this skill.
+You run `package-plugin` for every marketplace wrapper in the workspace in a single batch operation. This is **plugin packaging** — it produces AIWG/Codex plugin archives that wrap extension, addon, or framework payloads. It is **not** native/language-toolchain release packaging (Rust crates, `.deb`/`.rpm`, container images, GHCR, or release-asset checksums). For native or full release-pipeline work use `flow-release` / `release-publication-verify`, not this skill.
 
 ## Triggers
 
@@ -61,7 +61,7 @@ When triggered:
    aiwg package-all-plugins --bump patch
    ```
 
-3. **Report the result** — list each plugin with its status (packaged, failed, skipped), total count, and any errors.
+3. **Report the result** — list each marketplace wrapper with its status (packaged, failed, skipped), total count, and any errors.
 
 ## Output Format
 
@@ -83,7 +83,7 @@ By default (`--abort-on-error`), the batch stops at the first failure and report
 
 ## Relationship to `package-plugin`
 
-`package-all-plugins` is a thin loop over `package-plugin`. Each plugin runs through the same validation and packaging logic as a single `package-plugin` call. Flags like `--dry-run`, `--publish`, and `--bump` are forwarded to each plugin invocation.
+`package-all-plugins` is a thin loop over `package-plugin`. Each marketplace wrapper runs through the same validation and packaging logic as a single `package-plugin` call. Flags like `--dry-run`, `--publish`, and `--bump` are forwarded to each invocation.
 
 ## Examples
 

package/agentic/code/addons/aiwg-utils/skills/package-plugin/SKILL.md

@@ -2,12 +2,12 @@
 namespace: aiwg
 name: package-plugin
 platforms: [all]
-description: Bundle a single plugin into a distributable marketplace archive, validating metadata and optionally publishing
+description: Bundle a single marketplace delivery wrapper into a distributable archive, validating metadata and optionally publishing
 ---
 
 # Package Plugin
 
-You bundle a single plugin into a distributable package for the AIWG marketplace. You validate metadata, create the package archive, and optionally publish to the registry.
+You bundle a single marketplace delivery wrapper for the AIWG marketplace. In AIWG vocabulary, the plugin layer packages an extension, addon, or framework payload for distribution. You validate metadata, create the package archive, and optionally publish to the registry.
 
 ## Triggers
 
@@ -34,7 +34,7 @@ Alternate expressions and non-obvious activations (primary phrases are matched a
 When triggered:
 
 1. **Extract intent**:
-   - Which plugin is being packaged?
+   - Which delivery wrapper is being packaged?
    - Should it be published after packaging, or just archived locally?
    - Is a version bump needed?
    - Is this a validation dry run?
@@ -42,7 +42,7 @@ When triggered:
 2. **Run the appropriate command**:
 
    ```bash
-   # Package a plugin (creates archive, no publish)
+   # Package a marketplace wrapper (creates archive, no publish)
    aiwg package-plugin sdlc
    aiwg package-plugin voice
    aiwg package-plugin marketing
@@ -65,7 +65,7 @@ When triggered:
 
 ## What the Package Contains
 
-A plugin package archive (`.aiwg-plugin.tar.gz`) includes:
+A plugin package archive (`.aiwg-plugin.tar.gz`) is a delivery wrapper. It includes the manifest plus the payload files being distributed:
 
 | Contents | Path in Archive |
 |----------|----------------|
@@ -73,7 +73,7 @@ A plugin package archive (`.aiwg-plugin.tar.gz`) includes:
 | Command definitions | `commands/` |
 | Skill definitions | `skills/` |
 | Rule definitions | `rules/` |
-| Plugin manifest | `plugin.json` |
+| Delivery manifest | `plugin.json` |
 | Changelog | `CHANGELOG.md` (if present) |
 
 Files excluded from packages: `.aiwg/working/`, test fixtures, development-only configs.
@@ -84,7 +84,7 @@ Before creating the archive, the command automatically runs:
 
 1. `aiwg validate-metadata` — all extension definitions must pass
 2. Version format check — must be valid CalVer
-3. Manifest completeness — `id`, `name`, `description`, `version` required
+3. Delivery manifest completeness — `id`, `name`, `description`, `version` required
 
 Packaging fails if any validation step fails.
 

package/agentic/code/addons/aiwg-utils/skills/plugin-status/SKILL.md

@@ -2,12 +2,12 @@
 namespace: aiwg
 name: plugin-status
 platforms: [all]
-description: List installed Claude Code plugins with version, install date, and enabled status
+description: List installed Claude Code marketplace plugins with version, install date, and enabled status
 ---
 
 # Plugin Status
 
-You list all installed Claude Code plugins with their version, install date, and enabled status.
+You list installed Claude Code marketplace plugins with their version, install date, and enabled status. In AIWG vocabulary, these are delivery wrappers around extension, addon, or framework payloads.
 
 ## Triggers
 
@@ -55,12 +55,12 @@ When triggered:
    aiwg plugin-status --json
    ```
 
-3. **Report the result** — show plugin name, version, install date, enabled status, and update availability.
+3. **Report the result** — show package name, version, install date, enabled status, and update availability.
 
 ## Output Format
 
 ```
-Installed Plugins (2)
+Installed Marketplace Packages (2)
 
   sdlc@aiwg
     Version:     2026.3.15

package/agentic/code/addons/aiwg-utils/skills/steward/SKILL.md

@@ -80,9 +80,9 @@ Route these intents directly:
 
 | User intent | Primary route | Notes |
 |---|---|---|
-| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates source under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`; deploy with `aiwg use <name>`. |
+| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates content source under `.aiwg/{extensions,addons,frameworks}/<name>/`; deploy with `aiwg use <name>`. |
 | Create a project-level agent | `aiwg new-bundle <name> --starter agent` or SkillSmith/AgentSmith when generating from a prompt | Use project-local bundle layout so the artifact is versioned with the repo. |
-| Choose extension/addon/framework/plugin shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. |
+| Choose extension/addon/framework shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. Plugins are marketplace delivery wrappers. |
 | Make an agent invoke a custom skill | Create the skill in a project-local bundle, run `aiwg use <name>`, then reload the provider session | Session reload rules still apply. |
 
 Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.

package/agentic/code/addons/aiwg-utils/skills/uninstall-plugin/SKILL.md

@@ -2,12 +2,12 @@
 namespace: aiwg
 name: uninstall-plugin
 platforms: [all]
-description: Remove a previously installed Claude Code plugin and unregister it from the local plugin registry
+description: Remove a previously installed Claude Code marketplace plugin and unregister it from the local plugin registry
 ---
 
 # Uninstall Plugin
 
-You remove a previously installed Claude Code plugin. You remove deployed plugin files and unregister the plugin from the local plugin registry.
+You remove a previously installed Claude Code marketplace plugin. In AIWG vocabulary, the plugin is the delivery wrapper; the deployed files are its extension, addon, or framework payload. You remove deployed files and unregister the wrapper from the local plugin registry.
 
 ## Triggers
 
@@ -52,7 +52,7 @@ When triggered:
    aiwg uninstall-plugin sdlc@aiwg --keep-artifacts
    ```
 
-3. **Report the result** — list what was removed (agents, commands, skills, rules) and confirm the plugin is deregistered.
+3. **Report the result** — list what was removed (agents, commands, skills, rules) and confirm the marketplace wrapper is deregistered.
 
 ## What Gets Removed
 
@@ -62,15 +62,15 @@ When triggered:
 | Command files | Files in `.claude/commands/` that belong to the plugin |
 | Skill files | Files in `.claude/skills/` that belong to the plugin |
 | Rule files | Files in `.claude/rules/` that belong to the plugin |
-| Registry entry | Plugin entry removed from local plugin registry |
+| Registry entry | Delivery-wrapper entry removed from local plugin registry |
 
 ## What Is NOT Removed
 
 | Preserved | Reason |
 |-----------|--------|
-| `.aiwg/` project artifacts | These are your project output, not plugin files |
-| Shared skills used by other plugins | Removed only when last dependent plugin is removed |
-| Custom modifications to plugin files | Files modified after install are flagged, not deleted |
+| `.aiwg/` project artifacts | These are your project output, not marketplace package files |
+| Shared skills used by other packages | Removed only when the last dependent package is removed |
+| Custom modifications to deployed package files | Files modified after install are flagged, not deleted |
 
 ## Examples
 

package/agentic/code/agents/personas/aiwg-steward.md

@@ -65,9 +65,9 @@ Route these intents directly:
 
 | User intent | Primary route | Notes |
 |---|---|---|
-| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates source under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`; deploy with `aiwg use <name>`. |
+| Create a repo/project-level skill | `aiwg new-bundle <name> --starter skill` or `aiwg new-extension <name> --starter skill` | Creates content source under `.aiwg/{extensions,addons,frameworks}/<name>/`; deploy with `aiwg use <name>`. |
 | Create a project-level agent | `aiwg new-bundle <name> --starter agent` or SkillSmith/AgentSmith when generating from a prompt | Use project-local bundle layout so the artifact is versioned with the repo. |
-| Choose extension/addon/framework/plugin shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. |
+| Choose extension/addon/framework shape | `aiwg discover "project-local customization"` and docs/customization quickstart | Extensions are the usual smallest local customization; addons/frameworks are heavier. Plugins are marketplace delivery wrappers. |
 | Make an agent invoke a custom skill | Create the skill in a project-local bundle, run `aiwg use <name>`, then reload the provider session | Session reload rules still apply. |
 
 Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.

package/agentic/code/frameworks/knowledge-base/skills/kb-ingest/SKILL.md

@@ -48,9 +48,9 @@ echo "# Foo" > "$KB_ROOT/entities/foo.md"
 ```
 
 Fortemi storage routing here is only a persistence backend choice. It is not the
-Fortemi Core index/search backend used by `aiwg index ... --backend
-fortemi-core`; KB pages join that preview only after the artifact graph has been
-built and synced with `aiwg index sync --backend fortemi-core`.
+Fortemi Core index/search backend used by `aiwg index ...` by default;
+`--backend local` selects the legacy fallback. KB pages join that search cache
+only after the artifact graph has been built and synced with `aiwg index sync`.
 
 ### `--dry-run` (optional)
 Show what would be created or updated without writing files.

package/agentic/code/frameworks/knowledge-base/skills/knowledge-base-quickref/SKILL.md

@@ -81,10 +81,10 @@ aiwg index neighbors --graph kb --node <slug>  # traverse the KB graph
 
 KB ingest and health operations continue to use `resolveStorage('kb')` and the
 semantic-memory topology. Fortemi storage routing, when configured through
-`.aiwg/storage.config`, is separate from the opt-in Fortemi Core index/search
-backend. During the migration preview, use `--backend fortemi-core` only on
+`.aiwg/storage.config`, is separate from the default Fortemi Core index/search
+backend. During the migration preview, use `--backend local` for legacy fallback only on
 artifact graph commands such as `aiwg index neighbors --graph kb` after
-`aiwg index sync --backend fortemi-core`; do not treat `kb-ingest` or
+`aiwg index sync`; do not treat `kb-ingest` or
 `kb-health` as Fortemi Core ingest commands.
 
 ## How knowledge-base composes with semantic-memory

package/agentic/code/frameworks/media-curator/docs/type-flexible-curation.md

@@ -44,10 +44,11 @@ tooling that fits the observed need:
 3. Wrap the tool as a skill or small helper that preserves the generic contract:
    input discovery/acquisition, quality assessment, metadata/provenance,
    integrity, and export or handoff.
-4. Keep type-specific fields in that specialized skill or plugin. Do not move
+4. Keep type-specific fields in that specialized skill or bundle. Do not move
    them into the generic intake unless they apply across asset classes.
 5. If the workflow is project-specific or experimental, author it as a
-   project-local bundle under `.aiwg/{extensions,addons,frameworks,plugins}/`
+   project-local content bundle under `.aiwg/{extensions,addons,frameworks}/`
+   or as a marketplace delivery wrapper under `.aiwg/plugins/`
    and promote upstream only after the contract stabilizes.
 
 ## Consequences

package/agentic/code/frameworks/research-complete/skills/research-query/SKILL.md

@@ -32,10 +32,11 @@ A natural language question to answer from the corpus.
 Search depth: `quick` (tag + title matching only) or `thorough` (full-text content search). Default: `thorough`.
 
 ### `--backend` (optional)
-Retrieval backend for the executable source-selection wrapper: `local` or `fortemi-core`. Default: `local`.
-When `fortemi-core` is explicit, the Fortemi static cache must already be
-synced with `aiwg index sync --backend fortemi-core`; missing, stale, or
-malformed caches fail with recovery guidance instead of falling back silently.
+Retrieval backend for the executable source-selection wrapper: `fortemi-core` or `local`. Default: `fortemi-core`.
+By default, research-query uses the Fortemi static cache after it is synced
+with `aiwg index sync`; missing, stale, or malformed caches fail with recovery guidance
+instead of falling back silently. Use `--backend local` only for the legacy
+local corpus fallback.
 
 ### `--save` (optional)
 Save the synthesized answer as a new artifact in `.aiwg/research/synthesis/`.
@@ -174,7 +175,7 @@ confidence: moderate
 /research-query "prompt injection defenses" --depth quick
 
 # Use the Fortemi Core static cache for source selection
-aiwg research-query "prompt injection defenses" --backend fortemi-core --sources-only --json
+aiwg research-query "prompt injection defenses" --sources-only --json
 
 # Just list matching sources
 /research-query "multi-agent orchestration" --sources-only

package/agentic/code/frameworks/sdlc-complete/skills/artifact-lookup/SKILL.md

@@ -44,12 +44,12 @@ aiwg index query --tags security,auth --json
 # Combined filters
 aiwg index query "login" --type use-case --phase requirements --json
 
-# Opt-in Fortemi Core static cache
-aiwg index query "login" --backend fortemi-core --json
+# default Fortemi Core static cache
+aiwg index query "login" --json
 
 # Fortemi static semantic and filtered hybrid modes
-aiwg index query "login architecture" --semantic --backend fortemi-core --json
-aiwg index query "login architecture" --hybrid --backend fortemi-core --type adr --tags auth --json
+aiwg index query "login architecture" --semantic --json
+aiwg index query "login architecture" --hybrid --type adr --tags auth --json
 ```
 
 Parse the JSON output and present results in a readable summary:
@@ -72,9 +72,9 @@ aiwg index deps .aiwg/requirements/UC-001.md --direction upstream --json
 aiwg index deps .aiwg/requirements/UC-001.md --direction downstream --json
 
 # Fortemi Core static-cache traversal, when synced
-aiwg index deps .aiwg/requirements/UC-001.md --backend fortemi-core --json
-aiwg index neighbors --graph project --node UC-001 --backend fortemi-core --json
-aiwg index set --graph project --op intersection --node-a UC-001 --node-b ADR-001 --backend fortemi-core --json
+aiwg index deps .aiwg/requirements/UC-001.md --json
+aiwg index neighbors --graph project --node UC-001 --json
+aiwg index set --graph project --op intersection --node-a UC-001 --node-b ADR-001 --json
 ```
 
 Present the dependency tree in a readable format:
@@ -152,8 +152,8 @@ Found 3 artifacts about "authentication":
 
 - Artifact index must exist (`aiwg index build` must have been run)
 - If index doesn't exist, offer to build it first
-- Fortemi Core lookups require `aiwg index sync --backend fortemi-core`; if the
-  static cache is missing or stale, omit `--backend fortemi-core` and use the
+- Fortemi Core lookups require `aiwg index sync`; if the
+  static cache is missing or stale, omit the legacy backend and use the
   local index
 
 ## References

package/agentic/code/frameworks/sdlc-complete/skills/build-artifact-index/SKILL.md

@@ -36,16 +36,17 @@ aiwg index build --all
 
 Report what changed: new artifacts indexed, updated, unchanged, and removed counts.
 
-If the operator explicitly asks for Fortemi Core preview cache refresh after a
+If the operator explicitly asks for Fortemi Core cache refresh after a
 successful build, run:
 
 ```bash
-aiwg index sync --backend fortemi-core
+aiwg index sync
 aiwg index status --json
 ```
 
-Do not switch default behavior to Fortemi Core; the synced cache is opt-in and
-read only when commands pass `--backend fortemi-core`.
+Fortemi Core is the default artifact search backend after sync. Keep the
+legacy local backend available behind `--backend local` during the phase-out
+window.
 
 ### Archived Query Answers
 

package/agentic/code/frameworks/sdlc-complete/skills/flow-release/SKILL.md

@@ -8,6 +8,11 @@ triggers:
   - "help me make the build or deployment path safer"
   - "start with pipeline safety or release readiness"
   - "pipeline safety ci"
+  - "release flow"
+  - "flow release"
+  - "flow-release"
+  - "run the release flow"
+  - "run release flow"
 commandHint:
   argumentHint: '<version> [--channel <stable|rc|beta|alpha|nightly>] [--dry-run] [--skip-uat] [--no-mirror] [--config <path>] [--guidance "text"]'
   allowedTools: 'Task, Read, Write, Edit, Bash, Glob, Grep, mcp__git-gitea__*'
@@ -47,6 +52,10 @@ When the user requests a release:
 ## Natural language triggers
 
 - "release v2026.5.2"
+- "release flow"
+- "flow release"
+- "flow-release"
+- "run the release flow"
 - "cut a release"
 - "promote to stable"
 - "ship it"

package/agentic/code/frameworks/sdlc-complete/templates/project/AIWG-codex.md

@@ -16,7 +16,7 @@ SDLC Complete — agents, commands, skills, and rules for full lifecycle coverag
 
 ## Customize Per Project
 
-Author project-specific rules, skills, agents, addons, or frameworks under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`. Discovered automatically by `aiwg use`.
+Author project-specific content bundles under `.aiwg/{extensions,addons,frameworks}/<name>/`. Use `.aiwg/plugins/<name>/` only for marketplace delivery wrappers. Discovered automatically by `aiwg use`.
 
 ```bash
 aiwg new-bundle my-rules --type extension --starter rule

package/agentic/code/frameworks/sdlc-complete/templates/project/AIWG-copilot.md

@@ -16,7 +16,7 @@ SDLC Complete — agents, commands, skills, and rules for full lifecycle coverag
 
 ## Customize Per Project
 
-Author project-specific rules, skills, agents, addons, or frameworks under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/`. Discovered automatically by `aiwg use`.
+Author project-specific content bundles under `.aiwg/{extensions,addons,frameworks}/<name>/`. Use `.aiwg/plugins/<name>/` only for marketplace delivery wrappers. Discovered automatically by `aiwg use`.
 
 ```bash
 aiwg new-bundle my-rules --type extension --starter rule