…GES REQUESTED

Rex's review of #344 surfaced a real correctness gap between AgDR-0049's
Decision #4 claim and what the smoke test actually enforces. The leak-scan
is a PATH-scan (catches files at framework-distinctive paths like
_lib-portfolio-paths.sh) but is NOT a CONTENT-scan (doesn't catch SKILL.md
prose mentioning /handover, or _lib-audit-history.sh calling
portfolio_projects_dir). Several extracted files in audit-pack DO carry
such prose references.

Per the operator's chosen path (Rex's option a, honest-scope amend, not
full refactor): acknowledge the limitation in the AgDR + add a "Known
framework references" section to the audit-pack README so adopters know
what they're looking at, while preserving the generated-not-forked
contract (decision #3) that would be contradicted by content-scrubbing.

Changes:

- AgDR-0049 § Decision #4 rewritten — distinguishes path-leak guard
  (mechanically enforced) from content references (deliberate, funnel-
  pointer, graceful-degrade outside an apexyard fork). v2 may revisit if
  adopter friction surfaces.
- marketplace/audit-pack/README.md — new "Known framework references"
  section enumerates the three concrete surfaces Rex found (SKILL.md
  prose hints, _lib-audit-history.sh portfolio_projects_dir fallback,
  broken relative links to upstream docs/agdr/). Frames each as
  intentional + funnel-pointer. Flags v2 as the escape hatch.
- safety-hooks is unaffected — Rex confirmed graceful-degrades correctly.

Smoke test unchanged (path-scan is the right shape for what it catches;
the AgDR amend clarifies what it does and doesn't claim).

Refs #321

* feat(#321): scaffold marketplace/audit-pack + safety-hooks layout

- marketplace/audit-pack/ — extracted /launch-check + 8 deep-dive audit
  skills + _lib-audit-history.sh + _lib-read-config.sh + _lib-ops-root.sh
  + AI-crawler registry + 8 audit templates. Includes authored README
  and PLUGIN.json that pitch the full framework as the graduation path.
- marketplace/safety-hooks/ — extracted 7 safety hooks (secrets / main
  push / git-add-all / pre-push / commit-refs / PR-title / branch-name)
  + _lib-tracker.sh (tracker-agnostic) + _lib-read-config.sh +
  _lib-ops-root.sh + _lib-extract-pr.sh + settings.snippet.json showing
  recommended hook wiring. Same funnel-pitching README and PLUGIN.json.
- EXTRACTION_MANIFEST.json in each sub-pack records the upstream SHA
  and file inventory so the "generated, not forked" maintenance
  contract is auditable.
- Strategic intent: a one-way discovery funnel from Claude Code
  marketplace users to full-framework adopters. The two sub-packs are
  genuinely self-contained — no portfolio model, no /handover, no role
  definitions — and pitch the full framework via the README without
  pressuring.

Closes #321

* feat(#321): bin/extract-subpacks.sh + extraction smoke test

- bin/extract-subpacks.sh — idempotent extraction script that copies
  the audit-pack + safety-hooks inventories from upstream HEAD into
  marketplace/<pack>/, writes EXTRACTION_MANIFEST.json with the
  upstream SHA, and supports --dry-run + --manifest-only for CI
  validation. Invokable both locally (operator debugging) and from
  the release-tag CI workflow.
- .claude/hooks/tests/test_subpack_extraction.sh — smoke test that
  (a) runs extraction into a tmp dir, (b) asserts the file inventory
  matches the AgDR-0049 contract for both sub-packs, (c) scans for
  framework-distinctive paths that would indicate a leak
  (apexyard.projects.yaml, _lib-portfolio-paths.sh, /handover skill,
  /agdr skill, role definitions), (d) plants a deliberate leak token
  and asserts the scan catches it (proves the scan does work, not
  just exits 0 silently), and (e) verifies each sub-pack's authored
  marketplace files (PLUGIN.json, README, settings snippet) are
  present at the repo-root marketplace/.

Refs #321

* feat(#321): release-tag extraction CI workflow

- .github/workflows/extract-subpacks-on-release.yml — fires on every
  v* tag push (cut by /release) and on PRs touching extraction-
  relevant files. Runs bin/extract-subpacks.sh, then runs the
  smoke test, then uploads marketplace/ as a build artefact when
  the trigger is a release tag (90-day retention).
- The publish step (push to Claude Code marketplace) remains a
  manual operator concern in v1 — the workflow's job summary lists
  the next steps with the tag name + upstream SHA so the operator
  can take the artefact from the run and push it to the marketplace
  with the right semver.
- Per-PR mode catches contributors who break the extraction
  contract (e.g. an audit skill that adds a portfolio dependency)
  at PR time rather than at release time.

See AgDR-0049 for the rationale on release-tag-driven vs every-PR
auto-publish (the marketplace doesn't want a release per PR; every
WIP commit landing on real users is the wrong shape).

Refs #321

* docs: AgDR-0049 — marketplace sub-packs as framework funnel

Records the strategic + maintenance decisions behind the two
marketplace sub-packs (apexyard/audit-pack and apexyard/safety-hooks):

- Two-sub-pack scope vs alternatives (single mega-plugin, more
  sub-packs in v1, /rex + /migrations sub-packs)
- Generated-not-forked maintenance contract — sub-packs are
  extracted from upstream HEAD at release time, NOT separately
  maintained codebases; the framework stays single source of truth
- Release-tag-driven CI workflow + manual operator publish step
  (release-tag-only in v1; automated publish deferred to v2)
- Funnel direction is one-way (plugin → framework); the README
  pitches but does not pressure
- Performance contract — same files serve both distribution
  channels; the smoke test mechanically asserts no framework-
  distinctive elements (portfolio registry, _lib-portfolio-paths.sh,
  /handover skill, role definitions) leak into the extracted output
- Why /rex and /migrations are deferred — session-state convention
  and migration-ticket dependencies respectively don't survive
  extraction into a drop-in shape without losing the gate's value

Closes #321

* fix: shellcheck SC2064 trap-expansion + markdownlint MD051 link-fragment slugs

Two CI failures on initial #344 push:

1. shellcheck SC2064 in test_subpack_extraction.sh:34 — double-quoted
   trap expanded $TMP_ROOT at definition time rather than signal time.
   Swap inner/outer quoting (single quotes around the trap body, double
   quotes around the variable) so expansion is deferred. Cleanup now
   resolves the correct path even if TMP_ROOT is reassigned later.

2. markdownlint MD051 in both READMEs — link `#graduation-path-the-full-framework`
   doesn't match heading `## Graduation path — the full framework` because
   GFM slug-generation translates ` — ` (em-dash with spaces) to `--`
   (double dash). Swap the em-dash in the heading to a colon: the slug
   becomes `graduation-path-the-full-framework`, matching the existing
   link. Same fix in both audit-pack and safety-hooks READMEs.

Refs #321

* docs: honest-scope amend AgDR-0049 + audit-pack README per Rex's CHANGES REQUESTED

Rex's review of #344 surfaced a real correctness gap between AgDR-0049's
Decision #4 claim and what the smoke test actually enforces. The leak-scan
is a PATH-scan (catches files at framework-distinctive paths like
_lib-portfolio-paths.sh) but is NOT a CONTENT-scan (doesn't catch SKILL.md
prose mentioning /handover, or _lib-audit-history.sh calling
portfolio_projects_dir). Several extracted files in audit-pack DO carry
such prose references.

Per the operator's chosen path (Rex's option a, honest-scope amend, not
full refactor): acknowledge the limitation in the AgDR + add a "Known
framework references" section to the audit-pack README so adopters know
what they're looking at, while preserving the generated-not-forked
contract (decision #3) that would be contradicted by content-scrubbing.

Changes:

- AgDR-0049 § Decision #4 rewritten — distinguishes path-leak guard
  (mechanically enforced) from content references (deliberate, funnel-
  pointer, graceful-degrade outside an apexyard fork). v2 may revisit if
  adopter friction surfaces.
- marketplace/audit-pack/README.md — new "Known framework references"
  section enumerates the three concrete surfaces Rex found (SKILL.md
  prose hints, _lib-audit-history.sh portfolio_projects_dir fallback,
  broken relative links to upstream docs/agdr/). Frames each as
  intentional + funnel-pointer. Flags v2 as the escape hatch.
- safety-hooks is unaffected — Rex confirmed graceful-degrades correctly.

Smoke test unchanged (path-scan is the right shape for what it catches;
the AgDR amend clarifies what it does and doesn't claim).

Refs #321

---------

Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com>

… SENTINEL nit (me2resh#3)

Post-merge cleanup after the Rex re-review of PR #1. Four blockers
and one nit — all small, all correctness fixes, no scope creep.

N1 — Default-mode contradiction (CRITICAL)
Four files claimed single-project was the default, contradicting
CLAUDE.md, README, onboarding.yaml, docs/multi-project.md, the site,
and 7 of 8 new skills (which all say multi-project is the default).
The commit message for ba892bc literally said "multi-project mode
(default)". These four were the stragglers; they now align:

- apexstack.projects.yaml.example: header comment rewritten to say
  this file is the registry for the default multi-project mode,
  single-project is the opt-in
- workspace/README.md: section order swapped (multi-project first as
  the default, single-project second as opt-in), intro paragraph
  reworded, mode comments in the onboarding.yaml snippet flipped
- projects/README.md: opening paragraph flipped so multi-project is
  described as the default
- .claude/skills/projects/SKILL.md: mode detection table row order
  flipped (multi-project "or missing" is now default), sections
  swapped so multi-project comes first as the default, single-project
  moved below as opt-in, the "how to flip back" prompt reworded

N2 — Roles count
- README.md:166 — "20 software development roles" → "19"
  (actual count: 7 Engineering + 3 Product + 3 Design + 3 Security
  + 3 Data = 19)

N3 — Site file count
- site/index.html:956 — dropped the "79 files · " prefix from the
  tree header line to kill the drift-prone number entirely. The
  descriptive tagline "the runnable + portfolio layers added in v0.1"
  stays. Any time a file is added to the repo, the header no longer
  lies.

Stale SENTINEL comment
- golden-paths/pipelines/ci.yml:93 — the security section comment
  said "SENTINEL — Security Scanning" but the job itself is named
  "Shield: Security" (the Sentinel→Shield rename from PR #1). Fixed
  the comment to match.

What's NOT in this commit
- N4 (PR body "5 skills" + Sentinel/Scout in glossary) — GitHub PR
  bodies are immutable after merge, so this is recorded in the
  tracking issue as NOT FIXABLE.
- Retroactive AgDRs — intentionally skipped per the CEO's call
  (v0.1 doesn't need them backfilled).

Verification
  grep -n "20 software development roles" README.md     → no hits
  grep -n "79 files" site/index.html                    → no hits
  grep -n "SENTINEL" golden-paths/pipelines/ci.yml      → no hits
  grep for "single-project is the default" in the 4 N1 files → no hits

Closes me2resh/apexscript-org#99

Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* feat(#321): scaffold marketplace/audit-pack + safety-hooks layout

- marketplace/audit-pack/ — extracted /launch-check + 8 deep-dive audit
  skills + _lib-audit-history.sh + _lib-read-config.sh + _lib-ops-root.sh
  + AI-crawler registry + 8 audit templates. Includes authored README
  and PLUGIN.json that pitch the full framework as the graduation path.
- marketplace/safety-hooks/ — extracted 7 safety hooks (secrets / main
  push / git-add-all / pre-push / commit-refs / PR-title / branch-name)
  + _lib-tracker.sh (tracker-agnostic) + _lib-read-config.sh +
  _lib-ops-root.sh + _lib-extract-pr.sh + settings.snippet.json showing
  recommended hook wiring. Same funnel-pitching README and PLUGIN.json.
- EXTRACTION_MANIFEST.json in each sub-pack records the upstream SHA
  and file inventory so the "generated, not forked" maintenance
  contract is auditable.
- Strategic intent: a one-way discovery funnel from Claude Code
  marketplace users to full-framework adopters. The two sub-packs are
  genuinely self-contained — no portfolio model, no /handover, no role
  definitions — and pitch the full framework via the README without
  pressuring.

Closes #321

* feat(#321): bin/extract-subpacks.sh + extraction smoke test

- bin/extract-subpacks.sh — idempotent extraction script that copies
  the audit-pack + safety-hooks inventories from upstream HEAD into
  marketplace/<pack>/, writes EXTRACTION_MANIFEST.json with the
  upstream SHA, and supports --dry-run + --manifest-only for CI
  validation. Invokable both locally (operator debugging) and from
  the release-tag CI workflow.
- .claude/hooks/tests/test_subpack_extraction.sh — smoke test that
  (a) runs extraction into a tmp dir, (b) asserts the file inventory
  matches the AgDR-0049 contract for both sub-packs, (c) scans for
  framework-distinctive paths that would indicate a leak
  (apexyard.projects.yaml, _lib-portfolio-paths.sh, /handover skill,
  /agdr skill, role definitions), (d) plants a deliberate leak token
  and asserts the scan catches it (proves the scan does work, not
  just exits 0 silently), and (e) verifies each sub-pack's authored
  marketplace files (PLUGIN.json, README, settings snippet) are
  present at the repo-root marketplace/.

Refs #321

* feat(#321): release-tag extraction CI workflow

- .github/workflows/extract-subpacks-on-release.yml — fires on every
  v* tag push (cut by /release) and on PRs touching extraction-
  relevant files. Runs bin/extract-subpacks.sh, then runs the
  smoke test, then uploads marketplace/ as a build artefact when
  the trigger is a release tag (90-day retention).
- The publish step (push to Claude Code marketplace) remains a
  manual operator concern in v1 — the workflow's job summary lists
  the next steps with the tag name + upstream SHA so the operator
  can take the artefact from the run and push it to the marketplace
  with the right semver.
- Per-PR mode catches contributors who break the extraction
  contract (e.g. an audit skill that adds a portfolio dependency)
  at PR time rather than at release time.

See AgDR-0049 for the rationale on release-tag-driven vs every-PR
auto-publish (the marketplace doesn't want a release per PR; every
WIP commit landing on real users is the wrong shape).

Refs #321

* docs: AgDR-0049 — marketplace sub-packs as framework funnel

Records the strategic + maintenance decisions behind the two
marketplace sub-packs (apexyard/audit-pack and apexyard/safety-hooks):

- Two-sub-pack scope vs alternatives (single mega-plugin, more
  sub-packs in v1, /rex + /migrations sub-packs)
- Generated-not-forked maintenance contract — sub-packs are
  extracted from upstream HEAD at release time, NOT separately
  maintained codebases; the framework stays single source of truth
- Release-tag-driven CI workflow + manual operator publish step
  (release-tag-only in v1; automated publish deferred to v2)
- Funnel direction is one-way (plugin → framework); the README
  pitches but does not pressure
- Performance contract — same files serve both distribution
  channels; the smoke test mechanically asserts no framework-
  distinctive elements (portfolio registry, _lib-portfolio-paths.sh,
  /handover skill, role definitions) leak into the extracted output
- Why /rex and /migrations are deferred — session-state convention
  and migration-ticket dependencies respectively don't survive
  extraction into a drop-in shape without losing the gate's value

Closes #321

* fix: shellcheck SC2064 trap-expansion + markdownlint MD051 link-fragment slugs

Two CI failures on initial #344 push:

1. shellcheck SC2064 in test_subpack_extraction.sh:34 — double-quoted
   trap expanded $TMP_ROOT at definition time rather than signal time.
   Swap inner/outer quoting (single quotes around the trap body, double
   quotes around the variable) so expansion is deferred. Cleanup now
   resolves the correct path even if TMP_ROOT is reassigned later.

2. markdownlint MD051 in both READMEs — link `#graduation-path-the-full-framework`
   doesn't match heading `## Graduation path — the full framework` because
   GFM slug-generation translates ` — ` (em-dash with spaces) to `--`
   (double dash). Swap the em-dash in the heading to a colon: the slug
   becomes `graduation-path-the-full-framework`, matching the existing
   link. Same fix in both audit-pack and safety-hooks READMEs.

Refs #321

* docs: honest-scope amend AgDR-0049 + audit-pack README per Rex's CHANGES REQUESTED

Rex's review of #344 surfaced a real correctness gap between AgDR-0049's
Decision #4 claim and what the smoke test actually enforces. The leak-scan
is a PATH-scan (catches files at framework-distinctive paths like
_lib-portfolio-paths.sh) but is NOT a CONTENT-scan (doesn't catch SKILL.md
prose mentioning /handover, or _lib-audit-history.sh calling
portfolio_projects_dir). Several extracted files in audit-pack DO carry
such prose references.

Per the operator's chosen path (Rex's option a, honest-scope amend, not
full refactor): acknowledge the limitation in the AgDR + add a "Known
framework references" section to the audit-pack README so adopters know
what they're looking at, while preserving the generated-not-forked
contract (decision #3) that would be contradicted by content-scrubbing.

Changes:

- AgDR-0049 § Decision #4 rewritten — distinguishes path-leak guard
  (mechanically enforced) from content references (deliberate, funnel-
  pointer, graceful-degrade outside an apexyard fork). v2 may revisit if
  adopter friction surfaces.
- marketplace/audit-pack/README.md — new "Known framework references"
  section enumerates the three concrete surfaces Rex found (SKILL.md
  prose hints, _lib-audit-history.sh portfolio_projects_dir fallback,
  broken relative links to upstream docs/agdr/). Frames each as
  intentional + funnel-pointer. Flags v2 as the escape hatch.
- safety-hooks is unaffected — Rex confirmed graceful-degrades correctly.

Smoke test unchanged (path-scan is the right shape for what it catches;
the AgDR amend clarifies what it does and doesn't claim).

Refs #321

---------

Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com>