release: v0.2.0 — agent-native CLI skill bundle public launch

.github/CODEOWNERS

@@ -1,6 +1,9 @@
-# Mandatory review on anything that runs on user machines at install time.
-# 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).
 
-scripts/**             @brettdavies
-.github/workflows/**   @brettdavies
-.github/CODEOWNERS     @brettdavies
+scripts/**              @brettdavies
+.github/workflows/**    @brettdavies
+.github/rulesets/**     @brettdavies
+.github/CODEOWNERS      @brettdavies

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+---
+name: Bug report
+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 file, the cited example, and the unexpected behavior. -->
+
+## What you expected
+
+<!-- One sentence — what should the bundle have said or done instead? -->
+
+## How to reproduce
+
+1. 1. 1.
+
+```bash
+# exact commands or quoted bundle content; redact paths/credentials
+```
+
+## Environment
+
+- Bundle version (`cat VERSION` if cloned, or the tag you installed): vX.Y.Z
+- Pinned spec version (`cat spec/VERSION`): vX.Y.Z
+- Host (Claude Code / Cursor / Codex / other):
+- `anc --version` (if a workflow involving anc is at issue):
+- OS and shell:
+
+## Why this is a bundle bug, not a spec or anc bug
+
+<!-- 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: SKILL.md, getting-started.md, references/<file>, templates/<file>. -->
+
+## Type of change
+
+- [ ] New starter template under `templates/`
+- [ ] New reference doc under `references/`
+- [ ] Update to `SKILL.md` (entry-point structure or routing)
+- [ ] Update to `getting-started.md` (new flow, new invocation)
+- [ ] Idioms for a new language/framework in `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
+<!-- <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/pull_request_template.md

@@ -0,0 +1,151 @@
+## Summary
+
+<!-- Provide a brief overview of the changes in this PR. What feature/fix/improvement does this introduce? -->
+
+## Changelog
+
+<!-- CRITICAL: This section is the source of truth for CHANGELOG.md.
+     generate-changelog.sh extracts these categorized bullets verbatim
+     into the release changelog. Write carefully — this IS the changelog.
+
+     AUDIENCE: Users and operators. Write from their perspective.
+
+     INCLUDE: new features, changed behavior, breaking changes, fixed bugs,
+     new/removed config, new dependencies users need to know about.
+
+     EXCLUDE: internal refactors, test additions, code cleanup, CI changes,
+     regenerated files, implementation details (unreachable!() arms, import
+     reordering, cargo_bin migration, cfg gates, etc.). Document those in
+     the PR body text or Files Modified section — NOT here.
+
+     RULES:
+- 1-5 bullets per PR. Fewer is better. One-line fixes get one bullet.
+- Delete empty ### sections entirely — don't leave blank categories.
+- Each bullet starts with a verb: Add, Fix, Change, Remove, Deprecate.
+- Don't duplicate the PR title — expand on it or provide context.
+- If the PR has NO user-facing changes (pure refactor, test-only, CI), leave this section empty or omit it. The PR still
+  appears in git history; it just won't clutter the changelog. -->
+
+### Added
+
+-
+
+### Changed
+
+-
+
+### Fixed
+
+-
+
+### Documentation
+
+-
+
+## Type of Change
+
+<!-- Check the type that applies to this PR -->
+
+- [ ] `feat`: New feature (non-breaking change which adds functionality)
+- [ ] `fix`: Bug fix (non-breaking change which fixes an issue)
+- [ ] `refactor`: Code refactoring (no functional changes)
+- [ ] `perf`: Performance improvement
+- [ ] `docs`: Documentation update
+- [ ] `test`: Adding or updating tests
+- [ ] `chore`: Maintenance tasks (dependencies, config, etc.)
+- [ ] `ci`: CI/CD configuration changes
+- [ ] `style`: Code style/formatting changes
+- [ ] `build`: Build system changes
+- [ ] `BREAKING CHANGE`: Breaking API change (requires major version bump)
+
+## Related Issues/Stories
+
+<!-- Link to related issues, stories, or documentation -->
+
+- Story:
+- Issue:
+- Architecture:
+- Related PRs:
+
+## Testing
+
+<!-- Describe the testing approach and results -->
+
+- [ ] Unit tests added/updated
+- [ ] Integration tests added/updated
+- [ ] Manual testing completed
+- [ ] All tests passing
+
+**Test Summary:**
+
+- Unit tests: X passing
+- Integration tests: Y passing
+- Coverage: Z%
+
+## Files Modified
+
+<!-- List the main files modified in this PR -->
+
+**Modified:**
+
+**Created:**
+
+**Renamed:**
+
+**Deleted:**
+
+## Key Features
+
+<!-- Optional: Highlight key features or capabilities introduced -->
+
+-
+
+## Benefits
+
+<!-- Optional: Describe the benefits (performance, security, compliance, UX, etc.) -->
+
+-
+
+## Breaking Changes
+
+<!-- If this PR contains breaking changes, describe them and the migration path -->
+
+- [ ] No breaking changes
+- [ ] Breaking changes described below:
+
+## Deployment Notes
+
+<!-- Any special deployment considerations, migrations, or configuration changes needed -->
+
+- [ ] No special deployment steps required
+- [ ] Deployment steps documented below:
+
+## Screenshots/Recordings
+
+<!-- Optional: Add screenshots or recordings for UI changes -->
+
+## Checklist
+
+- [ ] Code follows project conventions and style guidelines
+- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)
+- [ ] Self-review of code completed
+- [ ] Tests added/updated and passing
+- [ ] No new warnings or errors introduced
+- [ ] Changes are backward compatible (or breaking changes documented)
+
+## Additional Context
+
+<!-- Optional: Add any additional context, screenshots, or information -->
+
+---
+
+<!--
+PR Title Format: <type>(<scope>): <description>
+
+Examples:
+- feat(auth): add OAuth2 authentication provider
+- fix(api): resolve rate limiting edge case
+- docs(readme): update installation instructions
+- refactor(db): optimize query performance
+- chore(deps): upgrade to bun 1.3.1
+-->

.github/rulesets/protect-dev.json

@@ -0,0 +1,31 @@
+{
+  "name": "Protect dev",
+  "target": "branch",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "exclude": [],
+      "include": [
+        "refs/heads/dev"
+      ]
+    }
+  },
+  "rules": [
+    {
+      "type": "deletion"
+    },
+    {
+      "type": "non_fast_forward"
+    },
+    {
+      "type": "required_signatures"
+    }
+  ],
+  "bypass_actors": [
+    {
+      "actor_id": 5,
+      "actor_type": "RepositoryRole",
+      "bypass_mode": "always"
+    }
+  ]
+}

.github/rulesets/protect-main.json

@@ -0,0 +1,69 @@
+{
+  "name": "Protect main",
+  "target": "branch",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "exclude": [],
+      "include": [
+        "refs/heads/main"
+      ]
+    }
+  },
+  "rules": [
+    {
+      "type": "creation"
+    },
+    {
+      "type": "deletion"
+    },
+    {
+      "type": "non_fast_forward"
+    },
+    {
+      "type": "pull_request",
+      "parameters": {
+        "required_approving_review_count": 0,
+        "dismiss_stale_reviews_on_push": false,
+        "required_reviewers": [],
+        "require_code_owner_review": true,
+        "require_last_push_approval": false,
+        "required_review_thread_resolution": false,
+        "allowed_merge_methods": [
+          "squash"
+        ]
+      }
+    },
+    {
+      "type": "required_signatures"
+    },
+    {
+      "type": "required_status_checks",
+      "parameters": {
+        "strict_required_status_checks_policy": true,
+        "do_not_enforce_on_create": false,
+        "required_status_checks": [
+          {
+            "context": "markdownlint"
+          },
+          {
+            "context": "shellcheck"
+          },
+          {
+            "context": "guard-docs / check-forbidden-docs"
+          }
+        ]
+      }
+    },
+    {
+      "type": "required_linear_history"
+    }
+  ],
+  "bypass_actors": [
+    {
+      "actor_id": 5,
+      "actor_type": "RepositoryRole",
+      "bypass_mode": "always"
+    }
+  ]
+}