docs(coc): replace placeholders in CODE_OF_CONDUCT.md

Follow-up to #112 / #113. `CODE_OF_CONDUCT.md` was the same kind of
half-rendered template as the original `CONTRIBUTING.md`: it shipped
with a `TEMPLATE INSTRUCTIONS` HTML-comment block at the top and
`{{PROJECT_NAME}}`, `{{CONDUCT_EMAIL}}`, `{{CONDUCT_TEAM}}`,
`{{RESPONSE_TIME}}`, `{{CURRENT_YEAR}}`, `{{FORGE}}`, `{{OWNER}}`,
`{{REPO}}` placeholders unresolved.

Changes:

- Removed the `TEMPLATE INSTRUCTIONS` HTML-comment block at the top.
- Filled all placeholders with real values:
    {{PROJECT_NAME}}   → AffineScript
    {{CONDUCT_EMAIL}}  → jonathan.jewell@gmail.com
    {{CONDUCT_TEAM}}   → "the maintainers" (this is a solo-maintained
                         personal estate; "team" / "committee" would
                         overpromise)
    {{RESPONSE_TIME}}  → 7 days (calibrated for solo-maintained
                         response cadence rather than the 48h SLA the
                         template suggested)
    {{CURRENT_YEAR}}   → 2026
    {{FORGE}}/{{OWNER}}/{{REPO}} → github.com / hyperpolymath /
                                   affinescript
- Dropped the "Enforcement Across Perimeters" table — Perimeter 1/2/3
  vocabulary is template-only and was also removed from CONTRIBUTING.md
  in #113.
- Dropped the "Perimeter 2 applicants must confirm" line under
  Onboarding for the same reason.
- Dropped the "Anonymous Form" row from the reporting table — its body
  was `[Link to form if available]` and no such form exists.
- Dropped the "Maintainers receive additional training on enforcement"
  bullet — there is no such training programme; the line was
  aspirational template text.
- Reworded the Appeals "different team member" claim
  (impossible with one maintainer) to "after consultation with an
  uninvolved party where possible" — honest about the conflict-of-
  interest mitigation that's actually available.
- Reworded the Conflicts of Interest section to match the same
  single-maintainer reality.

Base Contributor Covenant 2.1 attribution preserved.

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

Author: hyperpolymath

CODE_OF_CONDUCT.md

@@ -1,28 +1,8 @@
 # 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 AffineScript 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,9 +116,8 @@ If you experience or witness unacceptable behaviour, or have any other concerns,
 
 | Method | Details | Best For |
 |--------|---------|----------|
-| **Email** | {{CONDUCT_EMAIL}} | Detailed reports, sensitive matters |
+| **Email** | jonathan.jewell@gmail.com | 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 |
 
 **What to Include**
 
@@ -152,8 +131,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 **7 days**
+2. The maintainers 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,17 +148,17 @@ All reports will be handled with discretion:
 
 ### Conflicts of Interest
 
-If a {{CONDUCT_TEAM}} member is involved in an incident:
+If a maintainer is involved in an incident:
 
 - They will recuse themselves from the process
-- Another maintainer or external party will handle the report
+- An uninvolved party will handle the report
 - We will disclose any potential conflicts
 
 ---
 
 ## Enforcement Guidelines
 
-The {{CONDUCT_TEAM}} will follow these guidelines in determining consequences:
+The maintainers will follow these guidelines in determining consequences:
 
 ### 1. Correction
 
@@ -213,31 +192,20 @@ The {{CONDUCT_TEAM}} will follow these guidelines in determining consequences:
 
 **Duration**: Permanent (with appeal rights after 12 months)
 
-### Enforcement Across Perimeters
-
-For contributors with elevated access (Perimeter 2 or 1):
-
-| Level | Additional Consequence |
-|-------|----------------------|
-| Correction | Noted in contributor record |
-| Warning | Access privileges may be temporarily reduced |
-| Temporary Ban | Access reduced to Perimeter 3 for ban duration |
-| Permanent Ban | All access revoked |
-
 ---
 
 ## Appeals
 
 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** jonathan.jewell@gmail.com 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 after consultation with an uninvolved party where possible
 - You will receive a response within 14 days
 - The appeals decision is final
 - You may only appeal once per incident
@@ -277,8 +245,6 @@ Beyond enforcement, we actively work to prevent issues:
 
 **Onboarding**
 - All contributors are expected to read this Code of Conduct
-- Perimeter 2 applicants must confirm they've read and understood it
-- Maintainers receive additional training on enforcement
 
 **Culture**
 - We model the behaviour we expect
@@ -310,8 +276,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/affinescript/discussions) (for general questions)
+- Email jonathan.jewell@gmail.com (for private questions)
 - Contact any maintainer directly
 
 ---
@@ -324,4 +290,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>