From a7fd4a4e29edf7318094803e5e6cb03c27e6300e Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 11 Apr 2026 23:54:32 +0000 Subject: [PATCH] docs(maintenance): Project instructions patch for Trinity Core documentation gap MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes the stale 'SSH is blocked' guidance in the Claude Project config. Contains three patches to apply to project instructions: 1. What You CAN Access — add Trinity Core, MCP connectors, DB access 2. What You CANNOT Access — remove SSH/DB/Cockpit, clarify what remains 3. Add Task #126 deployment as positive example reference Also includes a fallback course-correction prompt the next Chronicler can paste at session start if the project config isn't updated in time. This is a Michael-side edit (Claude Project config lives in UI, not git). Estimated apply time: 2 minutes. --- ...tructions-trinity-core-patch-2026-04-11.md | 170 ++++++++++++++++++ 1 file changed, 170 insertions(+) create mode 100644 docs/maintenance/project-instructions-trinity-core-patch-2026-04-11.md diff --git a/docs/maintenance/project-instructions-trinity-core-patch-2026-04-11.md b/docs/maintenance/project-instructions-trinity-core-patch-2026-04-11.md new file mode 100644 index 0000000..dce85ce --- /dev/null +++ b/docs/maintenance/project-instructions-trinity-core-patch-2026-04-11.md @@ -0,0 +1,170 @@ +# Project Instructions Patch — Trinity Core Access Documentation + +**Written By:** Chronicler #80 — The Bulwark +**Date:** April 11, 2026 +**Purpose:** Fix the project instructions' documentation gap around Trinity Core SSH access + +--- + +## The Problem + +The current Claude Project Instructions for Firefrost Gaming Operations contain a "What You CAN Access" / "What You CANNOT Access" section that predates Trinity Core. It tells new Chroniclers that: + +- SSH to any server is blocked by Claude sandbox +- Cockpit web terminal is inaccessible +- Direct database access is unavailable +- They must "work through Gitea and web APIs" and have Michael run server commands + +**This is no longer true.** Trinity Core (MCP gateway deployed by Chronicler #78 The Crucible and reached production by #76 The Bridgekeeper) provides SSH access to all 7 Firefrost servers via the `Trinity Core:run_command` MCP tool, which is a standard tool call that works inside the Claude sandbox. + +The instructions' staleness caused real friction in Chronicler #80's session: + +- I refused to do a live deployment for a launch-critical task because the instructions said I couldn't SSH +- Michael had to remind me mid-session that Trinity Core existed +- I had to eat my own deployment caution in real time and adjust +- A task I estimated at 3-3.5 hours deployed in 7 minutes once I actually used the right tool + +Every future Chronicler will hit the same wall unless the instructions are updated. + +--- + +## How to Apply the Fix + +This is a **Michael-side edit.** The Claude Project config is not in any git repo — it lives in the Claude.ai project settings UI. The change takes about 2 minutes: + +1. Open the Claude Project for Firefrost Gaming Operations +2. Click "Edit project instructions" (or wherever the config is currently stored) +3. Find the two sections below +4. Replace the "OLD TEXT" with the "NEW TEXT" +5. Save + +Alternatively, if Michael prefers a fresh paste, use the replacement file at `docs/maintenance/project-instructions-REPLACEMENT-2026-04-11.md` (future Chronicler can compile this from the April 4 version + the patches below). + +--- + +## PATCH 1: "What You CAN Access" section + +### OLD TEXT + +``` +### What You CAN Access + +- ✅ Gitea API (git.firefrostgaming.com) +- ✅ Web services via HTTPS +- ✅ Push to repos (auto-deploys website) +``` + +### NEW TEXT + +``` +### What You CAN Access + +- ✅ Gitea API (git.firefrostgaming.com) +- ✅ Web services via HTTPS +- ✅ Push to repos (auto-deploys website) +- ✅ **Trinity Core MCP** — SSH command execution on all 7 Firefrost servers + via the `Trinity Core:run_command` tool. Servers: command-center, tx1-dallas, + nc1-charlotte, panel-vps, dev-panel, wiki-vps, services-vps. Use `list_servers` + to confirm the current roster. This is how Arbiter deployments, migrations, + log checks, and any SSH-requiring work gets done. It is NOT blocked. +- ✅ **MCP Connectors** — Canva, Cloudflare, Stripe, Google Calendar, Gmail, + Mermaid Chart are connected and available as native MCP tools. Use `tool_search` + to discover and load them when relevant. +- ✅ **Direct database access** via Trinity Core. Example: + `Trinity Core:run_command(server="command-center", command="PGPASSWORD='...' psql -U arbiter -h 127.0.0.1 -d arbiter_db -c 'SELECT ...'")` +``` + +--- + +## PATCH 2: "What You CANNOT Access" section + +### OLD TEXT + +``` +### What You CANNOT Access + +- ❌ SSH to any server (port 22 blocked by Claude sandbox) +- ❌ Vaultwarden (requires Michael's credentials) +- ❌ Direct database access +- ❌ Cockpit web terminal + +**Work through Gitea and web APIs. Michael runs server commands when needed.** +``` + +### NEW TEXT + +``` +### What You CANNOT Access + +- ❌ Vaultwarden (requires Michael's credentials — not accessible via any tool) +- ❌ Direct Cockpit web terminal UI (but the underlying servers ARE reachable + via Trinity Core SSH, which covers 99% of the use cases Cockpit was for) +- ❌ Michael's personal devices and accounts (phone, desktop, personal email) +- ❌ Real-time Discord UI (but the bot account can send messages, manage + channels, and create webhooks via scripts run through Trinity Core) + +**Deployment pattern:** For Arbiter code changes, use the backup → clone → +syntax check → copy → restart → verify pattern via Trinity Core. Never +git-pull directly to /opt/arbiter-3.0. Reference: Chronicler #80 Task #126 +deployment in the April 11 session handoff for a worked example. +``` + +--- + +## PATCH 3: Add a positive example reference + +Somewhere in the "Approach & patterns" or equivalent section, add a pointer: + +``` +**Trinity Core deployment example:** Chronicler #80 (The Bulwark) deployed +Task #126 lifecycle handlers to production Arbiter in 7 minutes using Trinity +Core. The full sequence — backup current file, clone branch to /tmp on target +server, syntax-check the new file in place, copy into /opt/arbiter-3.0, restart +service, verify active, tail logs, smoke-test endpoint, clean up temp clone, +merge branch to main — is reproducible. See SESSION-HANDOFF-PREVIOUS.md from +April 11, 2026 for the worked example. +``` + +--- + +## Fallback: Session-Start Course Correction Prompt + +If Michael doesn't get to updating the project config before the next session starts, the next Chronicler can be course-corrected with this exact paste at the start of their session, **after** they complete the standard Joining Protocol: + +``` +Before we begin work: the current project instructions have a documentation +gap. They say you cannot SSH to Firefrost servers. This is no longer true. + +Trinity Core is an MCP gateway that provides SSH execution on all 7 servers +via the `Trinity Core:run_command` tool. Call `tool_search` with query +"Trinity Core SSH" to load it, then call `Trinity Core:list_servers` to see +the roster. + +Use this for: Arbiter deployments, database queries, log checks, Discord bot +scripts, file operations on any server. The deployment pattern is backup → +clone → syntax check → copy → restart → verify. Chronicler #80 (The Bulwark) +used this pattern to deploy Task #126 lifecycle handlers in 7 minutes on +April 11, 2026 — see docs/relationship/memorials/the-bulwark-memorial.md for +a worked example. + +Do NOT refuse deployment tasks on grounds of "SSH is blocked." That is stale +guidance. Trinity Core is in your toolkit. + +Now proceed with the session normally. +``` + +--- + +## Why Both? + +- **Patch the project instructions** → permanent fix, every future Chronicler benefits +- **Fallback course correction prompt** → works in the window between now and when Michael gets to the edit + +The fallback is belt-and-suspenders insurance. The real fix is the project instructions update. + +--- + +**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️ + +— Chronicler #80, The Bulwark +April 11, 2026