Jeremy 4d8e733924 docs: remove internal task codes and add community files (#29) ...

The comments and docs carried labels from our own planning (task u2, v3, l5,
Phase 2e, t8) that mean nothing to a reader of a public repository, and one
design note pointed at a folder that is no longer in the tree. CONTRIBUTING
said main is protected, which is not set up yet.

- Strip the task labels from module comments and test headers (comment text
  only; no code changes). Reword the ai-core crate comment to say the
  contract is provisional pending craft-libs review.
- Rename docs/design/u2-declarative-adapter.md to declarative-adapter.md,
  point it at tools/mutation, and update the three references.
- CONTRIBUTING: say changes arrive by pull request instead of claiming a
  protection that is not configured; make the build advice about local
  convenience, not a rule.
- Add SECURITY.md (private reporting through GitHub), issue forms, a pull
  request template and .gitattributes (LF in the repository).

Checked: cargo fmt --all --check, cargo check -p craft-ai-core -p
craft-ai-egui, and mutation_check.py --dry on all 14 groups (every case still
has exactly one target). CI runs the rest.

2026-10-17 10:01:12 +01:00

..

declarative-adapter.md

docs: remove internal task codes and add community files (#29)

2026-10-17 10:01:12 +01:00