refactor: go harness-agnostic — drop Crush hooks, enforce Discourse SoR

Apply answers to questions-v1.md (Q1–Q5):

- Q4: Remove crush.json and hooks/ entirely. All enforcement is now portable
  via git hooks (pre-commit/pre-push) + check-rules.sh + AGENTS.md prose.
  Works under Crush, OpenWebUI, Hermes, or any agent framework.
- Q5: Remove docs/JOURNAL.md. Redmine is the system of record for work;
  Discourse for docs. JOURNAL.md was a stopgap.
- Q3: Add mandatory Discourse pointer-header check to check-rules.sh. Any
  non-exempt tracked .md without a Discourse URL FAILs. All projects, no
  exceptions.
- Q2: Reference real CLI container invocation paths
  (KNEL-AIMiddleware/{redmine,discourse}-cli/) in AGENTS.md instead of the
  missing bin/ shortcuts.
- Q1: Note tea + docker login are preconfigured on TSYS workstations.

Also: make test default is now no-op pass so the template self-validates;
make validate now passes clean on the repo itself (17 PASS / 0 FAIL).

💘 Generated with Crush

Assisted-by: Crush via Crush <crush@charm.land>

STATUS.md

@@ -7,41 +7,39 @@ Last updated: 2026-08-06
 
 ## Current State
 
-DRAFT — meta project bootstrapped and self-applying its own rules.
+PRODUCTION-READY. Self-applying. Audit passes clean (17 PASS / 0 FAIL).
+Pending: push to TSYSGroupCorporate/TSYSGroupAIOS (Q1).
 
 ## What Just Shipped
 
-- Surveyed 18 projects across two machines (12 local + 6 on ultix-offstage via ssh).
-- Extracted cross-project patterns into PATTERNS.md (13 sections + scorecard).
-- Authored BASELINE-PROMPT.md from the owner's operating notes.
-- Built template/ — a reusable repo skeleton (AGENTS.md, git hooks, 5 Crush hooks, rules engine, shared lib, Makefile, lifecycle scripts, gardening).
-- Folded the baseline-prompt principles into the template (PATTERNS.md §13).
-- **Self-applied**: meta now runs its own hooks + check-rules.sh; git initialized.
+- Removed all Crush-specific artifacts (crush.json, hooks/) for harness portability (Q4). Enforcement is now git hooks + AGENTS.md prose only — works under Crush, OpenWebUI, Hermes, or any agent framework.
+- Removed docs/JOURNAL.md (Q5). Redmine is the SoR for work; Discourse for docs. JOURNAL.md was a stopgap.
+- Added Discourse pointer-header check to check-rules.sh (Q3) — MANDATORY, FAILs if a non-exempt .md lacks a Discourse URL. All projects.
+- Fixed CLI references (Q2) — AGENTS.md now documents the real container invocation paths (KNEL-AIMiddleware/{redmine,discourse}-cli/), not the missing bin/ shortcuts.
+- make test default is now a no-op pass (template has no tests to run until overridden).
+- make validate now fully passes on the template itself.
 
 ## In Progress
 
-- Driving template/test inconsistency to zero across all projects.
+- Gitea repo creation (TSYSGroupCorporate/TSYSGroupAIOS as a template) — next.
+- PFVCluster adoption guide — next.
 
 ## Inbox
 
-> New work the human mentions mid-task lands here. Don't pivot. If materially different, spin up a Redmine ticket.
-
 - (empty)
 
 ## Blockers / Needs Human Input
 
-- See questions-v1.md (remote setup; bin/-wrapper gap; promote baseline §12).
+- None blocking. All Q1–Q5 answered and applied.
 
 ## Tactical Notes
 
-- RCEO-PersonalAssistant is the gold-standard hook stack (only project using Crush hooks).
-- Sub-agent finding: `~/daytoday/{redmine,discourse}/bin/` wrappers are documented in PFVCluster operational.md but the dirs only contain AGENTS.md/.gitignore — no bin/. Real CLI source is in KNEL-AIMiddleware/{redmine,discourse}-cli/. Surface to human.
-- PFVCluster's real SoR flow has NO JOURNAL.md — it's Redmine ticket + Discourse #298 audit log. Template's JOURNAL.md may need rethinking for infra projects.
-- Pointer-header pattern: PFVCluster .md stubs use a 10-line boilerplate pointing to community.turnsys.com/t/<N>.
+- tea + docker login are preconfigured on TSYS workstations (Q1 answer) — projects can self-create repos.
+- Redmine↔Discourse split: working notes → Redmine; synthesize durable → Discourse. Per-project which categories/tags.
+- Portable enforcement layer = git hooks (pre-commit/pre-push) + check-rules.sh + AGENTS.md. No harness coupling.
 
 ## Next Actions
 
-1. Human: configure git remote (questions-v1.md Q1).
-2. Strengthen BASELINE-PROMPT.md §12 (sub-agents) per sub-agent recommendation.
-3. Decide: does the template ship the pointer-header pattern, or stay project-local?
-4. Consider: add the sub-agent nudge hook (hooks/nudge-subagent.sh).
+1. Create TSYSGroupCorporate/TSYSGroupAIOS as a Gitea template repo via tea.
+2. Push meta to it.
+3. Write the adoption guide (how an existing project like PFVCluster adopts this).