operations

✅ Verification

Smallest relevant checks for wiki content, Moincraft runtime, dashboard, Nexus, AIRI, and LLM Wiki work.

Wiki verification# 

cd /home/mc/wiki
npm run wiki:content
PATH="/home/mc/bin:/tmp/dart-sass:$PATH" hugo --renderToMemory --buildDrafts --buildFuture
npm run wiki:build
npm run wiki:verify

Then inspect generated output as output only, including:

  • public/wiki/index.html
  • public/wiki/projects/index.html
  • public/wiki/operations/index.html
  • public/wiki/omp/index.html
  • public/wiki/hermes/index.html
  • public/wiki/moincraft/index.html
  • public/wiki/airi/index.html
  • public/wiki/nexus/index.html
  • public/wiki/skills/hugo-knowledge-site/index.html

Secret hygiene scan targets#

Search source and generated output for suspicious patterns:

  • API_KEY
  • TOKEN
  • PASSWORD
  • SECRET
  • .env
  • BEGIN PRIVATE
  • OPENROUTER_API_KEY
  • RCON
  • PI_DISCORD_BOT_TOKEN
  • PI_DISCORD_LAUNCHER_SECRET

Expected result: no actual secret values. Safe explanatory variable names may appear in cheat sheets.

Moincraft checks# 

cd /home/mc/moincraft
npm run check
npm run build
npm run contract

Use npm run verify or npm run green only when the task changes live runtime behavior or stack wiring.

Other project checks#

  • AIRI: targeted pnpm -F <package> typecheck, pnpm -F <package> build, or pnpm exec vitest run <path>.
  • Nexus: syntax-check changed Python and run the affected script only when generated data updates are safe.
  • LLM Wiki: WIKI_PATH=/home/mc/llm-wiki-site python3 scripts/wiki-pipeline.py --lint for non-mutating content validation.

Sources: root AGENTS.md, plan verification contract.