skills

Workspace Filesystem Rewire Skill

Hermes-loadable workflow for safe source-root moves, generated/runtime splits, route rewires, and public-safety checks.

The devops/workspace-filesystem-rewire skill is the workspace contract for deep filesystem organizing and reference rewiring.

Use it when a change moves ownership boundaries: source roots, generated output, runtime state, deploy roots, service routes, subdomains, package metadata, or operator wiki inputs.

Why it exists#

The workspace is not one repository. /home/mc/wiki owns the operator wiki, /home/mc/moincraft owns the Minecraft runtime, /home/mc/nexus-dash owns Nexus dashboard generation, and Hermes/Hermit owns agent runtime state. A safe move must update every caller without turning generated output or private runtime data into source.

The skill makes agents do the hard parts explicitly:

  • map source, generated output, runtime state, deploy output, public route, process, and credential ownership;
  • identify references with find, search, LSP, or AST tools instead of memory;
  • move only authoritative source, then rewire scripts, docs, deploy logic, service maps, route docs, PM2/systemd/nginx references, and verification checks;
  • preserve compatibility routes and document intentional non-changes;
  • verify affected projects before removing obsolete source.

Hermes handling#

Canonical skill source:

/home/mc/wiki/skills/devops/workspace-filesystem-rewire/SKILL.md

Hermes discovery is wired through:

/home/mc/hermit/config.yaml
skills.external_dirs:
  - /home/mc/wiki/skills

This keeps the skill reviewable in the operator wiki source tree instead of copying it into hidden ~/.hermes/skills. Local Hermes skills still take precedence when names collide.

Safety boundary#

Never publish or quote these as part of a rewire:

  • .env, tokens, passwords, RCON credentials, auth or pairing state;
  • .hermes, .omp, sessions, raw memories, logs, browser profiles, DBs, WAL/SHM files, caches, and hidden runtime state;
  • relay, MindServer, viewer, KB, raw Hermes, logs, databases, cache, or session surfaces without explicit auth/safety review;
  • generated output such as public/, dist/, .svelte-kit/, Hugo resources, deploy releases, and test reports as source.

Use sanitized Nexus/wiki generated summaries for public pages. Do not dump raw Hermes files into Hugo.

OMP and Pi-facing contracts#

Keep Pi-facing names stable. Preserve PI_*, Pi package metadata, and /kb-style package contracts. Adapt to OMP only at runtime boundaries such as /home/mc/.local/bin/omp-plugin-env, /home/mc/.omp/agent, launch wrappers, or protected reverse proxies.

Verification checklist#

Before calling a rewire complete:

  1. The new source root builds or verifies from its owner directory.
  2. Runtime projects still pass their targeted checks from their owner directories.
  3. Generated wiki/content is regenerated from source when changed.
  4. Deploy scripts point at the intended source and deploy roots.
  5. Old path references are either gone or documented as compatibility routes/fallbacks.
  6. No protected Hermes/runtime state was copied, published, or quoted.