Publish AI setup lane guidance in npm package and installed Codex skills

[BaseInfinity]

Summary

AI_SETUP_LANES.md exists on GitHub main, but the current npm @latest package does not ship it and the installed Codex skill bundle does not expose the Setup A/B lane guidance. This made a real consumer setup confusing: the user referenced Setup B / Codex Spark from the GitHub docs, while the active local $update-wizard / $setup-wizard skill context had no lane document to consult.

Evidence

• GitHub main lists AI_SETUP_LANES.md in the repo root.
• npm view codex-sdlc-wizard version reports 0.7.31.
• npm pack --dry-run --json codex-sdlc-wizard@latest for 0.7.31 lists 48 packaged files and does not include AI_SETUP_LANES.md.
• Local installed bundle check also returned nothing:

find /Users/stefanayala/.codex/skills/codex-sdlc-wizard -maxdepth 2 -name 'AI_SETUP_LANES.md' -print

Why this matters

The README and GitHub repo now discuss setup lanes, but the actual consumer path (npx codex-sdlc-wizard@latest, $setup-wizard, $update-wizard) can leave the agent without the lane contract. In the VisualHUD repo, that caused the agent to initially miss the Setup A vs Setup B distinction and only correct after checking GitHub main directly.

Expected behavior

One of these should be true:

1. Publish AI_SETUP_LANES.md in the npm package and installed skill bundle; or
2. Inline/link the lane rules directly from the setup/update skill docs that agents read at runtime; and
3. Add packaging coverage so npm pack --dry-run fails if README-referenced runtime guidance is omitted from the package.

Acceptance notes

• A consumer running only npx codex-sdlc-wizard@latest should have enough local instructions to decide whether a task is Setup A or Setup B.
• $setup-wizard and $update-wizard should not require browsing GitHub main to discover the lane policy.