docs: license pack, public agent guides, community templates (#105)

## Summary

Phase A of the OSS-ready program (approved plan, 7 Codex review rounds):
adds the repository's licensing posture and rewrites the public
contributor surface.

- **LICENSE**: official PolyForm Noncommercial 1.0.0 text with the
Required Notice line — code is free for noncommercial use; commercial
use requires a separate license.
- **NOTICE**: separates first-party excluded assets (all rights
reserved) from third-party materials governed by their own embedded
terms (fonts, the four proprietary skills, the shared office tree);
nominative-use statement; commercial contact.
- **29 manifests** gain `license` fields; root description now says
*source-available*; the five skills that claimed MIT now carry the
repository license.
- **AGENTS.md** rewritten from scratch as the canonical public
contributor/agent guide (agents.md convention) — stack, layout, gates,
house naming contracts, BYOK and DB-role boundaries, migration safety,
neutral verification policy. All private operator prose removed.
**CLAUDE.md** is now a thin `@AGENTS.md` import.
- **Community files**: Contributor Covenant 2.1, bug/feature issue
forms, PR template with a verification-notes checklist.
- One UI comment reworded to describe its real constraint.

## Verification notes

- [x] `pnpm lint`
- [x] `pnpm typecheck`
- [x] `pnpm turbo build --force`
- [x] `pnpm deadcode`
- [x] `pnpm architecture:check`
- [x] `pnpm turbo skills:build`

Docs-only + comment reword + manifest metadata: no runtime behavior
changes, so no browser QA applies. LICENSE body verified against the
official polyformproject.org plain text (wrap-insensitive match); every
path asserted in AGENTS.md verified to exist.

Author: iamjr15

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,53 @@
+name: Bug report
+description: Report a reproducible problem with Cheatcode
+title: "[Bug]: "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a problem. Please avoid including credentials, provider keys, or other sensitive data.
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      description: Describe the problem and what you expected to happen.
+      placeholder: A clear, concise description of the problem.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Give the smallest reliable sequence that reproduces the problem.
+      placeholder: |
+        1. Go to ...
+        2. Select ...
+        3. Observe ...
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Include the browser, operating system, Node.js version, and deployment context when relevant.
+      placeholder: Chrome 140, macOS 16, Node.js 24.18.0, local development
+    validations:
+      required: true
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add sanitized logs, screenshots, or other details that may help diagnose the problem.
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues for the same problem.
+          required: true
+        - label: I removed credentials, provider keys, and other sensitive data from this report.
+          required: true
+        - label: I agree to follow this repository's Code of Conduct.
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,45 @@
+name: Feature request
+description: Suggest an improvement for Cheatcode
+title: "[Feature]: "
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping improve Cheatcode. Explain the user need before proposing implementation details.
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or opportunity
+      description: What user need, limitation, or opportunity should this change address?
+      placeholder: Describe who is affected and why the current experience is insufficient.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed outcome
+      description: Describe the behavior or outcome you would like to see.
+      placeholder: A clear, concise description of the desired result.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Share workarounds or alternative approaches you considered.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add mockups, examples, or related links. Do not include credentials or sensitive data.
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues for a similar request.
+          required: true
+        - label: I agree to follow this repository's Code of Conduct.
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,16 @@
+## Summary
+
+<!-- Explain what changed, why it changed, and any relevant issue or architectural decision. -->
+
+## Verification notes
+
+<!-- Mark every gate you ran. If a gate is not applicable, explain why. -->
+
+- [ ] `pnpm lint`
+- [ ] `pnpm typecheck`
+- [ ] `pnpm turbo build --force`
+- [ ] `pnpm deadcode`
+- [ ] `pnpm architecture:check`
+- [ ] `pnpm turbo skills:build`
+
+<!-- For behavior changes, describe the real user flow exercised through direct browser QA and summarize console, network, and application-log review. If browser QA is not applicable, say why. -->