Project-Local Customization

Status: Shipped in 2026.5.x. The `.aiwg/{extensions,addons,frameworks}/<name>/` content layout

superseded the original single-directory `.aiwg/.project/` proposal (#750 → epic #1033).

`.aiwg/plugins/<name>/` remains supported for marketplace delivery wrappers.

Canonical docs

The authoritative documentation now lives under `docs/customization/`:

Doc	What it covers
Quickstart	Author your first project-local bundle in 5 minutes
Lifecycle reference	Discovery, deploy, conflict resolution, doctor, remove, promote, activity log
Project quickrefs	Always-visible project orientation, precedence, generation, and provider deployment
Type disambiguation	Which bundle type to author
Customization README	Path A (project-local) / Path B (fork) / Path C (corpus)
Troubleshooting	Common failures and fixes
From-fork migration	Move existing fork-based customizations to project-local

Quick orientation

aiwg new-bundle <name>        # scaffold .aiwg/extensions/<name>/
aiwg use <name>               # deploy
aiwg doctor --project-local   # health check
aiwg remove <name>            # revert deployed files (source preserved)
aiwg promote <name>           # graduate to upstream or corpus
aiwg activity-log show        # audit trail
aiwg quickref generate --project --dry-run  # preview project orientation
aiwg quickref deploy --project              # deploy to provider kernel surfaces

The load-bearing invariant: a project-local bundle is byte-identical in shape to its upstream form, so `aiwg promote` is a hash-verified copy with zero rewrite (ADR #1038).