refactor: migrate Markdown to AsciiDoc

CHANGELOG.adoc

@@ -0,0 +1,45 @@
+== Changelog
+
+All notable changes to `+veridical-simulation-core+` will be documented
+in this file.
+
+This file is generated from conventional commits by the
+https://github.com/hyperpolymath/standards/blob/main/.github/workflows/changelog-reusable.yml[`+changelog-reusable.yml+`]
+workflow (`+hyperpolymath/standards#206+`). Adopt the workflow in this
+repo’s CI to keep this file in sync automatically — see
+https://github.com/hyperpolymath/standards/blob/main/templates/cliff.toml[`+templates/cliff.toml+`]
+for the canonical config.
+
+The format follows https://keepachangelog.com/en/1.1.0/[Keep a
+Changelog]; this project aims to follow
+https://semver.org/spec/v2.0.0.html[Semantic Versioning].
+
+=== [Unreleased]
+
+==== Added
+
+* feat(proofs): per-phase Idris2 bundles + echidnabot priorities for all
+six phases
+* feat(veridical-simulation): Phase 4 reversibility cluster +
+cross-cutting library extraction
+* feat: bootstrap veridical-simulation-core for Phase 2/3 (Agda)
+
+==== Documentation
+
+* docs: adopt docs-template/ skeleton
+(architecture/usage/contributing/troubleshooting + ADR) (#8)
+* docs: record tech-debt audit findings (2026-05-26) (#6)
+
+==== CI
+
+* ci(spark): adopt estate SPARK Theatre Gate (standards#135) (#1)
+
+=== Pre-history
+
+Prior commits to this file’s introduction are recorded in git history
+but not formally classified into Keep-a-Changelog sections. To backfill,
+run `+git cliff -o CHANGELOG.md+` locally using the canonical
+https://github.com/hyperpolymath/standards/blob/main/templates/cliff.toml[`+cliff.toml+`]
+— this is one-shot mechanical work.
+
+'''''

CONTRIBUTING.adoc

@@ -0,0 +1,75 @@
+== Contributing to veridical-simulation-core
+
+Thanks for your interest. This repository follows the Hyperpolymath
+estate standards defined in
+https://github.com/hyperpolymath/standards[hyperpolymath/standards].
+
+=== Licence
+
+This project is licensed under *MPL-2.0*. By contributing you agree that
+your contributions are licensed under the same terms. Every source file
+carries an `+SPDX-License-Identifier+` header; keep it when editing, and
+add one to any new file.
+
+=== Development environment
+
+A pinned dev shell is provided:
+
+[source,sh]
+----
+nix develop        # toolchain: just cargo rustc rustfmt clippy
+----
+
+Estate policy is Guix primary / Nix fallback; this repo currently ships
+the Nix fallback. A `+guix.scm+` is welcome if you prefer the primary
+tier.
+
+=== Build and test
+
+This repo uses https://just.systems[`+just+`] (the estate uses
+Justfiles, never Makefiles). Recipes available here:
+
+[source,sh]
+----
+just            # list recipes
+just fmt        # format
+just fmt-check  # check formatting
+just lint       # lint
+just test-all   # run the full suite
+just doctor     # environment diagnostics
+----
+
+=== Machine-readable artefacts
+
+This repo carries `+.machine_readable/+` A2ML files (`+STATE.a2ml+`,
+`+META.a2ml+`, `+ECOSYSTEM.a2ml+`, `+AGENTIC.a2ml+`, `+NEUROSYM.a2ml+`,
+`+PLAYBOOK.a2ml+`). If your change alters project state, architecture,
+or operational steps, update the corresponding file in the same PR — CI
+validates them.
+
+=== Language policy
+
+The estate restricts which languages may be used. In particular Python,
+Go, TypeScript, ReScript, V-lang, Java/Kotlin, Swift and Makefiles are
+*not* accepted in new code; AffineScript, Rust/SPARK, Zig, Deno, Gleam,
+Elixir, Haskell, Idris2, Agda, Julia and OCaml are. CI enforces this, so
+check the policy in `+hyperpolymath/standards+` before introducing a new
+language.
+
+=== Documentation format
+
+Docs are AsciiDoc (`+.adoc+`) by default, including `+README.adoc+`. The
+GitHub-required community-health files stay Markdown: `+SECURITY.md+`,
+`+CONTRIBUTING.md+`, `+CODE_OF_CONDUCT.md+`, `+CHANGELOG.md+`. Do not
+add a `+.md+` duplicate of a doc that already exists as `+.adoc+`.
+
+=== Pull requests
+
+[arabic]
+. Branch from `+main+` — do not push to `+main+` directly; branch
+protection requires review and passing checks.
+. Keep the change focused, and explain _why_ in the PR body.
+. Make sure governance CI is green. It checks documentation presence,
+packaging policy, secrets, licence consistency and workflow security.
+. Security issues: follow `+SECURITY.md+` — report privately, never in a
+public issue.