fix: instantiate the RSR template placeholders for contractiles

Contractiles was scaffolded from the RSR template but never instantiated:
{{PLACEHOLDER}} tokens (and, separately, the literal string
"rsr-template-repo") survived across ~100 files, including the Zig FFI
source, which genuinely failed to parse (export fn {{project}}_init()).

- Substitute identity placeholders (AUTHOR, OWNER, REPO, PROJECT[_NAME],
  FORGE, CURRENT_YEAR/DATE, LICENSE, etc.) with this repo's real values,
  derived from its own SPDX headers, GitHub metadata, and the A2ML/K9
  ecosystem memory of what "contractiles" (the normative half of the
  contractile/descriptile pattern) actually is.
- De-clobber CODE_OF_CONDUCT.md, which an unrelated estate-wide sweep had
  stamped with a different project's identity ("Squisher Corpus").
- Fix real Zig bugs beyond substitution: `Handle` was an `opaque` type with
  fields (invalid Zig — opaque types cannot have fields), `callconv(.C)` is
  not valid under Zig 0.16 (`.c` is), and `std.heap.c_allocator` requires
  libc, which build.zig never linked. Rewrote build.zig to produce a real
  static-library artifact and wire `zig build test` to both the inline
  unit tests and a genuine integration_test.zig (was a fully-commented
  placeholder). Verified: `zig fmt --check .` exit 0, `zig build` exit 0,
  `zig build test` exit 0 (11/11 tests passing).
- Replace Justfile fake-gate stubs (build/test/e2e/aspect/bench/lint/deps/
  install, all `echo "..."` regardless of outcome) with real invocations
  of `idris2` and `zig`; delete recipes with nothing real to do
  (build-watch's language list, run/run-verbose for a library with no
  executable). tests/e2e.sh gets a real build-the-ABI/build-the-FFI
  pipeline in place of its fully-commented example sections.
- Remove template-only machinery that has no purpose once a repo is
  instantiated: scripts/validate-template.sh,
  tests/e2e/template_instantiation_test.sh,
  .machine_readable/ai/PLACEHOLDERS.adoc, and the corresponding sections
  of benches/template_bench.sh.
- Rewrite README.adoc, SECURITY.md, CODE_OF_CONDUCT.md, security.txt,
  and docs/status/TEST-NEEDS.adoc to describe this repo truthfully;
  drop fabricated-risk fields (PGP fingerprint/key URL, hiring line)
  rather than invent them.

Known residue (left deliberately): container/*, machine-readable-design/
canonical-directory-structure/*, and .machine_readable/configs/{selur-
compose,stapeln}.toml still carry {{SERVICE_NAME}}/{{PORT}}/etc. — these
are legitimate recurring templates substituted by `just container-init`,
not one-time instantiation artifacts (documented in container/README.adoc).
docs/governance/*-AUDIT-TEMPLATE.adoc, .machine_readable/contractiles/
Justfile (a stale duplicate of the root Justfile), and build/just/init.just
(the now-vestigial bootstrap wizard) were not touched.

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 Contractiles
 # Base: Chainguard Wolfi (minimal, supply-chain-secure)
-# Build: podman build -t {{PROJECT_NAME}}-dev -f .devcontainer/Containerfile .
+# Build: podman build -t Contractiles-dev -f .devcontainer/Containerfile .
 
 FROM cgr.dev/chainguard/wolfi-base:latest
 
@@ -24,7 +24,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/Contractiles
 
 # 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 `Contractiles` 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 Contractiles
 // Works with: VS Code Dev Containers, GitHub Codespaces, Gitpod
 // Container runtime: Podman (recommended) or any OCI-compliant runtime
 {
-  "name": "{{PROJECT_NAME}}",
+  "name": "Contractiles",
 
   "build": {
     "dockerfile": "Containerfile",

.envrc

@@ -18,7 +18,7 @@ if has nix && [ -f flake.nix ]; then
 fi
 
 # Project environment variables
-export PROJECT_NAME="{{PROJECT_NAME}}"
+export PROJECT_NAME="Contractiles"
 export RSR_TIER="infrastructure"
 # export DATABASE_URL="..."
 # export API_KEY="..."

.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,9 @@ 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
-============================================================================
--->
-
 ## 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 Contractiles 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 +120,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 +136,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 **48 hours**
+2. The 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 +153,7 @@ All reports will be handled with discretion:
 
 ### Conflicts of Interest
 
-If a {{CONDUCT_TEAM}} member is involved in an incident:
+If a the maintainer member is involved in an incident:
 
 - They will recuse themselves from the process
 - Another maintainer or external party will handle the report
@@ -183,7 +163,7 @@ If a {{CONDUCT_TEAM}} member is involved in an incident:
 
 ## Enforcement Guidelines
 
-The {{CONDUCT_TEAM}} will follow these guidelines in determining consequences:
+The the maintainer will follow these guidelines in determining consequences:
 
 ### 1. Correction
 
@@ -235,13 +215,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 the maintainer member than the original
 - You will receive a response within 14 days
 - The appeals decision is final
 - You may only appeal once per incident
@@ -314,8 +294,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/contractiles/discussions) (for general questions)
+- Email j.d.a.jewell@open.ac.uk (for private questions)
 - Contact any maintainer directly
 
 ---
@@ -328,4 +308,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/contractiles.git
+cd contractiles
 
 # Using Nix (recommended for reproducibility)
 nix develop
 
 # Or using toolbox/distrobox
-toolbox create {{REPO}}-dev
-toolbox enter {{REPO}}-dev
+toolbox create contractiles-dev
+toolbox enter contractiles-dev
 # Install dependencies manually
 
 # Verify setup
@@ -21,7 +21,7 @@ just test    # Run test suite
 
 ### Repository Structure
 ```
-{{REPO}}/
+contractiles/
 ├── src/                 # Source code (Perimeter 1-2)
 ├── lib/                 # Library code (Perimeter 1-2)
 ├── extensions/          # Extensions (Perimeter 2)
@@ -62,7 +62,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**:
@@ -95,10 +95,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/contractiles/labels/good%20first%20issue) — Simple Perimeter 3 tasks
+- [`help wanted`](https://github.com/hyperpolymath/contractiles/labels/help%20wanted) — Community help needed
+- [`documentation`](https://github.com/hyperpolymath/contractiles/labels/documentation) — Docs improvements
+- [`perimeter-3`](https://github.com/hyperpolymath/contractiles/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/MAINTAINERS

@@ -4,7 +4,7 @@
 # Format: Name <email> (role)
 # Replace placeholders with actual maintainer information.
 
-{{AUTHOR}} <{{AUTHOR_EMAIL}}> (Lead Maintainer)
+Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk> (Lead Maintainer)
 
 # Additional maintainers:
 # Name <email> (role)