@ps-neko/nekowork 0.1.0-alpha.4 → 0.1.0-alpha.6

package/CLAUDE.md

@@ -8,7 +8,7 @@
 
 ## 자동 갱신 영역
 
-<!-- HARNESS:START version=0.1.0-alpha.4 -->
+<!-- HARNESS:START version=0.1.0-alpha.6 -->
 <!-- 이 영역은 scripts/sync-claude-md.js 가 자동 갱신한다. 직접 편집 금지. -->
 
 ## 카탈로그 요약
@@ -17,8 +17,8 @@
 - skills: 10
 - commands: 1 (legacy compat)
 - hooks: 5 (gateguard-fact-force, config-protection, quality-gate, pre-bash-dispatcher, persistent-mode)
-- packs: core, quality, security, frontend, testing, release, enterprise
-- profiles: core, developer, security, product, quality, frontend, testing, research, full
+- packs: core, builder, quality, security, frontend, testing, release, enterprise
+- profiles: core, developer, builder, security, product, quality, frontend, testing, research, full
 - harnesses: claude, codex, cursor, gemini, opencode
 
 ## 에이전트 → 모델 매트릭스

package/README.md

@@ -1,10 +1,10 @@
 # NEKOWORK
 
-Local-first AI development quality runtime for Claude Code, Codex CLI, and Gemini CLI.
+Local-first AI development OS and quality runtime for Claude Code, Codex CLI, and Gemini CLI.
 
 [![harness-validate](https://github.com/Ps-Neko/NEKOWORK/actions/workflows/harness-validate.yml/badge.svg)](https://github.com/Ps-Neko/NEKOWORK/actions/workflows/harness-validate.yml)
 
-NEKOWORK prevents AI coding agents from shipping unverified changes.
+NEKOWORK helps AI coding agents build quickly, then prevents unverified changes from shipping.
 
 It runs:
 
@@ -18,7 +18,7 @@ No auto-commit. No auto-push. No surprise deploy.
 Product principle:
 
 ```text
-NEKOWORK = Claude work -> Codex verification -> Human Gate
+NEKOWORK = fast AI build -> Codex verification -> Human Gate -> explicit apply
 ```
 
 NEKOWORK is the product. HARNESS is the local runtime it packages: one source catalog, `agent.yaml`, projected into Claude Code, Codex CLI, Cursor, Gemini CLI, and OpenCode surfaces.
@@ -30,10 +30,12 @@ NEKOWORK is intentionally not a 100-agent pack. Every agent, skill, hook, profil
 3. produce auditable evidence,
 4. respect Human Gate.
 
-**Public alpha evidence:** 7 packs / 9 profiles / 36 components / 5 harness targets / 7 case-study flows / 252 tests / 0 moderate+ npm audit issues / fresh `npx @alpha` smoke
+**Public alpha evidence:** 8 packs / 10 profiles / 36 components / 5 harness targets / 7 case-study flows / 263 tests / 0 moderate+ npm audit issues / fresh `npx @alpha` smoke
 
 NEKOWORK does not automatically commit, push, publish, deploy, or apply diffs. `apply` is explicit and requires verified ship-ready evidence.
 
+**Latest alpha evidence:** [CI badge](https://github.com/Ps-Neko/NEKOWORK/actions/workflows/harness-validate.yml) / [npm package](https://www.npmjs.com/package/@ps-neko/nekowork) / [smoke transcript](docs/DEMO.md#one-minute-terminal-transcript) / [report artifact](docs/DEMO-REPORT.md)
+
 **One-minute demo:** [terminal transcript](docs/DEMO.md#one-minute-terminal-transcript) / [full report example](docs/DEMO-REPORT.md) / [alpha feedback](https://github.com/Ps-Neko/NEKOWORK/issues/new?template=alpha-feedback.yml) / [roadmap](docs/ROADMAP.md)
 
 ![NEKOWORK one-minute terminal demo](docs/assets/demo-terminal.svg)
@@ -44,9 +46,22 @@ Use the current npm alpha for the published health smoke:
 
 ```bash
 npx -y @ps-neko/nekowork@alpha check
+npx -y @ps-neko/nekowork@alpha build "implement this safely" --mode fast --session first-build
+npx -y @ps-neko/nekowork@alpha report --session latest
+```
+
+Start with `build`. Drop down to `work`, `verify`, and `ship` only when you need phase-level control.
+
+Use a source checkout for local development:
+
+```bash
+node scripts/cli.js check
+node scripts/cli.js build "implement this safely" --mode fast --session first-build
+node scripts/cli.js report --session latest
+node scripts/cli.js gate status --session latest
 ```
 
-Use a source checkout for the new simple command path:
+Or use the decomposed beginner path directly:
 
 ```bash
 node scripts/cli.js check
@@ -55,7 +70,7 @@ node scripts/cli.js report --session first-run
 node scripts/cli.js gate status --session first-run
 ```
 
-The simple path maps to the full evidence loop: `check = doctor --quick`, and `run = work -> verify -> ship`.
+The simple paths map to the evidence loop: `check = doctor --quick`, `build = mode presets over run`, and `run = work -> verify -> ship`.
 
 To add generated harness surfaces to another local repository:
 
@@ -107,13 +122,29 @@ Decision:
 
 Human Gate is the point where NEKOWORK stops being an autopilot and becomes an approval system.
 
+## Apply Preview
+
+Before `apply`, NEKOWORK expects the human to inspect the evidence surface:
+
+```text
+Session: first-work
+Diff source: captured live-work diff
+Files changed: 3
+Verifier verdict: approve
+Human gate: clear
+Ship ready: true
+Apply command: node scripts/cli.js apply --session first-work
+```
+
+`apply` still does not commit, push, publish, deploy, or create a PR. It only applies the verified `SHIP_READY` diff when gates are clear and the target worktree is clean.
+
 ## Compared With Agent Packs
 
 | Tool pattern | Optimizes for | NEKOWORK optimizes for |
 |---|---|---|
 | Large Claude Code packs | More agents, commands, skills | Curated verification loop |
 | Team simulation | More specialist perspectives | Read-only team plus one executor |
-| Autopilot | Fast autonomous execution | Report, gate, explicit apply |
+| Autopilot | Fast autonomous execution | `build` modes, report, gate, explicit apply |
 | Discipline workflows | Better development habits | Evidence-backed ship decision |
 
 ## When To Choose What
@@ -124,13 +155,16 @@ Human Gate is the point where NEKOWORK stops being an autopilot and becomes an a
 | Get the broadest Claude Code skill/command environment | Everything Claude Code |
 | Simulate startup team roles from planning to QA | GStack |
 | Run autonomous multi-agent execution | OMC |
+| Use one local AI development runtime with safe build modes | NEKOWORK |
 | Verify AI changes, require human approval, then apply explicitly | NEKOWORK |
 
+Use Superpowers, Everything Claude Code, GStack, or OMC to produce stronger AI work when they fit your workflow. Use NEKOWORK as the main runtime when you want build speed plus verification, gate, report, and explicit apply in one product.
+
 ## Three Paths
 
 Most users should start with the Beginner path. The other paths are for explicit phase control or legacy compatibility.
 
-1. Beginner: `check -> run -> report -> gate`
+1. Beginner: `check -> build -> report -> gate`
 2. Advanced: `ask -> plan -> team -> work -> verify -> gate -> ship -> report -> apply`
 3. Legacy: `review` / `review-cycle`
 
@@ -140,9 +174,10 @@ NEKOWORK is for teams that want AI-assisted development without making the agent
 
 ## Status
 
-- Current repository version: `0.1.0-alpha.4`
+- Current repository version: `0.1.0-alpha.6`
 - Current package name: `@ps-neko/nekowork`
-- Current npm alpha: `@ps-neko/nekowork@0.1.0-alpha.4`
+- Published CLI names: `nekowork` and `harness`
+- Current npm alpha: `@ps-neko/nekowork@0.1.0-alpha.6`
 - Supported install path today: npm alpha, clone, submodule, or local repository integration
 - Dist-tag note: use `@alpha` until a stable release; `latest` still points at the first alpha line
 - Default mode: mock providers, no API keys, no provider CLI calls
@@ -150,7 +185,7 @@ NEKOWORK is for teams that want AI-assisted development without making the agent
 Current local verification:
 
 - `npm run lint`: pass
-- `npm test`: 252 tests pass
+- `npm test`: 263 tests pass
 - `npm audit --audit-level=moderate`: 0 vulnerabilities
 - `npm pack --dry-run --json`: pass
 - `npx -y @ps-neko/nekowork@alpha check`: pass with warnings only
@@ -179,21 +214,11 @@ Current local verification:
 | `release` | ship/no-ship evidence | pre-release checks |
 | `enterprise` | full catalog with all gates | high-control teams |
 
-## Quick Start
-
-Requirements:
+## Quick Start Details
 
-- Node.js 22+
-- npm
-- git
-
-Fastest no-API demo:
-
-```bash
-npx -y @ps-neko/nekowork@alpha check
-```
+Requirements: Node.js 22+, npm, and git.
 
-Repository demo:
+For a repository-pinned local demo:
 
 ```bash
 git clone https://github.com/Ps-Neko/NEKOWORK.git harness
@@ -202,21 +227,7 @@ npm ci
 npm run demo:quick -- --cleanup
 ```
 
-This creates a disposable target project and runs `doctor -> run -> report -> gate status`. It uses mock providers and does not call Claude, Codex, Gemini, or paid APIs.
-
-Recommended path for most users:
-
-```bash
-git clone https://github.com/Ps-Neko/NEKOWORK.git harness
-cd harness
-npm ci
-node scripts/cli.js check
-node scripts/cli.js run "implement, verify, and prepare ship readiness" --session first-run
-node scripts/cli.js report --session first-run
-node scripts/cli.js gate status --session first-run
-```
-
-`run` executes `work -> verify -> ship`. `report` turns the session evidence into a readable `REPORT.md`. It does not apply by default. `apply` is always explicit and requires a verified `SHIP_READY` live-work diff.
+This creates a disposable target project and runs `doctor -> build -> report -> gate status`. It uses mock providers and does not call Claude, Codex, Gemini, or paid APIs.
 
 To initialize another local repository with the published alpha:
 
@@ -225,20 +236,6 @@ cd /path/to/my-project
 npx -y @ps-neko/nekowork@alpha init --profile developer --project-root .
 ```
 
-Advanced path:
-
-```text
-ask -> plan -> team -> work -> verify -> gate -> ship -> report -> apply
-```
-
-Legacy compatibility smoke:
-
-```bash
-node scripts/cli.js review "check the project setup" --no-ship --session first-smoke
-```
-
-The default review path uses mock providers, so it does not need API keys or provider CLIs.
-
 For the fuller first-run guide, see [docs/QUICKSTART.md](docs/QUICKSTART.md).
 
 For the trust and recovery model, see [Safety Guarantees](docs/SAFETY-GUARANTEES.md), [Failure Modes](docs/FAILURE-MODES.md), [Trust Model](docs/TRUST-MODEL.md), and [Why Not Autopilot](docs/WHY-NOT-AUTOPILOT.md).
@@ -251,11 +248,11 @@ npm run demo:external
 
 To inspect small case-study targets, see [examples/trading-dashboard-mock](examples/trading-dashboard-mock), [examples/github-actions-hardening](examples/github-actions-hardening), [examples/quality-lifecycle-smoke](examples/quality-lifecycle-smoke), and [docs/case-studies](docs/case-studies). They demonstrate financial UI, CI workflow, quality lifecycle, npm package, auth parser, Python protocol library, and environment configuration flows while still preserving Codex verification, Human Gate policy, and explicit apply control.
 
-## What You Get
+## Output Shape
 
 ```text
 doctor ... OK
-run workflow ... OK
+build workflow ... OK
 report ... OK
 gate status ... OK
 Demo completed: verdict=approve_with_fixes, ship_ready=false, applied=false
@@ -268,25 +265,14 @@ Outputs are written under:
 .harness/state/sessions/<session-id>/REPORT.md
 ```
 
-## Use It In Another Project
-
-Shortest npm alpha install shape:
-
-```bash
-cd <target-project>
-npx -y @ps-neko/nekowork@alpha init --profile developer --project-root .
-npx -y @ps-neko/nekowork@alpha check --project-root .
-```
-
-Repository-pinned install shape:
+## Repository-Pinned Install
 
 ```bash
 cd <target-project>
 git submodule add https://github.com/Ps-Neko/NEKOWORK.git .harness-tool
 node .harness-tool/scripts/portability/simulate-port.js . --profile developer --verbose
 node .harness-tool/scripts/install-apply.js --profile developer --project-root .
-node .harness-tool/scripts/cli.js doctor --project-root . --quick
-node .harness-tool/scripts/cli.js plan "first NEKOWORK smoke" --project-root .
+node .harness-tool/scripts/cli.js check --project-root .
 ```
 
 The HARNESS tool root stays in `.harness-tool/`. Session state, generated harness files, and git work happen in the target project root.
@@ -327,6 +313,7 @@ The public alpha surface is intentionally small:
 - `ship`: produce a ship/no-ship readiness handoff after Codex verification
 - `apply`: apply a verified `SHIP_READY` live-work diff to the target project
 - `run`: execute the decomposed wrapper, `work -> verify -> ship`, with optional apply
+- `build`: one-command builder wrapper with `fast`, `safe`, `team`, `tdd`, and `release` modes
 - `report`: summarize session evidence into `REPORT.md` without project mutation
 - `review`: run the legacy full Claude-led/Codex-reviewed workflow
 - `review-cycle`: explicit compatibility alias for the legacy full review workflow
@@ -336,12 +323,15 @@ Advanced features such as `team-lite`, `ralph`, `wait`, instincts, cost tracking
 
 `plan` is recommended before `work` for larger changes. The current `run` command intentionally stays compact: it runs `work -> verify -> ship`, records acceptance criteria through `work`, and applies only when `--apply` is explicitly provided.
 
-Use `--profile quality` or `--profile security` on `work`, `verify`, and `run` when a task needs stronger evidence prompts. Add `--strict-quality` to `verify` or `run` when missing evidence or acceptance coverage should become a fix-required verdict before ship.
+Use `build "<task>" --mode fast` when NEKOWORK should be the single entrypoint. Use `--mode safe` for security-sensitive work, `--mode team` for read-only multi-perspective planning before implementation, `--mode tdd` for strict acceptance evidence, and `--mode release` for readiness-focused work. `build` still uses one executor for writes, Codex verification before ship, and explicit apply only.
+
+Use `--profile quality` or `--profile security` on `work`, `verify`, and `run` when a task needs stronger evidence prompts. Add `--strict-quality` to `verify`, `run`, or `build` when missing evidence or acceptance coverage should become a fix-required verdict before ship.
 
 Use official packs when choosing an install shape:
 
 ```bash
 node scripts/install-plan.js --list
+node scripts/install-plan.js --pack builder
 node scripts/install-plan.js --pack quality
 node scripts/install-plan.js --pack security --target codex --json
 ```
@@ -354,8 +344,8 @@ Packs are aliases over validated profiles. They add clearer product packaging wi
 - Skills: 10
 - Hooks: 5
 - Modules: 7
-- Profiles: `core`, `developer`, `security`, `product`, `quality`, `frontend`, `testing`, `research`, `full`
-- Official packs: `core`, `quality`, `security`, `frontend`, `testing`, `release`, `enterprise`
+- Profiles: `core`, `developer`, `builder`, `security`, `product`, `quality`, `frontend`, `testing`, `research`, `full`
+- Official packs: `core`, `builder`, `quality`, `security`, `frontend`, `testing`, `release`, `enterprise`
 - Harness targets: `claude`, `codex`, `cursor`, `gemini`, `opencode`
 
 Key skills:
@@ -377,6 +367,8 @@ Key skills:
 node scripts/cli.js doctor
 node scripts/cli.js doctor --quick --gemini-smoke
 npm run demo:quick
+node scripts/cli.js build "builder smoke" --mode team --session build-smoke
+node scripts/cli.js report --session latest
 node scripts/install-plan.js --list
 node scripts/install-plan.js --pack quality
 node scripts/install-plan.js --profile developer
@@ -421,11 +413,12 @@ npm run security:hardening
 npm pack --dry-run --json
 ```
 
-`npm pack --dry-run --json` currently produces a package named like `ps-neko-nekowork-0.1.0-alpha.4.tgz`. It does not publish.
+`npm pack --dry-run --json` currently produces a package named like `ps-neko-nekowork-0.1.0-alpha.6.tgz`. It does not publish.
 
 ## Documentation
 
 - [docs/QUICKSTART.md](docs/QUICKSTART.md) - first run and common paths
+- [docs/BUILD.md](docs/BUILD.md) - build command modes and invariants
 - [docs/WHY-NEKOWORK.md](docs/WHY-NEKOWORK.md) - comparison and product positioning
 - [docs/CATALOG-PACKS.md](docs/CATALOG-PACKS.md) - curated catalog, official packs, and case-study evidence
 - [docs/PUBLISH-ALPHA.md](docs/PUBLISH-ALPHA.md) - public npm alpha release plan
@@ -446,7 +439,7 @@ npm pack --dry-run --json
 - [docs/RUNBOOK.md](docs/RUNBOOK.md) - operations guide
 - [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) - system architecture
 - [docs/PRODUCT-PRINCIPLES.md](docs/PRODUCT-PRINCIPLES.md) - product position, invariants, CLI phase semantics
-- [docs/AI-DEVELOPMENT-LIFECYCLE.md](docs/AI-DEVELOPMENT-LIFECYCLE.md) - quality runtime and disciplined AI development lifecycle
+- [docs/AI-DEVELOPMENT-LIFECYCLE.md](docs/AI-DEVELOPMENT-LIFECYCLE.md) - AI development OS, quality runtime, and disciplined lifecycle
 - [docs/CORE-INVARIANTS.md](docs/CORE-INVARIANTS.md) - non-negotiable runtime safety rules
 - [docs/CLI-STAGES.md](docs/CLI-STAGES.md) - stage contract and compatibility transition
 - [docs/RISK-CLASSIFIER.md](docs/RISK-CLASSIFIER.md) - shared risk tags, challenge, and gate policy

package/agent.yaml

@@ -1,8 +1,8 @@
 spec_version: gitagent/0.1.0
 name: nekowork
 runtime_name: harness
-version: 0.1.0-alpha.4
-description: "NEKOWORK HARNESS - Local-first multi-AI development verification runtime"
+version: 0.1.0-alpha.6
+description: "NEKOWORK HARNESS - Local-first AI development OS and quality runtime"
 license: MIT
 homepage: https://github.com/Ps-Neko/NEKOWORK
 # authors: contributor 목록은 git 히스토리로 갈음. 별도 명시 안 함.
@@ -89,6 +89,7 @@ profiles:
   available:
     - core
     - developer
+    - builder
     - security
     - product
     - quality

package/docs/ADVANCED.md

@@ -1,6 +1,6 @@
 # Advanced Features
 
-The public alpha path focuses on `doctor`, `ask`, `plan`, `team`, `work`, `verify`, `gate`, `ship`, `apply`, `run`, `review`, `review-cycle`, and install/apply. This page keeps the larger runtime surface discoverable without crowding the first-run docs.
+The public alpha path focuses on `doctor`, `build`, `report`, `gate`, and the decomposed `ask`, `plan`, `team`, `work`, `verify`, `ship`, `apply`, `run`, `review`, `review-cycle`, and install/apply surfaces. This page keeps the larger runtime surface discoverable without crowding the first-run docs.
 
 ## team
 
@@ -184,12 +184,37 @@ Outputs:
 - `.harness/state/sessions/<id>/run-summary.json`
 - all normal `work`, `verify`, `ship`, and optional `apply` outputs
 
+## build
+
+`build` is the public one-command builder wrapper:
+
+```bash
+node scripts/cli.js build "implement this safely" --mode fast --session build-smoke
+node scripts/cli.js build "auth-sensitive change" --mode safe --session auth-smoke
+node scripts/cli.js build "scope with team thinking" --mode team --session team-smoke
+```
+
+Rules:
+
+- `fast` runs the compact safe path through `run`.
+- `safe` uses the security profile, strict quality, and Codex challenge.
+- `team` creates read-only team handoffs before the single executor runs.
+- `tdd` uses strict quality and acceptance evidence.
+- `release` focuses on ship/readiness and report evidence.
+- `apply` is never implicit; use `--apply` only for verified live-work diffs.
+
+Outputs:
+
+- `.harness/state/sessions/<id>/build-summary.json`
+- all normal `run`, `work`, `verify`, `ship`, and optional `apply` outputs
+
 ## report
 
 `report` turns existing session evidence into a readable inspect-only report:
 
 ```bash
 node scripts/cli.js report --session run-smoke
+node scripts/cli.js report --session latest
 node scripts/cli.js report --session run-smoke --stdout
 node scripts/cli.js report --session run-smoke --output docs/session-report.md
 ```
@@ -199,7 +224,7 @@ Rules:
 - Reads summaries, markers, acceptance criteria, and handoffs from `.harness/state/sessions/<id>/`.
 - Writes `REPORT.md` and `report-summary.json` by default.
 - Does not call providers, run git commands, apply diffs, or mutate target project files.
-- Can run after `ask`, `work`, `verify`, `ship`, `run`, or `apply`.
+- Can run after `ask`, `work`, `verify`, `ship`, `run`, `build`, or `apply`.
 
 Outputs:
 

package/docs/AI-DEVELOPMENT-LIFECYCLE.md

@@ -1,23 +1,24 @@
 # AI Development Lifecycle
 
-NEKOWORK is a local-first AI development quality runtime. Its job is not to collect every useful agent feature; its job is to make AI development disciplined, high-quality, independently verified, and human-gated.
+NEKOWORK is a local-first AI development OS and quality runtime. Its job is not to collect every useful agent feature; its job is to make AI development fast, disciplined, high-quality, independently verified, and human-gated.
 
 ## Position
 
 ```text
-Good development habits
+Fast build loop
++ good development habits
 + quality rules, hooks, and skills
 + product-aware scope control
 + read-only multi-agent thinking
 + Codex verification
 + Human Gate and explicit apply
-= NEKOWORK gated AI development runtime
+= NEKOWORK gated AI development OS
 ```
 
 The short slogan remains:
 
 ```text
-Claude work -> Codex verification -> Human Gate
+fast AI build -> Codex verification -> Human Gate -> explicit apply
 ```
 
 ## Product Rules
@@ -29,6 +30,7 @@ Claude work -> Codex verification -> Human Gate
 5. Multiple agents may think, but only one executor writes.
 6. Rich skills, hooks, and rules may improve quality, but cannot weaken safety.
 7. Apply is explicit and evidence-based.
+8. Build modes may improve speed, but cannot bypass verification or gates.
 
 ## Absorption Model
 
@@ -40,6 +42,7 @@ External project ideas are absorbed as capabilities, not as a new architecture:
 | Rich agent environment | Skills, hooks, rules, MCP, memory, scanner-style checks | Profile/module based selective install |
 | Product questioning | Product, design, QA, release, and scope control questions | `ask`, `plan`, and `product` profile |
 | Team orchestration | Multiple perspectives and parallel review | `team` read-only handoffs |
+| Productivity/autopilot-lite | One command for implementation, verification, and readiness | `build` modes over `run`; apply remains explicit |
 | NEKOWORK core | Codex verification, Human Gate, controlled apply | Non-bypassable runtime invariants |
 
 Capabilities can expand. The architecture cannot weaken the verification loop.
@@ -60,6 +63,16 @@ ask
 
 Quality enters early through `ask` and `plan`, not only at the final review step. Team mode collects multiple perspectives, but the write phase stays single-executor. Verification is independent, gate decisions are explicit, `report` makes evidence readable, and apply requires evidence.
 
+For the one-command product experience, `build` selects a safe preset over the same loop:
+
+```bash
+nekowork build "implement feature" --mode fast
+nekowork build "auth-sensitive change" --mode safe
+nekowork build "scope through QA first" --mode team
+nekowork build "test-first change" --mode tdd
+nekowork build "prepare release handoff" --mode release
+```
+
 ## Quality Profile
 
 The `quality` profile is the disciplined-development bundle:

package/docs/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # Architecture
 
-NEKOWORK is the product. HARNESS is the local runtime packaged by NEKOWORK as a local-first AI development harness. The project keeps one canonical catalog and projects it into multiple agent surfaces.
+NEKOWORK is the product. HARNESS is the local runtime packaged by NEKOWORK as a local-first AI development OS and quality harness. The project keeps one canonical catalog and projects it into multiple agent surfaces.
 
 ## Core Idea
 
@@ -25,10 +25,10 @@ The canonical source is the repository catalog. Generated harness directories ar
 
 ## Product Invariants
 
-NEKOWORK is a verification runtime, not a general agent pack:
+NEKOWORK is an AI development OS bounded by a verification runtime, not a general agent pack:
 
 ```text
-Claude work -> Codex verification -> Human Gate
+fast AI build -> Codex verification -> Human Gate -> explicit apply
 ```
 
 Core invariants:
@@ -50,7 +50,7 @@ User command
         |
         |-- doctor
         |-- install plan/apply
-        |-- ask / plan / team / work / verify / gate / ship / report / apply / run / review / review-cycle
+        |-- ask / plan / team / work / verify / gate / ship / report / apply / run / build / review / review-cycle
         |-- ralph
         |-- team-lite
         |-- sessions / costs / instincts
@@ -87,6 +87,7 @@ node scripts/cli.js ship "ship readiness" --session work-smoke --project-root <t
 node scripts/cli.js report --session work-smoke --project-root <target>
 node scripts/cli.js apply --session work-smoke --project-root <target>
 node scripts/cli.js run "decomposed wrapper" --session run-smoke --project-root <target>
+node scripts/cli.js build "safe builder wrapper" --mode team --session build-smoke --project-root <target>
 node scripts/cli.js review "change request" --no-ship --project-root <target>
 node scripts/cli.js review-cycle "legacy full-cycle request" --no-ship --project-root <target>
 ```
@@ -137,6 +138,8 @@ ask -> plan -> team -> work -> verify -> gate -> ship -> report -> apply
 
 `run` is the compatibility-friendly wrapper around the decomposed path. It runs `work -> verify -> ship` and only runs `apply` when `--apply` is explicitly requested and `SHIP_READY` exists. New automation should prefer `run` or the explicit decomposed commands; old automation can continue to use `review` or `review-cycle`.
 
+`build` is the safe one-command builder entrypoint. It applies named mode presets (`fast`, `safe`, `team`, `tdd`, `release`) over the existing safe loop, records `build-summary.json`, and keeps apply explicit.
+
 `ralph` is an advanced repeated-iteration loop. Its default engine remains legacy `review` for compatibility, but `ralph --engine run` repeats the decomposed wrapper and records child run sessions. Ralph does not apply diffs; verified mutation still flows through `apply`.
 
 `wait` is an advanced persistent wakeup daemon. It watches session `wakeup.json` files, parses the session `active` contract, and resumes only supported modes (`ralph`, `run`, `review-cycle`). It writes `wait-summary.json` / `wait-events.jsonl`, backs off failed resumes, and refuses to resume sessions with `HUMAN_GATE`.
@@ -202,8 +205,8 @@ Builders project the catalog into tool-specific files:
 
 ## Release State
 
-The current release line is `0.1.0-alpha.4`:
+The current repository release line is `0.1.0-alpha.6`:
 
 - Repository and GitHub tarball release are available.
-- Public npm alpha is published as `@ps-neko/nekowork@alpha`.
+- Public npm alpha is published as `@ps-neko/nekowork@alpha` and currently points at `0.1.0-alpha.6`.
 - Clone, submodule, and local checkout integration remain supported for repository-pinned workflows.

package/docs/AUDIT.md

@@ -2,22 +2,22 @@
 
 Status date: 2026-05-08
 
-This audit summarizes the current NEKOWORK state after publishing the `0.1.0-alpha.4` public alpha. It replaces the older week-by-week scratch audit, which contained stale planning notes and encoding damage.
+This audit summarizes the current NEKOWORK state after publishing the `0.1.0-alpha.6` public alpha.
 
 ## Current Status
 
 | Area | Status | Notes |
 |---|---|---|
-| Package metadata | OK | `@ps-neko/nekowork@0.1.0-alpha.4`, `agent.yaml` uses `name: nekowork`, `runtime_name: harness`, and matching version |
-| npm publish | OK | `@ps-neko/nekowork@alpha` points at `0.1.0-alpha.4` |
+| Package metadata | OK | repository version `@ps-neko/nekowork@0.1.0-alpha.6`, `agent.yaml` uses `name: nekowork`, `runtime_name: harness`, matching version, and `nekowork`/`harness` CLI bins |
+| npm publish | OK | `@ps-neko/nekowork@alpha` points at `0.1.0-alpha.6` |
 | Source install | OK | Clone, local checkout, and submodule workflows are documented |
-| Public npm alpha | OK | `docs/PUBLISH-ALPHA.md` records the first alpha publish and the `0.1.0-alpha.4` alpha update |
+| Public npm alpha | OK | `docs/PUBLISH-ALPHA.md` records alpha publishes through `0.1.0-alpha.6` |
 | CLI doctor/check | OK | `check`, `doctor`, `doctor --quick`, and `doctor --gemini-smoke` are available |
 | Provider auth | OK | Local delegated CLI auth is the default path |
 | Internal provider adapter | OK | `HARNESS_PROVIDER_OVERRIDE=internal` can call an explicit JSON command adapter without weakening gates |
-| Catalog | OK | 7 official packs, 11 agents, 10 skills, 5 hooks, 7 modules, 36 components, 9 profiles |
+| Catalog | OK | 8 official packs, 11 agents, 10 skills, 5 hooks, 7 modules, 36 components, 10 profiles |
 | Multi-harness output | OK | Claude, Codex, Cursor, Gemini, and OpenCode builders are present |
-| Quick demo | OK | `npm run demo:quick` verifies the shortest no-API `doctor -> run -> report -> gate status` path |
+| Quick demo | OK | `npm run demo:quick` verifies the shortest no-API `doctor -> build -> report -> gate status` path |
 | Fresh npm alpha smoke | OK | CI runs `npx -y @ps-neko/nekowork@alpha check --json` from a disposable directory |
 | Report UX | OK | `report` writes inspect-only `REPORT.md` and `report-summary.json` from session evidence |
 | External demo | OK | `npm run demo:external` verifies a disposable target project flow |
@@ -30,7 +30,7 @@ This audit summarizes the current NEKOWORK state after publishing the `0.1.0-alp
 | Persistent wakeup | OK | `wait` resumes supported active sessions and blocks on `HUMAN_GATE` |
 | Generated docs | OK | CODEMAP output is stable ASCII and reproducible |
 | Tests | OK | Unit, integration, and e2e suites pass locally and in CI |
-| Release | OK | `v0.1.0-alpha.4` is tagged and published as a GitHub prerelease |
+| Release | OK | `v0.1.0-alpha.6` is tagged and published as a GitHub prerelease |
 
 ## Verification Gates
 
@@ -55,7 +55,7 @@ Current local result for this working tree:
 - `npm run test:unit`: covered by full `npm test`
 - `npm run validate:all`: pass
 - `npm run lint`: pass
-- `npm test`: 252 tests pass
+- `npm test`: 263 tests pass
 - quick run demo: pass through `npm run demo:quick -- --cleanup`
 - external project e2e smoke: pass through `npm test`
 - `node scripts/sync-claude-md.js --check`: pass
@@ -63,13 +63,14 @@ Current local result for this working tree:
 - `npm audit --audit-level=moderate`: 0 vulnerabilities
 - `npm pack --dry-run --json`: pass
 - `npm publish --dry-run --access public --tag alpha`: pass
-- `npm publish --access public --tag alpha`: `0.1.0-alpha.4` published
-- `npm view @ps-neko/nekowork dist-tags version versions --json`: `alpha` points at `0.1.0-alpha.4`; `latest` remains `0.1.0-alpha.0`
-- `npx -y @ps-neko/nekowork@alpha check`: passed for `0.1.0-alpha.4` with WARN summary from non-git project root and Gemini auth not checked
+- `npm publish --access public --tag alpha`: `0.1.0-alpha.6` published
+- `npm view @ps-neko/nekowork dist-tags version versions --json`: `alpha` points at `0.1.0-alpha.6`; `latest` remains `0.1.0-alpha.0`
+- `npx -y @ps-neko/nekowork@alpha check`: passed for `0.1.0-alpha.6` with WARN summary from Gemini auth not checked
 
 ## Completed Work
 
 - Local-first provider auth policy implemented and documented.
+- `build` is the beginner entrypoint with `fast`, `safe`, `team`, `tdd`, and `release` modes over the safe run/report/gate loop.
 - Internal provider command adapter implemented and documented without bypassing verification, Human Gate, or apply controls.
 - `acceptance-coverage` skill added as a focused quality evidence helper.
 - API-key override warnings and guards are in place.
@@ -93,7 +94,7 @@ Current local result for this working tree:
 - Official packs expose curated install shapes without creating a second safety model.
 - Checked-in example fixtures now cover financial UI, CI hardening, and quality lifecycle evidence flows.
 - Third-party case studies record NEKOWORK runs against `sindresorhus/is-plain-obj`, `jshttp/basic-auth`, `python-hyper/h11`, and `motdotla/dotenv`.
-- Public npm alpha `0.1.0-alpha.4` is published under the `alpha` dist-tag.
+- Public npm alpha `0.1.0-alpha.6` is published under the `alpha` dist-tag.
 
 ## Remaining Optional Work
 
@@ -113,7 +114,7 @@ Current local result for this working tree:
 
 ## External Readiness Score
 
-Current external readiness, excluding broader adoption evidence: **9.1 / 10**.
+Current external readiness, excluding broader adoption evidence: **9.2 / 10**.
 
 Main deductions: