feat: complete VQL-UT repo overhaul — documentation, ABI/FFI, architecture, PanLL

Major overhaul transforming vql-ut from RSR template skeleton into a
fully documented, production-quality project:

**ABI/FFI (real implementation):**
- Idris2 ABI: 10 SafetyLevel tags, 11 VqlUtError codes, QueryMode,
  QueryPlanHeader with roundtrip proofs and layout verification
- Zig FFI: 5-stage pipeline (parse→bind→check→effects→compile),
  thread-safe 256-slot context pool, 11 unit tests passing
- All ~83 placeholder tokens replaced with real VQL-UT identifiers

**Educational documentation (A-Level accessible):**
- WHY-TYPE-SAFETY-MATTERS: horror stories (Therac-25, Equifax, Knight
  Capital), real-world analogies, safe/unsafe code examples
- WHAT-IS-VERISIMDB: octad concept, 6 modalities, 3 query paths
- THE-10-LEVELS-EXPLAINED: detailed walkthrough with TypeLL foundation
- GLOSSARY: 30+ terms in plain English
- FAQ: 8 questions including performance, comparison, roadmap

**Architecture:**
- ARCHITECTURE: 6-stage pipeline, technology stack, proof certificates
- TOPOLOGY: ecosystem positioning, deployment tiers
- DECISIONS: 4 ADRs (Idris2 over Lean, 10 levels, VQL-DT supersession,
  ReScript parser)
- QUICKSTART: prerequisites, build, example walkthrough
- CONTRIBUTING: real contribution guide with code standards

**PanLL integration:**
- panels/manifest.json: 4 panels (safety dashboard, query editor,
  proof explorer, horror stories)
- panels/clade.a2ml: database-tooling clade with 6 capabilities

**Infrastructure:**
- All container, CI, SCM, workflow files de-placeholdered
- 15 src/ README stubs replaced with real descriptions
- .gitignore updated for Zig build artifacts

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.devcontainer/Containerfile

@@ -1,9 +1,9 @@
 # SPDX-License-Identifier: PMPL-1.0-or-later
-# 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 VQL-UT
 # Base: Chainguard Wolfi (minimal, supply-chain-secure)
-# Build: podman build -t {{PROJECT_NAME}}-dev -f .devcontainer/Containerfile .
+# Build: podman build -t VQL-UT-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/VQL-UT
 
 # Default shell
 ENV SHELL=/bin/bash

.devcontainer/README.adoc

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: PMPL-1.0-or-later
 = Dev Container Usage
-:author: {{AUTHOR}} <{{AUTHOR_EMAIL}}>
+:author: Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 
 == Overview
 
@@ -24,4 +24,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 `VQL-UT` 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: PMPL-1.0-or-later
-// 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 VQL-UT
 // Works with: VS Code Dev Containers, GitHub Codespaces, Gitpod
 // Container runtime: Podman (recommended) or any OCI-compliant runtime
 {
-  "name": "{{PROJECT_NAME}}",
+  "name": "VQL-UT",
 
   "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="VQL-UT"
 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

@@ -5,13 +5,13 @@
 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
+  VQL-UT     - Your project name
+  hyperpolymath            - GitHub/GitLab username or org
+  vql-ut             - Repository name
+  j.d.a.jewell@open.ac.uk    - Email for conduct reports
+  Code of Conduct Committee     - Name of conduct team/committee
+  48 hours    - Initial response SLA (e.g., 48 hours)
+  2026     - Current year
 
 Review and customise:
 - Adjust enforcement ladder for your community size
@@ -22,7 +22,7 @@ Review and customise:
 
 ## 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 VQL-UT 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.
 
@@ -136,7 +136,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 |
 
@@ -152,8 +152,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 Code of Conduct Committee 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)
@@ -169,7 +169,7 @@ All reports will be handled with discretion:
 
 ### Conflicts of Interest
 
-If a {{CONDUCT_TEAM}} member is involved in an incident:
+If a Code of Conduct Committee member is involved in an incident:
 
 - They will recuse themselves from the process
 - Another maintainer or external party will handle the report
@@ -179,7 +179,7 @@ If a {{CONDUCT_TEAM}} member is involved in an incident:
 
 ## Enforcement Guidelines
 
-The {{CONDUCT_TEAM}} will follow these guidelines in determining consequences:
+The Code of Conduct Committee will follow these guidelines in determining consequences:
 
 ### 1. Correction
 
@@ -231,13 +231,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 Code of Conduct Committee member than the original
 - You will receive a response within 14 days
 - The appeals decision is final
 - You may only appeal once per incident
@@ -310,8 +310,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/vql-ut/discussions) (for general questions)
+- Email j.d.a.jewell@open.ac.uk (for private questions)
 - Contact any maintainer directly
 
 ---
@@ -324,4 +324,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

@@ -1,13 +1,13 @@
 # Clone the repository
-git clone https://{{FORGE}}/{{OWNER}}/{{REPO}}.git
-cd {{REPO}}
+git clone https://github.com/hyperpolymath/vql-ut.git
+cd vql-ut
 
 # Using Nix (recommended for reproducibility)
 nix develop
 
 # Or using toolbox/distrobox
-toolbox create {{REPO}}-dev
-toolbox enter {{REPO}}-dev
+toolbox create vql-ut-dev
+toolbox enter vql-ut-dev
 # Install dependencies manually
 
 # Verify setup
@@ -17,7 +17,7 @@ just test    # Run test suite
 
 ### Repository Structure
 ```
-{{REPO}}/
+vql-ut/
 ├── src/                 # Source code (Perimeter 1-2)
 ├── lib/                 # Library code (Perimeter 1-2)
 ├── extensions/          # Extensions (Perimeter 2)
@@ -58,7 +58,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**:
@@ -91,10 +91,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/vql-ut/labels/good%20first%20issue) — Simple Perimeter 3 tasks
+- [`help wanted`](https://github.com/hyperpolymath/vql-ut/labels/help%20wanted) — Community help needed
+- [`documentation`](https://github.com/hyperpolymath/vql-ut/labels/documentation) — Docs improvements
+- [`perimeter-3`](https://github.com/hyperpolymath/vql-ut/labels/perimeter-3) — Community sandbox scope
 
 ---
 

.github/FUNDING.yml

@@ -1,7 +1,7 @@
 # SPDX-License-Identifier: PMPL-1.0-or-later
-# 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

@@ -2,13 +2,13 @@
 
 # Project Governance
 
-This document describes the governance model for **{{PROJECT_NAME}}**.
+This document describes the governance model for **VQL-UT**.
 
 ---
 
 ## Project Governance Model
 
-{{PROJECT_NAME}} follows a **Benevolent Dictator For Life (BDFL)** governance model.
+VQL-UT 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.
 
@@ -155,4 +155,4 @@ with the community before adoption, even though the BDFL retains final authority
 
 ---
 
-<sub>Copyright (c) {{CURRENT_YEAR}} {{OWNER}}. Licensed under PMPL-1.0-or-later.</sub>
+<sub>Copyright (c) 2026 hyperpolymath. Licensed under PMPL-1.0-or-later.</sub>