Nucs

build-install

Build and install Agentmaster ON THIS MACHINE — every build flavor (lib-only compile check, ClCompile-only for locked binaries, full Debug package, full Release package, the engine test harness) and both local installs: the DEV instance (AgentmasterDev, Debug loose layout, close → build → relaunch) and the PRODUCTION instance (Agentmaster, Release loose layout: build -ReleaseIdentity → stamp version → register → launch → profile picker). Encodes the machine map (two registered identities side by side, one repo tree, the Store WT to never touch) and the battle-tested troubleshooting: the self-kill check (is MY shell hosted in the instance I'm about to close?), PRI210 mapped resources.pri, 0x80070020 same-full-name re-register collisions (orphaned claudes pin a removed package — bump the layout version, never kill them), stale build-mutex reclaim, Git-Bash msbuild invocation quirks, the ~156s `.appxsym` symbol-package skip (the wrapper's default `/p:AppxSymbolPackageEnabled=false`, a measured 4–10x speedup), th

release-version

Deploy or cut a versioned release of Agentmaster — the local deploy inner-loop (close → build → relaunch) AND the public GitHub release pipeline (tag or dispatch release.yml → monitor → verify the 4 signed assets → apply notes → publish). Encodes the hard rules: hold the build mutex, pin `-R Nucs/Agentmaster` (gh defaults to the upstream microsoft/terminal remote), confirm the version with the user first, build the RELEASE identity, and ALWAYS pre-validate with a clean local Release build (incremental Debug builds mask clean-build errors the runner WILL hit). Use when the user asks to release a new version, cut/publish a release, ship vX.Y.Z, cut a NIGHTLY (vX.Y.Z-prerelease-nightly — auto-marked prerelease, offered only to nightly-opted users), or deploy the dev instance.

AI & Automation Listed

claude-wrap-conpty

Drive a REAL Claude Code TUI from code on Windows — spawn `claude.exe` on a pseudo-console (ConPTY), render its ANSI output into a readable screen, inject prompts as bracketed paste, and verify what actually landed in the session transcript on disk. This is the black-box test harness for Claude Code itself: what a headless `claude -p` can NEVER exercise (the Ink TUI's input box, startup modals, draft/type-ahead behavior, paste framing, the eaten-Enter class of bug). Ships a verified driver (`scripts/conpty_claude.py`, pywinpty + pyte) with a `selftest` that proves the whole chain on this machine in one tiny turn, plus `probe` / `send` / `raw` CLI verbs. Encodes the measured facts that make it work: `\r` submits while `\n` is a literal newline in the box; bracketed paste is the only atomic multi-line delivery; an inherited `CLAUDE_CODE_CHILD_SESSION` SILENTLY DISABLES transcript saving (so every on-disk verification fails for a reason nothing on screen explains) — the trap for any wrapper launched from inside

debug-dumps

Analyze and debug Windows crash dumps (.dmp) and app crashes for Agentmaster (the C++/WinRT WindowsTerminal fork) WITHOUT cdb/WinDbg — using the in-repo DIA-SDK + DbgHelp tools. Covers the whole loop: find the crash (WER Application Error event id 1000 + the full dump in %LOCALAPPDATA%\CrashDumps), read the exception record + faulting registers (dumpexc), decode what it means (0xC0000005 access violation, 0xC0000409 __fastfail incl. the CFG subcode 0xA freed-vtable, 0xC000027B stowed fail-fast, the 0xDDDDDDDD "dead-land" freed-memory register signature, non-canonical -1 faultData), walk the faulting-thread stack (dumpwalk2 ordered StackWalkEx; dumpourscan full-stack scan for OUR frames with a module histogram; dumpstack/hangwalk fallbacks), and symbolize OUR frames against the matching build's PDBs to pin the exact source line + root cause. Encodes the hard-won patterns: matching the PDB to the CRASHED binary by build time, "zero of our frames == a deferred/async XAML fail-fast off our call stack (uncatchable

release-notes

Author and assemble Agentmaster GitHub release notes — the house format (tight intro + "New"/"Fixes" + "Install" with the exact asset names), turning a commit delta into dense themed bullets, and the three framings: NIGHTLY vs PRE-RELEASE vs STABLE. Encodes the mechanics done repeatedly: derive the changelog since the right baseline (nightlies are INVISIBLE to baselines), the copy-paste Install block, the "comprehensive changelog since last stable" ASSEMBLY (a stable release folds every intervening pre-release's notes in full — never nightlies), stripping the draft's HTML-comment header before publishing, applying via `gh release edit --notes-file`, and CONVERTING a live release between stable and pre-release — including the gotcha that `--latest=false` does NOT move the Latest badge (you must explicitly `--latest` the release you want as Latest). Use when writing or updating a release's notes, choosing nightly/stable/pre-release framing, assembling the full changelog for a version, or flipping a published re