feat: add docs checker for ADRs and implementation plans (#1)

Add cmd/docs, the first corestack component: `docs new adr|plan "Title"`
writes records from embedded templates, and `docs check` validates them
against the public format spec in docs/docs-format.md (timestamp IDs,
frontmatter keys and enums, separate decision and implementation status,
supersession symmetry, MADR 4 layout with required Consequences, plan
sections, and repo-root/durable references), reporting path:line errors.

Also adds the module skeleton (go.auvem.com/corestack, BSD-3-Clause,
README, AGENTS.md, CLAUDE.md), Gitea CI running tests and docs check,
a tag-triggered goreleaser release for darwin/linux binaries, and the
accepted ADR adopting the format.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

README.md

@@ -1 +1,29 @@
 # corestack go
+
+Shared Go building blocks. The first one is `docs`, a checker for architecture decision records (ADRs) and implementation plans.
+
+## docs
+
+Install:
+
+```sh
+go install go.auvem.com/corestack/cmd/docs@latest
+```
+
+Use, from a repository root:
+
+```sh
+docs new adr "Use Example Queue for background jobs"   # creates docs/adr/<id>.md
+docs new plan "Adopt Example Queue"                    # creates docs/plans/<id>.md
+docs check [--root DIR]                                # prints path:line: message; exit 1 on problems
+```
+
+The format is specified in [docs/docs-format.md](docs/docs-format.md); that document is the complete rule set. Exit status is `0` when every record is valid, `1` when problems are reported and `2` for usage errors.
+
+## Status
+
+No support is guaranteed. Breaking changes, including to the format rules, may happen before 1.0 and are listed in the release notes.
+
+## License
+
+BSD-3-Clause, see [LICENSE](LICENSE).