fix: instantiate knot-rider from the RSR template (#17)

## Summary

`knot-rider` was scaffolded from `rsr-template-repo` but never
instantiated — `{{PLACEHOLDER}}` tokens survived throughout, including
in the `.zig` sources, so the Zig FFI seam genuinely did not parse. This
PR cures the instantiation for real.

- **Identity placeholders substituted** across ~80 files
(`{{PROJECT_NAME}}`, `{{OWNER}}`, `{{REPO}}`, `{{AUTHOR}}`, `{{FORGE}}`,
`{{LICENSE}}`, etc.) — real values used throughout, intentional generic
scaffolding (`docs-template/`, ADR templates, K9 example configs, native
Justfile `{{recipe}}` interpolation) left untouched.
- **`.github/settings.yml` landmine fixed**: an unsubstituted `name:
"{{REPO}}"` under the probot/settings config would have made the app try
to rename the repo to the literal string `{{REPO}}` on the next push to
`main`.
- **Zig FFI seam now genuinely builds and tests**: `{{project}}_*` →
`knot_rider_*`, plus two real Zig 0.16 incompatibilities fixed along the
way (`opaque` types can no longer carry fields; `callconv(.C)` →
`callconv(.c)`). `build.zig` was previously inert scaffolding with zero
real build targets — rewrote it to actually compile `main.zig` as a
static library and wire `zig build test` to the real test suites. `zig
fmt --check`, `zig build`, and `zig build test` all pass (4/4 tests).
- **`.machine_readable/6a2/{CLADE,ECOSYSTEM,STATE}.a2ml`** still
described `rsr-template-repo`'s own identity/purpose/"95% complete,
production maturity" claim — hardcoded wrong content, not a `{{}}`
token. Fixed the fields that feed the `CLAUDE.md` arrival-pack
generator, then regenerated `CLAUDE.md` for real via `just claude-md`
rather than hand-editing the generated region.
- **Justfile TODO/echo stubs rewired to real commands**:
`build`/`test`/`fmt`/`fmt-check` → real `zig build`/`zig build
test`/`zig fmt`; `lint` → `idris2 --typecheck abi.ipkg`; `e2e`/`aspect`
→ `bash tests/e2e.sh` / `bash tests/aspect_tests.sh`; `deps` → checks
the Zig toolchain. Deleted `run`/`run-verbose`/`bench`/`readiness`
recipes rather than leave `echo "..."` fake-pass stubs — this repo is a
C-ABI library with no application entry point and no bench/readiness
suite exists.
- **Two real false positives fixed in `tests/aspect_tests.sh`** that the
newly-wired `aspect` recipe surfaced: documentation prose describing
banned patterns (`sorry`, `Admitted`) was being flagged as a violation,
and Zig build-cache files were being scanned for SPDX headers. `just
test-all` / `just quality` are genuinely green now, not just
newly-wired-but-red.
- **Removed obsolete template machinery**:
`scripts/validate-template.sh`,
`tests/e2e/template_instantiation_test.sh`, `benches/template_bench.sh`,
`.machine_readable/ai/PLACEHOLDERS.adoc`. No workflow referenced any of
them (re-verified).
- **README/EXPLAINME/AFFIRMATION rewritten honestly.**

## This project's purpose remains undocumented

This is deliberate, not an oversight. `knot-rider`'s specific technical
purpose is not documented anywhere in this repository or the wider
hyperpolymath estate registry (checked: `reposystem` tool registry,
`verisimdb-data`, `gitbot-fleet`, estate memory). The only repo-specific
content that exists is GitHub's own description, a knowing pun on the
*Knight Rider* intro monologue:

> A shadowy flight into the dangerous world of a man, who is either
permanently or very often undone by circumstance.

That's wordplay, not a spec. README.adoc says this plainly rather than
inventing a product story.

## Known, out-of-scope findings (not fixed here)

- The literal string `rsr-template-repo` (not a `{{}}` placeholder, so
outside this PR's defined scope) still appears as leftover
self-referential text in ~40 files under
`.machine_readable/contractiles/`, `docs/onboarding/`, `docs/status/`,
`.machine_readable/coaptation/`, etc. I fixed the highest-impact
instances (the ones feeding `CLAUDE.md`, the Justfile's user-facing
`doctor`/`tour` output, and de-duplicated
`.machine_readable/contractiles/Justfile` back into a hardlink of the
root Justfile per its own dust-check). A full sweep of this second bug
class would roughly double the size of this change and is a reasonable
follow-up.
- `docs/status/TEST-NEEDS.adoc` describes `rsr-template-repo`'s own
historical test-suite development (not knot-rider's) — left as-is,
flagged as stale.
- `idris2 --typecheck abi.ipkg` was verified to pass in this environment
(exit 0, warnings only), but this wasn't part of the original ask and
toolchain availability may differ elsewhere.

## Test plan

- [x] `zig fmt --check src/interface/ffi` — exit 0
- [x] `cd src/interface/ffi && zig build` — exit 0
- [x] `cd src/interface/ffi && zig build test` — exit 0, 4/4 tests pass
- [x] `just quality` (fmt-check + lint + test) — exit 0
- [x] `just test-all` (test + e2e + aspect) — exit 0
- [x] `just claude-md && just validate-claude-md` — in sync
- [x] Edited workflow YAML re-parsed with `python3 -c "import yaml;
yaml.safe_load(...)"`
- [x] Grepped for lingering `.github/workflows/*.yml` references to the
deleted template-machinery scripts — none found

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: hyperpolymath

.devcontainer/Containerfile

@@ -1,9 +1,9 @@
 # SPDX-License-Identifier: MPL-2.0
-# Copyright (c) {{CURRENT_YEAR}} {{AUTHOR}} ({{OWNER}}) <{{AUTHOR_EMAIL}}>
+# Copyright (c) 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
 #
-# Dev Container image for {{PROJECT_NAME}}
+# Dev Container image for knot-rider
 # Base: Chainguard Wolfi (minimal, supply-chain-secure)
-# Build: podman build -t {{PROJECT_NAME}}-dev -f .devcontainer/Containerfile .
+# Build: podman build -t knot-rider-dev -f .devcontainer/Containerfile .
 # `:latest` suits a dev container (rebuilt daily); pin by digest
 # (...@sha256:<digest>) if you need a reproducible dev environment.
 
@@ -26,7 +26,7 @@ RUN groupadd -g 1000 nonroot || true \
     && useradd -m -u 1000 -g 1000 -s /bin/bash nonroot || true
 
 # Set workspace directory
-WORKDIR /workspaces/{{PROJECT_NAME}}
+WORKDIR /workspaces/knot-rider
 
 # Default shell
 ENV SHELL=/bin/bash

.devcontainer/README.adoc

@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: CC-BY-SA-4.0
 // Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 = Dev Container Usage
-:author: {{AUTHOR}} <{{AUTHOR_EMAIL}}>
+:author: Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 
 == Overview
 
@@ -25,4 +25,4 @@ This dev container uses `cgr.dev/chainguard/wolfi-base` with git, curl, bash, an
 
 == Customization
 
-Replace `{{PROJECT_NAME}}` placeholders in both `devcontainer.json` and `Containerfile` with your actual project name. Run `just deps` to verify the environment after first launch.
+Replace `knot-rider` placeholders in both `devcontainer.json` and `Containerfile` with your actual project name. Run `just deps` to verify the environment after first launch.

.devcontainer/devcontainer.json

@@ -1,11 +1,11 @@
 // SPDX-License-Identifier: MPL-2.0
-// Copyright (c) {{CURRENT_YEAR}} {{AUTHOR}} ({{OWNER}}) <{{AUTHOR_EMAIL}}>
+// Copyright (c) 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
 //
-// Dev Container configuration for {{PROJECT_NAME}}
+// Dev Container configuration for knot-rider
 // Works with: VS Code Dev Containers, GitHub Codespaces, Gitpod
 // Container runtime: Podman (recommended) or any OCI-compliant runtime
 {
-  "name": "{{PROJECT_NAME}}",
+  "name": "knot-rider",
 
   "build": {
     "dockerfile": "Containerfile",

.envrc

@@ -13,7 +13,7 @@ if has guix && [ -f guix.scm ]; then
 fi
 
 # Project environment variables
-export PROJECT_NAME="{{PROJECT_NAME}}"
+export PROJECT_NAME="knot-rider"
 export RSR_TIER="infrastructure"
 # Add non-secret project env vars above (e.g. DATABASE_URL, service endpoints).
 # Real secrets belong in .env (gitignored) — never commit them to .envrc.

.github/.mailmap

@@ -1 +1 @@
-{{AUTHOR}} <{{AUTHOR_EMAIL}}> <{{AUTHOR_EMAIL_ALT}}>
+Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>

.github/CODEOWNERS

@@ -2,13 +2,13 @@
 # CODEOWNERS - Define code review assignments
 # See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
 #
-# Replace {{OWNER}} with your GitHub username or team
+# Replace hyperpolymath with your GitHub username or team
 
 # Default owners for everything
-* @{{OWNER}}
+* @hyperpolymath
 
 # Security-sensitive files require explicit review
-SECURITY.md @{{OWNER}}
-.github/workflows/ @{{OWNER}}
-Trustfile.a2ml @{{OWNER}}
-.machine_readable/ @{{OWNER}}
+SECURITY.md @hyperpolymath
+.github/workflows/ @hyperpolymath
+Trustfile.a2ml @hyperpolymath
+.machine_readable/ @hyperpolymath

.github/CODE_OF_CONDUCT.md

@@ -4,29 +4,14 @@ Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 -->
 # Code of Conduct
 
-<!-- 
-============================================================================
-TEMPLATE INSTRUCTIONS (delete this block before publishing)
-============================================================================
-Replace all {{PLACEHOLDER}} values:
-  {{PROJECT_NAME}}     - Your project name
-  {{OWNER}}            - GitHub/GitLab username or org
-  {{REPO}}             - Repository name
-  {{CONDUCT_EMAIL}}    - Email for conduct reports
-  {{CONDUCT_TEAM}}     - Name of conduct team/committee
-  {{RESPONSE_TIME}}    - Initial response SLA (e.g., 48 hours)
-  {{CURRENT_YEAR}}     - Current year
-
-Review and customise:
-- Adjust enforcement ladder for your community size
-- Add/remove examples based on your context
-- Ensure contact methods work for your team
-============================================================================
--->
+> **Note:** This is a single-maintainer repository. The enforcement ladder
+> below is kept as-written from the RSR community-health template for
+> consistency across the estate; in practice reports go straight to the
+> maintainer.
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in {{PROJECT_NAME}} a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, colour, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in knot-rider a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, colour, religion, or sexual identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
@@ -140,7 +125,7 @@ If you experience or witness unacceptable behaviour, or have any other concerns,
 
 | Method | Details | Best For |
 |--------|---------|----------|
-| **Email** | {{CONDUCT_EMAIL}} | Detailed reports, sensitive matters |
+| **Email** | j.d.a.jewell@open.ac.uk | Detailed reports, sensitive matters |
 | **Private Message** | Contact any maintainer directly | Quick questions, minor issues |
 | **Anonymous Form** | [Link to form if available] | When you need anonymity |
 
@@ -156,8 +141,8 @@ If you experience or witness unacceptable behaviour, or have any other concerns,
 
 **What Happens Next**
 
-1. You will receive acknowledgment within **{{RESPONSE_TIME}}**
-2. The {{CONDUCT_TEAM}} will review the report
+1. You will receive acknowledgment within **5 business days**
+2. The maintainer will review the report
 3. We may ask for additional information
 4. We will determine appropriate action
 5. We will inform you of the outcome (respecting others' privacy)
@@ -173,7 +158,7 @@ All reports will be handled with discretion:
 
 ### Conflicts of Interest
 
-If a {{CONDUCT_TEAM}} member is involved in an incident:
+If the maintainer is involved in an incident:
 
 - They will recuse themselves from the process
 - Another maintainer or external party will handle the report
@@ -183,7 +168,7 @@ If a {{CONDUCT_TEAM}} member is involved in an incident:
 
 ## Enforcement Guidelines
 
-The {{CONDUCT_TEAM}} will follow these guidelines in determining consequences:
+The maintainer will follow these guidelines in determining consequences:
 
 ### 1. Correction
 
@@ -235,13 +220,13 @@ For contributors with elevated access (Perimeter 2 or 1):
 If you believe an enforcement decision was made in error:
 
 1. **Wait 7 days** after the decision (cooling-off period)
-2. **Email** {{CONDUCT_EMAIL}} with subject line "Appeal: [Original Report ID]"
+2. **Email** j.d.a.jewell@open.ac.uk with subject line "Appeal: [Original Report ID]"
 3. **Explain** why you believe the decision should be reconsidered
 4. **Provide** any new information not previously available
 
 **Appeals Process**
 
-- Appeals are reviewed by a different {{CONDUCT_TEAM}} member than the original
+- Appeals are reviewed by a different maintainer than the original, if one is available
 - You will receive a response within 14 days
 - The appeals decision is final
 - You may only appeal once per incident
@@ -314,8 +299,8 @@ We thank these communities for their leadership in creating welcoming spaces.
 
 If you have questions about this Code of Conduct:
 
-- Open a [Discussion](https://{{FORGE}}/{{OWNER}}/{{REPO}}/discussions) (for general questions)
-- Email {{CONDUCT_EMAIL}} (for private questions)
+- Open a [Discussion](https://github.com/hyperpolymath/knot-rider/discussions) (for general questions)
+- Email j.d.a.jewell@open.ac.uk (for private questions)
 - Contact any maintainer directly
 
 ---
@@ -328,4 +313,4 @@ We're all here because we care about this project. Let's make it a place where e
 
 ---
 
-<sub>Last updated: {{CURRENT_YEAR}} · Based on Contributor Covenant 2.1</sub>
+<sub>Last updated: 2026 · Based on Contributor Covenant 2.1</sub>

.github/CONTRIBUTING.md

@@ -3,15 +3,15 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 -->
 # Clone the repository
-git clone https://{{FORGE}}/{{OWNER}}/{{REPO}}.git
-cd {{REPO}}
+git clone https://github.com/hyperpolymath/knot-rider.git
+cd knot-rider
 
 # Using Guix (recommended for reproducibility)
 guix shell -D -f guix.scm
 
 # Or using toolbox/distrobox
-toolbox create {{REPO}}-dev
-toolbox enter {{REPO}}-dev
+toolbox create knot-rider-dev
+toolbox enter knot-rider-dev
 # Install dependencies manually
 
 # Verify setup
@@ -21,7 +21,7 @@ just test    # Run test suite
 
 ### Repository Structure
 ```
-{{REPO}}/
+knot-rider/
 ├── src/                 # Source code (Perimeter 1-2)
 ├── lib/                 # Library code (Perimeter 1-2)
 ├── extensions/          # Extensions (Perimeter 2)
@@ -61,7 +61,7 @@ just test    # Run test suite
 
 **Before reporting**:
 1. Search existing issues
-2. Check if it's already fixed in `{{MAIN_BRANCH}}`
+2. Check if it's already fixed in `main`
 3. Determine which perimeter the bug affects
 
 **When reporting**:
@@ -94,10 +94,10 @@ Use the [feature request template](.github/ISSUE_TEMPLATE/feature_request.md) an
 
 Look for issues labelled:
 
-- [`good first issue`](https://{{FORGE}}/{{OWNER}}/{{REPO}}/labels/good%20first%20issue) — Simple Perimeter 3 tasks
-- [`help wanted`](https://{{FORGE}}/{{OWNER}}/{{REPO}}/labels/help%20wanted) — Community help needed
-- [`documentation`](https://{{FORGE}}/{{OWNER}}/{{REPO}}/labels/documentation) — Docs improvements
-- [`perimeter-3`](https://{{FORGE}}/{{OWNER}}/{{REPO}}/labels/perimeter-3) — Community sandbox scope
+- [`good first issue`](https://github.com/hyperpolymath/knot-rider/labels/good%20first%20issue) — Simple Perimeter 3 tasks
+- [`help wanted`](https://github.com/hyperpolymath/knot-rider/labels/help%20wanted) — Community help needed
+- [`documentation`](https://github.com/hyperpolymath/knot-rider/labels/documentation) — Docs improvements
+- [`perimeter-3`](https://github.com/hyperpolymath/knot-rider/labels/perimeter-3) — Community sandbox scope
 
 ---
 

.github/FUNDING.yml

@@ -1,7 +1,7 @@
 # SPDX-License-Identifier: MPL-2.0
-# Funding platforms for {{OWNER}} projects
+# Funding platforms for hyperpolymath projects
 # See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
 
-github: {{OWNER}}
-ko_fi: {{OWNER}}
-liberapay: {{OWNER}}
+github: hyperpolymath
+ko_fi: hyperpolymath
+liberapay: hyperpolymath

.github/GOVERNANCE.md

@@ -4,13 +4,13 @@ Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 -->
 # Project Governance
 
-This document describes the governance model for **{{PROJECT_NAME}}**.
+This document describes the governance model for **knot-rider**.
 
 ---
 
 ## Project Governance Model
 
-{{PROJECT_NAME}} follows a **Benevolent Dictator For Life (BDFL)** governance model.
+knot-rider follows a **Benevolent Dictator For Life (BDFL)** governance model.
 This model is well-suited for solo maintainers and small project teams where rapid,
 consistent decision-making is more valuable than formal consensus processes.
 
@@ -157,4 +157,4 @@ with the community before adoption, even though the BDFL retains final authority
 
 ---
 
-<sub>Copyright (c) {{CURRENT_YEAR}} {{OWNER}}. Licensed under MPL-2.0.</sub>
+<sub>Copyright (c) 2026 hyperpolymath. Licensed under MPL-2.0.</sub>