feat(bundle)!: pivot skill to anc; vendor agentnative-spec; delete duplicate shell checker

.github/CODEOWNERS

@@ -1,8 +1,8 @@
-# Mandatory review on anything that runs on user machines at install time, and
-# on producer ops that determine what ships.
-# See: master plan risk row "Shell scripts in producer repo execute on user machines".
+# Mandatory review on producer-ops paths that determine what ships and how.
+# The bundle/ tree is content (markdown + templates) and is reviewed via normal
+# PR rules; bundle/spec/ specifically is vendored and not edited by hand
+# (see scripts/sync-spec.sh and bundle/spec/README.md).
 
-bundle/scripts/**       @brettdavies
 scripts/**              @brettdavies
 .github/workflows/**    @brettdavies
 .github/rulesets/**     @brettdavies

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,39 +1,47 @@
 ---
 name: Bug report
-about: A check produces wrong results, a script fails, or a doc says one thing while the code does another.
+about: A bundle file has a wrong example, a stale path, a broken cross-reference, or contradicts the spec.
 title: "bug: <short description>"
 labels: bug
 ---
 
+<!--
+Before filing:
+
+- For bugs in `anc` (the checker itself, e.g. wrong scorecard, missing check), file at
+  https://github.com/brettdavies/agentnative-cli/issues
+- For substantive principle changes (new principles, MUST/SHOULD/MAY tier changes), file at
+  https://github.com/brettdavies/agentnative/issues
+- This tracker is for skill-bundle bugs: stale templates, broken links, wrong invocations in `getting-started.md`, drift
+  between vendored spec and other bundle docs, etc.
+-->
+
 ## What happened
 
-<!-- One or two sentences. Include the command you ran and the unexpected behavior. -->
+<!-- One or two sentences. Include the file, the cited example, and the unexpected behavior. -->
 
 ## What you expected
 
-<!-- One sentence — what should the bundle have done instead? -->
+<!-- One sentence — what should the bundle have said or done instead? -->
 
 ## How to reproduce
 
 1. 1. 1.
 
 ```bash
-# exact commands; redact paths/credentials
+# exact commands or quoted bundle content; redact paths/credentials
 ```
 
 ## Environment
 
 - Bundle version (`cat bundle/VERSION` if cloned, or the tag you installed): vX.Y.Z
+- Pinned spec version (`cat bundle/spec/VERSION`): vX.Y.Z
 - Host (Claude Code / Cursor / Codex / other):
-- Target tool the checker was run against (if applicable): owner/repo @ commit
+- `anc --version` (if a workflow involving anc is at issue):
 - OS and shell:
-- `bundle/scripts/check-compliance.sh --principle N` output (if relevant):
-
-```text
-<paste relevant scorecard rows or error output>
-```
 
-## Why this is a bundle bug, not a target-tool bug
+## Why this is a bundle bug, not a spec or anc bug
 
-<!-- Optional but very useful. If a check fails on a tool that you believe is correctly implementing the principle,
-     explain why. Cite the relevant section of bundle/SKILL.md or bundle/references/principles-deep-dive.md. -->
+<!-- Optional but very useful. If a getting-started flow doesn't work, explain whether the breakage is in this
+     bundle's prose (fixable here) vs. in anc's behavior (file in agentnative-cli) vs. in the principle text
+     itself (file in agentnative-spec). -->

.github/ISSUE_TEMPLATE/bundle_proposal.md

@@ -0,0 +1,66 @@
+---
+name: Bundle proposal
+about: Propose a new template, reference doc, getting-started flow, or other change to the skill bundle.
+title: "proposal: <short description>"
+labels: proposal
+---
+
+<!--
+Route check before filing:
+
+- New principle, MUST/SHOULD/MAY tier change, or any substantive change to the standard itself → file at
+  https://github.com/brettdavies/agentnative/issues (the spec repo). This skill bundle vendors the spec; principle
+  changes happen there first, then arrive here via `scripts/sync-spec.sh`.
+
+- New compliance check, change to scorecard semantics, or anything `anc check` does → file at
+  https://github.com/brettdavies/agentnative-cli/issues (the checker).
+
+- New starter template, reference doc, getting-started flow, idiom for a new language/framework, or any change to how
+  this bundle teaches the existing principles → keep filing here.
+-->
+
+## Problem statement
+
+<!-- What is the problem this proposal addresses? Be specific about which agent's workflow it would improve.
+     Cite real tools, real PRs, or real `anc` findings where relevant. -->
+
+## Proposal
+
+<!-- One paragraph: what should the bundle do that it does not do today? Frame as a concrete change to one or more
+     of: bundle/SKILL.md, bundle/getting-started.md, bundle/references/<file>, bundle/templates/<file>. -->
+
+## Type of change
+
+- [ ] New starter template under `bundle/templates/`
+- [ ] New reference doc under `bundle/references/`
+- [ ] Update to `bundle/SKILL.md` (entry-point structure or routing)
+- [ ] Update to `bundle/getting-started.md` (new flow, new invocation)
+- [ ] Idioms for a new language/framework in `bundle/references/framework-idioms-other-languages.md`
+- [ ] Other (describe)
+
+## Prior art
+
+<!-- Existing tools, docs, or articles that demonstrate the problem or the proposed solution. Two or three is fine. -->
+
+- -
+
+## Draft of the change
+
+<!-- Sketch what the relevant bundle file(s) would look like after the change. A diff against the current state is
+     ideal; an outline is acceptable for early-stage proposals. -->
+
+```diff
+<!-- bundle/<file> -->
+```
+
+## Compatibility
+
+- [ ] Additive — no existing bundle content needs to change
+- [ ] Replaces existing content — list what gets removed/superseded
+- [ ] Coordinated with a spec or anc change — link the upstream issue/PR
+
+## Open questions
+
+<!-- Anything you're unsure about. Decisions to make in the issue thread before any PR. -->
+
+-

.github/workflows/ci.yml

@@ -41,17 +41,12 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
-      - name: Run ShellCheck (bundle scripts — ship to consumers)
-        uses: ludeeus/action-shellcheck@00cae500b08a931fb5698e11e79bfbd38e612a38 # 2.0.0
-        env:
-          # style severity surfaces all suggestions; CI fails on error+warning by default
-          SHELLCHECK_OPTS: "--severity=style"
-        with:
-          scandir: ./bundle/scripts
-          additional_files: bundle/scripts/checks/_helpers.sh
       - name: Run ShellCheck (producer scripts)
+        # The bundle is markdown-only (spec, references, templates, getting-started).
+        # Only producer-ops scripts under ./scripts/ are subject to shellcheck.
         uses: ludeeus/action-shellcheck@00cae500b08a931fb5698e11e79bfbd38e612a38 # 2.0.0
         env:
+          # style severity surfaces all suggestions; CI fails on error+warning by default
           SHELLCHECK_OPTS: "--severity=style"
         with:
           scandir: ./scripts

.markdownlint-cli2.yaml

@@ -80,6 +80,9 @@ ignores:
   - "target/**"  # Rust build artifacts; harmless for non-Rust projects
   - ".git/**"
   - "*.min.md"
+  # Vendored agentnative-spec content. Edited upstream; we do not enforce
+  # this repo's lint rules on it. Resync via scripts/sync-spec.sh.
+  - "bundle/spec/CHANGELOG.md"
 
 # Fix automatically when --fix is used
 fix: true