What's new​

Smart /agentic-z-update (three-way merge)​

The legacy auto-update did git checkout upstream/main -- <path> which silently overwrote anything you had edited locally. 1.2.0 replaces it with a per-file three-way merge (baseline, local, upstream) that classifies every change and only applies the safe ones automatically. Conflicts default to leave-alone with --per-file for an interactive picker.

New flags: --check, --quiet, --yes, --per-file. Persistent baseline at .claude/.upstream-baseline. PID-based concurrency lock at .claude/.upstream-update.lock.

SessionStart hook for upstream-ahead nudges​

A new SessionStart hook in .claude/settings.json runs update.py --check --quiet every time you open Claude Code. Silent on no-change, single-line nudge on drift, fail-open on network errors. Completes in under five seconds even on large repos.

The same hook also surfaces newer prebuilt search-index releases on GitHub. Read-only, never auto-downloads (the index tarball is ~200MB).

Voyage AI free-tier projection check​

/dayz-search-index and /dayz-search-wiki-index estimate the build's tokens before the embed phase and warn if cumulative monthly usage would exceed 80% of the 200M-token Voyage free tier. Tracks usage in ~/.claude/dayz-search-index/usage.log. New --ignore-tier-warning flag for CI.

Security baseline for shipped agents​

All twelve agent definitions tightened: explicit tools: allowlists, maxTurns caps, valid colors, stripped commentary blocks. Reviewer and debugger agents now run with permissionMode: acceptEdits. The shipped .claude/settings.json keeps a narrow Bash allowlist plus an explicit deny list (python -c, python -m, node -e, npm install, npx).

Skill renames for clarity​

The on-disk index path also moved from ~/.claude/dayz-rag-index/ to ~/.claude/dayz-search-index/. First-time users are unaffected. See "Upgrading from a pre-1.2.0 clone" below.

Plugin marketplace​

.claude-plugin/marketplace.json makes the repo installable via /plugin install agentic-z@dayz-n-chill.

Markdown lint hygiene​

Repo-wide markdown lint dropped from 40,349 errors to 0. .markdownlint.json was loosened for conversational prose; .markdownlint-cli2.jsonc and .markdownlintignore scope linting to canonical sources only (115 files, not 2,074).

Upgrading from a pre-1.2.0 clone​

If you're on a clone older than this release, your local update.py has a Unicode bug that crashes Windows cp1252 consoles when it tries to print the changelog box characters. To get past it once, run the upgrade with PYTHONIOENCODING=utf-8:

set PYTHONIOENCODING=utf-8 && python .claude\skills\agentic-z-update\update.py

Once the upgrade completes, the new update.py no longer prints those characters and future runs are clean. The shipped scripts/agentic-z-update.bat wrapper sets the env var automatically.

After the upgrade, you may see leftover folders from renamed skills in your working tree (the old git checkout-based merge didn't delete files removed upstream). Run python .claude\skills\agentic-z-update\update.py --check --per-file to walk through them and pick "take" to clean each one up.

Breaking changes​

• Skill names listed in the rename table above. References to old names (in your own scripts, hooks, agent prompts) need updating.
• On-disk RAG index path moved. If you migrated manually, no action. If you didn't, run /dayz-search-download to re-fetch or /dayz-search-index to rebuild.

What's next​

• Real-world feedback from people running 1.2.0 in anger.
• Revisit the deleted-locally-files-reappear-on-update behavior (currently a deliberate spec choice, also a UX wart).
• Wider wiki crawl scope so the wiki index covers gameplay-mechanic pages, not just CE/admin docs.

If you customize an agent or build a new skill, send it back upstream — every contribution sharpens the toolkit for the next person who clones.

What changed​

• Added the dayz-import-mod skill. Point it at an external folder, get a directory link at workspace/<ModName>/ plus the matching P:\<ModName>\ junction, so /dayz-build-pbo, /dayz-launch-workbench, and the rest of the toolchain work on it like a native scaffold. Source folder stays where it is, never copied or moved.
• Added the dayz-add-scaffold skill. Companion to /dayz-new-mod, but works on a folder that already exists. Idempotent: writes only the missing pieces (config.cpp, $PBOPREFIX$, workbench/dayz.gproj, README, skeleton folders), never overwrites. Used by /dayz-import-mod for the y/N "add this missing piece?" prompts, also runnable directly when you cloned a mod into workspace/ by hand and want the standard skeleton filled in.
• Fixed a real safety bug in dayz-clean-workspace. The old code used shutil.rmtree on the workspace folder, which on Windows recurses into junction targets and would have wiped an imported mod's external source. Clean now detects links (junctions and symlinks) and removes them via cmd /c rmdir, which removes the link without touching what it points at. The plan output distinguishes the two: (workspace) for native scaffolds (folder + contents), (workspace-link) for imports (link only, source kept).

How /dayz-import-mod works​

$ /dayz-import-mod --source C:\Users\me\repos\MyMod
[OK]    Source validated: C:\Users\me\repos\MyMod
[INFO]  Derived mod name: MyMod
[OK]    workspace\MyMod -> C:\Users\me\repos\MyMod (junction)
[OK]    P:\MyMod -> workspace\MyMod (junction)

Scaffolding check:
  [OK]    config.cpp present
  [WARN]  $PBOPREFIX$ missing (needed for /dayz-build-pbo)
  [WARN]  workbench/dayz.gproj missing (needed for /dayz-launch-workbench --mod)

  Add $PBOPREFIX$ to your source folder? [y/N]: y
  [OK]    $PBOPREFIX$ written
  Add workbench/dayz.gproj? [y/N]: y
  [OK]    workbench/dayz.gproj written

Mod name defaults to the source folder's basename. If the basename has spaces or punctuation, pass --name <ValidName> to override.

For non-interactive runs, --scaffold auto-yes every prompt or --no-scaffold skip them all (link only).

Safety story​

The whole point of import is that your source folder is untouchable unless you explicitly opt in:

• The link is created without copying. Files in your source repo are read-through.
• /dayz-clean-workspace --mod MyMod removes the link and the P:\MyMod\ junction. Your source folder at C:\Users\me\repos\MyMod is never touched.
• The only writes into your source folder happen when you answer y to a scaffolding prompt (or pass --scaffold). The user's external repo has its own conventions, history, and .gitignore. We don't surprise it.

When to use which​

What changed​

• Deleted .obsidian/ from the repo root.
• Deleted the original obsidian-vault blog post.
• Removed the Obsidian section from the Plugins page. Superpowers stays.

The historical release-note posts (v0.1.0, v1.0.0) keep their Obsidian mentions intact since they reflect what shipped at the time.

Why​

The pitch for Obsidian was "browse the agent stack as a graph." The agents already navigate that graph for you when they route a request to the right skill or doc. So the user-facing benefit was thin: a fancy markdown viewer with backlinks for files agents read on your behalf anyway.

If you actively take design notes, sketch architecture diagrams, or want a personal knowledge base alongside the repo, Obsidian is great. But that's a personal choice, not something Agentic-Z needs to ship a config for.

What if you were using it?​

Nothing breaks. Your local Obsidian install still reads markdown files in this folder if you point it at the repo root. You just won't get the pre-configured plugin manifest on first open. Recreate .obsidian/ locally and Obsidian will manage it from there.

What changed​

• Added a routing rule to L1 (CLAUDE.md / AGENTS.md / GEMINI.md): for DayZ work, dispatch the matching dayz-* specialist via the Agent tool.
• Added a role-to-specialist table to docs/dayz-modding.md so the rule has a concrete mapping.

The mapping​

Why​

Generic Superpowers agents (like superpowers:code-reviewer) don't know Enforce Script. They'd miss DayZ-specific traps like:

• modded class Foo extends Foo is a silent no-op (the extends is wrong; it has to be modded class Foo { }).
• GUI-extending modded classes need a #ifndef NO_GUI guard or the server crashes at compile.
• Engine classes rooted at Managed (UIScriptedMenu, Widget subtypes, UIManager) can't be modded at all.

Your DayZ specialists know all of this. The routing rule makes sure they get called.

What it doesn't change​

• For non-DayZ work (Python skills, scripts, infra, wiki), Superpowers' generic agents are still used.
• Superpowers' main-thread skills (brainstorming, writing-plans, systematic-debugging, etc.) still run as-is. Only the subagent-dispatch step changes.
• No skill files were modified. The rule lives in L1 + the docs table; agents read both.

What's new​

Pages and structure​

• Foundations sidebar reorganized into Introduction → Prerequisites → Installation & Setup → Plugins → MCP Servers. Prerequisites is now its own page with download links for DayZ, DayZ Tools, Voyage AI, and Python.
• About pages for both AI Agents and Skills & Tools, sitting first in their accordions. They explain the roster as a whole instead of dumping a generated index of boxes.
• Plugins page documenting Superpowers (obra/superpowers) and the Obsidian vault setup as optional adds.
• MCP Servers page documenting dayz-rag (bundled), GitHub MCP, and Web-fetch MCP with copy-paste config.
• Model Routing page rewritten as Model Selection — frames it as a per-agent default with an override workflow, instead of pretending the main thread auto-routes.

Agents​

• Twelve unique colors. Every agent now has its own display color (was: 5 agents sharing green). Same applies in Claude Code's agent picker and the wiki badges.
• Wiki agent pages cleaned up. Escaped <span> badge soup gone; example blocks render as a styled container with bold Context / User / Assistant labels and an italic commentary divider; the runtime memory protocol stripped from the body. Each page shows a single representative example instead of three.
• Frontmatter badges at the top of each agent page (Agent / model / color) with proper color rendering.

Skills​

• /agentic-z-update — new skill that pulls upstream template improvements into your clone without touching workspace/. Adds the upstream remote on first run, surfaces a changelog, merges only template paths, and re-runs /sync-skills automatically.
• Wiki skill mirrors regenerated from canonical SKILL.md sources so escaped angle brackets render as code spans, not raw text.

Homepage​

• Stats band: 12 specialist agents, 20 slash skills, 3 agent CLIs, 2 MCP servers (replaced the old "1 Drive" filler).
• Three-Layer Stack rewrites: each card now leads with a short pitch and explains the value to a non-technical reader. "What you get" lists three concrete behaviors per layer.
• On-Tap Reference section showcases the local RAG over vanilla source + Bohemia community wiki.
• The Style Guide section credits TrueDolphin's EnScript style guide, mirrored locally.
• Specialist Agents grid links to per-agent pages.
• Quick Start terminal with a typing animation cycling through 24 mod names — same component now reusable on the intro page via <QuickStartTerminal align="left" />.
• Become a Contributor section with Discord and GitHub links.

Theme and styling​

• Dark mode locked. Theme switcher removed; site is dark-only.
• Logo-matched color hierarchy: rust = CTAs and active states, bone = links, olive = borders/structure. WCAG 2.1 AA verified across 44+ contrast pairs.
• Sidebar polish: stencil-uppercase category headers, rust active-page indicator with faint tint and 2px left bar, no hover underlines, no double-hover on the chevron.
• Code blocks now have a layered background (warm gradient + rust corner glow + olive haze + scanlines + inset vignette) with rust title bars and themed copy buttons.
• Doc body theming: uppercase H2 with olive underline, rust inline code pills, italicized rust-bordered blockquotes, olive-bordered tables that fill the column without bleeding under the TOC.
• Custom 404 page — "404 — Off the Map" with rust hero accent.

Plugins now actually documented​

The L1 rules referenced Superpowers and Obsidian for a while as if they were installed. Removed those references back in v0.1.x; v1.0 puts both back as opt-in, documented setup steps on the new Plugins page.

What's next​

• Algolia DocSearch integration (waiting on OSS application approval).
• More specialist agents for surfaces this template doesn't cover (Workshop publishing? Custom map workflows? Tell us in Discord).
• Mermaid diagrams in the docs for the agent-dispatch flow.

If you customize an agent or build a new skill, send it back upstream — every contribution sharpens the toolkit for the next person who clones.

Highlights​

• 12 specialist agents — script, config, asset, map, UI, server-admin, object-builder, workbench, mod-debugger, mod-reviewer, docs-wiki-sync, and the meta agent-creator.
• 20 slash skills for the full mod lifecycle — /dayz-new-mod, /dayz-build-pbo, /dayz-launch-test, /dayz-pack-texture, /dayz-edit-types, /dayz-split-types, plus environment helpers (/dayz-preflight, /dayz-workdrive).
• DayZ RAG — semantic search over vanilla Enforce Script + the Bohemia community wiki via the dayz-rag MCP server. Build locally with /dayz-search-index or pull the prebuilt index with /dayz-search-download.
• Multi-CLI sync — /sync-skills links the repo's skills into Claude Code, Codex, and Gemini home dirs so all three agents see the same commands.
• Superpowers plugin integration — TDD, plan-first, and brainstorm-first workflows for general code (skipped on DayZ tasks where Enforce Script conventions take over).
• Obsidian vault — repo root works as a vault for graph-view navigation across CLAUDE.md, agents, skills, and docs.
• Docusaurus wiki mirror kept in sync via the docs-wiki-sync agent.

Getting started​

git clone https://github.com/DayZ-n-Chill/Agentic-Z.git
cd Agentic-Z
python .claude/skills/sync-skills/sync.py
python .claude/skills/dayz-search-download/download.py   # optional, ~1 min vs 25-30 min build

Then open in Claude Code, Codex, or Gemini and start with /dayz-preflight.

See the README for full docs.

The new /dayz-search-download skill skips it.

What changed​

• Added the dayz-search-download skill — pulls a prebuilt index tarball from the repo's GitHub releases and extracts it to ~/.claude/dayz-search-index/, the same place /dayz-search-index writes to.
• Same on-disk result. Roughly 1 minute instead of 25–30. No Voyage API token cost at index time (query-time embedding still needs the key).
• Idempotent — checks an installed-tag marker and skips re-download if you're already on the release version.
• New docs-wiki-sync agent keeps the Docusaurus wiki at wiki/ in sync with canonical sources (agent definitions, skill SKILL.md files, L1 docs).
• New model routing guide at docs/model-routing.md — when to dispatch to subagents, when to drop to Haiku for trivial lookups, when to keep work on the main Opus thread.

When to use which​

The downloaded index is built against vanilla DayZ at the release-tagged version. If your local install is on a newer patch and you need precise recall against your installed source, rebuild locally.

Where it applies​

• ✅ General code — Python, JS, shell helpers under scripts/, .claude/skills/, .claude/mcp/.
• ❌ DayZ work — .paa, .p3d, .rvmat, config.cpp, types.xml, modded .c Enforce Script.

DayZ has no Enforce Script unit-test runner, so on DayZ tasks the quality lever is strict adherence to .claude/skills/_shared/enscript-style.md instead of TDD.

Other methodology updates this round​

• New prompt engineering conventions doc for agents — referenced from agent definitions so they share a baseline for tool briefings, parallelism, and "why over what" patterns.
• L2 conventions (DayZ-specific rules) explicitly carved out from L1 default rules. L1 in CLAUDE.md / AGENTS.md / GEMINI.md; L2 in .claude/skills/_shared/dayz-conventions.md.
• Minimalism rule still wins for trivial fixes — a one-line bug fix doesn't trigger a brainstorm + plan + TDD cycle.