devrites 3.0.2 → 3.0.4

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [3.0.4](https://github.com/ViktorsBaikers/DevRites/compare/v3.0.3...v3.0.4) (2026-07-20)
+
+### Fixed
+
+* **ci:** harden supply chain checks ([d902574](https://github.com/ViktorsBaikers/DevRites/commit/d902574a7d30168fcef94aa4a3dae7707191fe8d))
+* **devrites:** normalize canonical workspace files ([e70221f](https://github.com/ViktorsBaikers/DevRites/commit/e70221f5dd9fbda0f3a73c500a493497bc023a91))
+
+## [3.0.3](https://github.com/ViktorsBaikers/DevRites/compare/v3.0.2...v3.0.3) (2026-07-20)
+
+### Fixed
+
+* **rite:** centralize workflow schema ([58bd55e](https://github.com/ViktorsBaikers/DevRites/commit/58bd55e8472a98be1073bcfa5fe7593e7bf0c5d1))
+
 ## [3.0.2](https://github.com/ViktorsBaikers/DevRites/compare/v3.0.1...v3.0.2) (2026-07-20)
 
 ### Fixed

package/README.md

@@ -115,7 +115,7 @@ Full diagram set (lifecycle, polish orchestrator, review fan-out, debug loop,
 rules carrier, workspace state, namespace map) →
 [`docs/flow.md`](docs/flow.md).
 
-**Status:** [`v3.0.2`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v3.0.2) — see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v3.0.4`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v3.0.4) — see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 ## Contents
 

package/docs/adr/0001-go-engine-as-control-plane.md

@@ -0,0 +1,43 @@
+# ADR-0001: Go engine as deterministic control plane
+
+- **Status:** Accepted
+- **Date:** 2026-07-08 (backfilled; decision predates the ADR log)
+
+> Network scope was narrowed by [ADR-0008](0008-sanctioned-engine-network-boundary.md):
+> deterministic workspace operations remain network-free, while explicit
+> updater/source-cache I/O is isolated in `internal/iohooks`.
+
+## Context
+
+DevRites orchestrates an LLM through a spec-driven lifecycle. Two kinds of work
+are entangled: **judgment** (is this spec good? is this code right?) which only
+a model can do, and **bookkeeping** (which phase are we in? are the required
+sections present? what's the next question id?) which must be exact, fast, and
+identical every run. Letting the model do the bookkeeping makes the process
+non-reproducible and burns context on arithmetic.
+
+## Decision
+
+Ship a single statically-linked Go binary (`CGO_ENABLED=0`, stdlib-only, zero
+third-party deps in the hot path) as the **control plane**: it owns all
+deterministic state transitions, gates, and derivations over `.devrites/`. It
+makes **no** model or network calls. The filesystem is the data plane; the LLM
+supplies judgment. Commands are a hand-rolled `switch` dispatch, not a CLI
+framework.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Bookkeeping inside the agent prompt | Non-deterministic, context-hungry, unauditable — the exact failure this system exists to remove. |
+| Node/TS engine (like the reference system GSD Core) | Drags a package tree + supply-chain surface; the pure-Go single binary has none and cross-compiles to every target from one runner. |
+| Cobra / urfave CLI framework | A dependency and a config surface for a switch statement the stdlib already handles. |
+
+## Consequences
+
+- Reproducible process: same state in, same verdict out, no wall-clock or
+  network variance (the one remaining wall-clock read is now seamed — ADR-0006).
+- Zero-dependency binary: trivial supply chain, `go install`-able, no runtime.
+- Cost: the engine can express only what's deterministic. Anything needing
+  judgment must round-trip to the model — by design.
+- The engine is the trust root, so it carries the strictest CI gates (ADR-0006).

package/docs/adr/0002-dual-host-harness.md

@@ -0,0 +1,34 @@
+# ADR-0002: Dual-host harness (Claude + Codex)
+
+- **Status:** Accepted
+- **Date:** 2026-07-08 (backfilled)
+
+## Context
+
+Each AI coding host (Claude Code, Codex, and — in adjacent tools — Cursor,
+Cline, Copilot) speaks its own hook dialect: different stdin shapes, exit-code
+conventions, and settings surfaces. The lifecycle logic (orient, gate, hook
+decisions) is host-independent; only the edge translation differs.
+
+## Decision
+
+Support exactly **two** hosts today — `claude` and `codex` — behind a thin
+`internal/harness` adapter that translates each host's hook stdin/exit
+conventions into the shared `orient` + `gate` core. Host support is
+enumerated in code, not open-ended. `harness-matrix --check` keeps
+`docs/harness-compliance.md` in sync with the adapters (drift is a CI failure).
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| A generic declarative capability/adapter registry now (the GSD Core model) | Real ceiling-raiser for N hosts, but a large refactor unjustified at N=2. Recorded as a Proposed follow-up, not built. See the adoption study in `docs/research/gsd-core-adoption.md` §3.1. |
+| Claude-only | Codex users are already real; single-host would strand them. |
+| Per-host forks of the logic | Duplicates the lifecycle core across edges — the thing the adapter exists to prevent. |
+
+## Consequences
+
+- Adding a host today means editing `harness.go` — acceptable friction at N=2,
+  the calcification risk rises with N (hence the Proposed registry follow-up).
+- The shared core is tested once; only edge translation is host-specific.
+- `harness-matrix --check` makes host-support drift visible in CI.

package/docs/adr/0003-gate-model-hitl-pause.md

@@ -0,0 +1,38 @@
+# ADR-0003: Gates block as a HITL pause, never a crash
+
+- **Status:** Accepted
+- **Date:** 2026-07-08 (backfilled)
+
+## Context
+
+A gate is a deterministic completeness check — e.g. "does this feature have the
+sections required to leave the current phase?" When a gate is not satisfied the
+engine must stop the agent, but *how* it stops matters. A crash (non-zero,
+stderr stack) reads as a tool failure and invites the agent to retry blindly or
+route around it. The intended meaning is the opposite: **the work is
+incomplete, pause and involve the human.**
+
+## Decision
+
+A blocked gate is a structured **human-in-the-loop pause**: a specific
+"missing X" message on stdout and a distinct, reserved **exit code 3** — never a
+crash, never a generic non-zero. Gates are **transition-fired** (they run only
+when explicitly invoked at a phase boundary, not on every tool call). Two
+kinds: `Readiness` (sections needed to leave the current phase) and `Seal` (the
+full seal set). `StopGate` enforces the rest-point invariant: a feature claiming
+completion with empty proof, or with `.red` set, cannot end the turn.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Exit 1 / crash on an unmet gate | Indistinguishable from a real error; agents retry or route around it instead of pausing for the human. |
+| Run gates on every tool call | Turns a transition check into per-action overhead and noise; gates are boundary events. |
+| Auto-advance past a soft-missing section | Defeats the completeness guarantee the gate exists to provide. |
+
+## Consequences
+
+- Exit 3 is a reserved, load-bearing contract — the harness and hooks branch on
+  it. Its guard test (`tests/adr_0003_gate_exit_code_test.go`) locks it.
+- Blocks are legible: the agent (and human) see exactly which section is missing.
+- Gate authors must classify a stop as "incomplete" (exit 3) vs a true error.

package/docs/adr/0004-state-schema-phases-sections.md

@@ -0,0 +1,47 @@
+# ADR-0004: Phase-relative section completeness
+
+- **Status:** Accepted
+- **Date:** 2026-07-08 (backfilled)
+
+> Artifact filename direction was amended by
+> [ADR-0007](0007-canonical-live-workspace-filenames.md). Phase-relative section
+> completeness remains unchanged.
+
+## Context
+
+A feature's working state must be legible to both humans and the engine, and
+"is it complete?" must be answerable deterministically at each step of the
+lifecycle. A single long document makes completeness opaque and burns context;
+a rigid "all fields required always" model blocks early phases on artifacts
+that don't exist yet (there's no proof during framing).
+
+## Decision
+
+Model feature state as **six single-concern sections** — `spec`, `plan`,
+`decisions`, `tasks`, `proof`, `status`. Drive the lifecycle
+through the ordered rite-\* arc:
+`frame → spec → temper → define → plan → vet → build → converge → prove → polish → review → seal → ship → done`.
+Completeness is **phase-relative and additive**: the typed phase registry maps
+each phase to the sections that must have real content to leave it; a section
+not yet required never blocks. `SchemaVersion = 1`; a feature may declare its
+own and the engine refuses anything newer than it understands. Files evolve
+additively.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| One `feature.md` mega-document | Completeness isn't self-evident; every read pays for the whole file. |
+| All sections required in every phase | Blocks framing/spec phases on proof/tasks that legitimately don't exist yet. |
+| Status inferred from git / external tracker | Couples state to a tool outside the workspace; breaks the git-diffable, self-contained record. |
+
+## Consequences
+
+- Completeness is a table lookup, not a judgment call — cheap and reproducible.
+- Small files stay context-cheap and make "what's missing" self-evident.
+- `SchemaVersion = 1` is young; migration is single-version. Hardening the
+  writer into one pure transition function is a recorded follow-up
+  (`docs/research/gsd-core-adoption.md` §3.2).
+- The typed registry in `engine/internal/state/schema.go` is the lifecycle
+  authority. Its invariant tests lock order, aliases, commands, requirements,
+  and cross-format manifest freshness.

package/docs/adr/0005-hooks-as-engine-subcommands.md

@@ -0,0 +1,39 @@
+# ADR-0005: Hooks are engine subcommands, not shell scripts
+
+- **Status:** Accepted
+- **Date:** 2026-07-08 (backfilled; see commits porting `reviewer-readonly`,
+  `subagent-orient`, and the guard hooks into the Go engine)
+
+## Context
+
+Lifecycle hooks (orient on session start, readonly-guard for reviewers,
+stop-gate, statusline, redwatch, …) began as standalone `pack/.claude/hooks/*.sh`
+scripts. Shell hooks drift from the engine's own state logic, are hard to test
+in isolation, behave differently across the two hosts, and duplicate parsing the
+engine already does.
+
+## Decision
+
+Hooks are **subcommands of the one Go binary**: `devrites-engine hook <id>`.
+The pack ships only `hooks.json` wiring plus host settings; every hook's logic
+lives in the engine, sharing the `orient`/`gate`/`state` core. A control plane
+selects which hooks fire: `DEVRITES_HOOK_PROFILE` (minimal / standard / strict)
+and `DEVRITES_DISABLED_HOOKS`. Each hook has a golden parity test
+(`tests/parity_*_test.go`) pinning its stdout + exit across both hosts.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Keep hooks as `.sh` scripts | Drift from engine state logic, per-host divergence, poor testability, duplicated parsing. |
+| One monolithic hook entry point | Loses per-hook enable/disable and per-hook golden tests. |
+| Node hook runtime | Reintroduces a runtime dependency ADR-0001 deliberately avoids. |
+
+## Consequences
+
+- Hooks are unit-testable Go with golden parity snapshots, not shell fixtures.
+- One implementation serves both hosts; the harness (ADR-0002) handles edge
+  translation.
+- Profiles make the hook surface tunable without editing wiring.
+- The pack's `hooks/*.sh` files are removed; `hooks.json` is the only pack-side
+  hook artifact.

package/docs/adr/0006-clock-seam-and-engine-ci-gates.md

@@ -0,0 +1,50 @@
+# ADR-0006: Clock seam + Go static-analysis CI gates
+
+- **Status:** Accepted
+- **Date:** 2026-07-08
+
+## Context
+
+Two gaps surfaced while studying a more mature peer system (GSD Core; see
+`docs/research/gsd-core-adoption.md`):
+
+1. **Unwired static analysis.** `engine/Makefile` defined `staticcheck` and
+   `govulncheck` targets, but CI ran only `gofmt` + `go vet`. No `-race`, no
+   custom analysis on the trust-root binary.
+2. **A wall-clock leak.** `resolve next-qid` derived today's date from a raw
+   `time.Now()` with no seam, so its golden snapshot was pinned to the date it
+   was recorded and failed **every other day** — a latent red the peer system's
+   clock-seam lint would have caught at author time.
+
+## Decision
+
+- **Clock seam.** Wall-clock reads in the resolve command flow through one
+  overridable point, `clockNow()`, honoring `DEVRITES_NOW` (RFC-3339 or bare
+  `YYYY-MM-DD`). Date-derived output is deterministic under test; goldens pin the
+  clock instead of tracking the real date.
+- **Engine CI gates.** The `engine` CI job installs pinned `staticcheck`
+  (2025.1.1) + `govulncheck` and runs both as **blocking** steps, and runs the
+  suite with `-race`. `make quality` mirrors this so a green local gate means a
+  green pipeline.
+- **Coverage** is measured (`make cover`) but **not** yet a hard floor: the
+  number is understated because most behaviour is exercised through CLI-level
+  integration tests in `tests/` that don't attribute to per-package coverage.
+  A ratchet-only floor is a follow-up once attribution is meaningful.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Regenerate the date golden and move on | Fixes it for one day; the test rots again at the next date boundary. The seam fixes the class. |
+| Introduce `golangci-lint` | New dependency + config surface; `staticcheck` + `govulncheck` were already defined in the Makefile — wire what exists. |
+| Inject a full `Clock` interface everywhere | Heavier than the one failing path needs; the env seam is the minimal correct fix. A shared clock package is a Proposed generalization. |
+| Hard coverage floor now | Misleading at ~23% aggregate due to integration-test attribution; a floor here would gate on noise. |
+
+## Consequences
+
+- The engine suite is deterministic across dates and race-checked; static
+  analysis and CVE scanning block on the trust-root binary.
+- `DEVRITES_NOW` is a supported test seam; other date-deriving commands
+  (`learnings`, `conventions`, `footprint`, `stuck`) still read `time.Now()`
+  directly and can adopt the same seam when they need deterministic output.
+- Guard test `tests/adr_0006_clock_seam_test.go` locks the seam behaviour.

package/docs/adr/0007-canonical-live-workspace-filenames.md

@@ -0,0 +1,36 @@
+# ADR-0007: Canonical live workspace filenames
+
+- **Status:** Accepted
+- **Date:** 2026-07-20
+
+## Context
+
+ADR-0004 established phase-relative `proof` and `status` sections while the
+live workspace later standardized its human-facing artifacts on `README.md`,
+`state.md`, and `evidence.md`. Shipped skills, validators, the typed workflow
+registry, and user documentation already write those names, but migration and
+some engine comments still normalized in the opposite direction.
+
+## Decision
+
+Use `README.md`, `state.md`, and `evidence.md` as the canonical live workspace
+map, cursor, and proof log. Continue reading `feature.md`/`index.md`, `status.md`,
+and `proof.md` as compatibility aliases. `devrites-engine migrate` adds missing
+canonical files from aliases without deleting or overwriting either form.
+Internal `proof` and `status` section identifiers remain conceptual completeness
+names, not canonical filename declarations.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Restore `feature.md`, `status.md`, and `proof.md` as canonical | Would reverse the shipped workspace contract and require coordinated changes across skills, validators, docs, fixtures, and generated hosts. |
+| Treat both directions as equally canonical | Makes migration non-idempotent and leaves writers without one preferred target. |
+| Delete aliases after migration | Risks data loss and breaks existing workspaces and older installed packs. |
+
+## Consequences
+
+- Migration direction matches the files produced and required by the live pack.
+- Existing aliases remain losslessly readable and are preserved on disk.
+- Schema version remains `1`; this is an additive filename normalization, not a
+  content-schema break.

package/docs/adr/0008-sanctioned-engine-network-boundary.md

@@ -0,0 +1,33 @@
+# ADR-0008: Sanctioned engine network boundary
+
+- **Status:** Accepted
+- **Date:** 2026-07-20
+
+## Context
+
+ADR-0001 described the Go control plane as network-free. The binary now also
+owns explicit installation/update and source-cache operations that require HTTP,
+while deterministic workspace bookkeeping still must not depend on network or
+model responses. The implemented boundary already isolates HTTP in one package.
+
+## Decision
+
+Keep deterministic workspace state, gate, hook, migration, and derivation logic
+network- and model-free. Permit network access only in `internal/iohooks` for
+explicit updater and source-cache operations. No other first-party package may
+import network clients, and no engine package may call a model API.
+
+## Alternatives considered
+
+| Option | Why not |
+|--------|---------|
+| Forbid all network access in the binary | Would remove the verified updater and source-cache refresh behavior users already rely on. |
+| Allow each consumer its own HTTP client | Expands the audit surface and weakens the executable package boundary. |
+| Ship a second updater binary | Adds packaging, release, and cross-platform complexity without improving the existing package isolation. |
+
+## Consequences
+
+- Workspace verdicts remain deterministic and offline-capable.
+- Network behavior has one auditable package and one guard test.
+- The binary as a whole is not network-free; documentation must distinguish the
+  control-plane core from explicit I/O commands.

package/docs/adr/README.md

@@ -0,0 +1,58 @@
+# Architecture Decision Records
+
+An ADR captures **one** load-bearing decision: the context that forced it, the
+decision itself, the alternatives that were rejected and *why*, and the
+consequences accepted. The rejected-alternatives table is the point — it keeps
+the "why not X" from being re-litigated every quarter.
+
+`CLAUDE.md` points every agent here (`CONTEXT.md` + `docs/adr/` are the
+single-context domain record). Keep this directory the source of truth for
+architecture; per-feature `decisions.md` files stay scoped to that feature.
+
+## Convention
+
+- Filename: `NNNN-kebab-title.md`, zero-padded, monotonic.
+- Frontmatter fields: **Status** (Proposed / Accepted / Superseded by NNNN),
+  **Date** (YYYY-MM-DD), **Deciders** (optional).
+- Sections: **Context** → **Decision** → **Alternatives considered** (a table:
+  option · why rejected) → **Consequences**.
+- **Guard test:** an accepted ADR that asserts a runtime invariant SHOULD have a
+  named regression test — `engine/tests/adr_NNNN_*_test.go` — so the decision
+  has an executable proof it still holds. Reference the ADR number in the test's
+  doc comment.
+
+## Template
+
+```markdown
+# ADR-NNNN: <title>
+
+- **Status:** Accepted
+- **Date:** YYYY-MM-DD
+
+## Context
+<the forces: what problem, what constraints, what was true at the time>
+
+## Decision
+<what we chose, stated as a present-tense rule>
+
+## Alternatives considered
+| Option | Why not |
+|--------|---------|
+| ... | ... |
+
+## Consequences
+<what this makes easy, what it costs, what follow-up it implies>
+```
+
+## Index
+
+| ADR | Title | Status | Guard test |
+|-----|-------|--------|-----------|
+| [0001](0001-go-engine-as-control-plane.md) | Go engine as deterministic control plane | Accepted | — |
+| [0002](0002-dual-host-harness.md) | Dual-host harness (Claude + Codex) | Accepted | `tests/parity_*_test.go` |
+| [0003](0003-gate-model-hitl-pause.md) | Gates block as HITL pause, never crash | Accepted | `tests/adr_0003_gate_exit_code_test.go` |
+| [0004](0004-state-schema-phases-sections.md) | Phase-relative section completeness | Accepted | `tests/adr_0004_required_by_phase_test.go` |
+| [0005](0005-hooks-as-engine-subcommands.md) | Hooks are engine subcommands, not shell scripts | Accepted | `tests/parity_*_test.go` |
+| [0006](0006-clock-seam-and-engine-ci-gates.md) | Clock seam + Go static-analysis CI gates | Accepted | `tests/adr_0006_clock_seam_test.go` |
+| [0007](0007-canonical-live-workspace-filenames.md) | Canonical live workspace filenames | Accepted | `internal/migrate/migrate_test.go`, `tests/migrate_cli_test.go` |
+| [0008](0008-sanctioned-engine-network-boundary.md) | Sanctioned engine network boundary | Accepted | `tests/meta_test.go` |

package/docs/command-map.md

@@ -167,7 +167,7 @@ when available, falling back to file reads otherwise:
 See [`flow.md`](flow.md) for the Mermaid diagrams. The text path:
 
 ```
-/rite-spec → /rite-define → /rite-build ×N → /rite-prove → /rite-polish → /rite-review → /rite-seal → /rite-ship
+/rite-frame → /rite-spec → /rite-temper → /rite-define → /rite-vet → /rite-build ×N → /rite-converge → /rite-prove → /rite-polish → /rite-review → /rite-seal → /rite-ship
    │            │                │  ▲              │                          │             (decide)   (execute+close)
    │            │                │  └ Spec Drift Guard → /rite-plan repair ────┘
    │            │                └ devrites-frontend-craft / source-driven / doubt

package/docs/engine/state-schema.md

@@ -54,9 +54,10 @@ Backward compatibility: `.devrites/features/<slug>/` remains readable as a legac
 workspace location. `feature.md` / `index.md` may stand in for `README.md`, and
 `proof.md` may stand in for `evidence.md`.
 
-### `feature.md`
+### Workspace maps
 
-The per-feature index. Its YAML frontmatter carries:
+The canonical per-feature index is `README.md`; `feature.md` and `index.md` are
+readable aliases. A map may carry YAML frontmatter with:
 
 | field           | meaning                                        |
 | --------------- | ---------------------------------------------- |
@@ -65,8 +66,9 @@ The per-feature index. Its YAML frontmatter carries:
 | `phase`         | current workflow phase (see below)             |
 | `schemaVersion` | schema version the file was written against    |
 
-A feature exists iff its `feature.md` exists. A `feature.md` with no `phase`, or
-an unknown `phase`, is an error.
+A feature exists when it has either a live `state.md` ledger or a workspace map.
+The mutable `state.md` cursor is authoritative when both declare a phase; an
+unknown declared phase is an error.
 
 ## Sections
 
@@ -91,16 +93,18 @@ requires only the sections needed to leave it, and the set grows additively down
 the arc. A section that is not yet required (e.g. `proof` during the `spec`
 phase) never blocks.
 
-| phase   | required sections                                     |
-| ------- | ----------------------------------------------------- |
-| `frame` | *(none)*                                              |
-| `spec`  | `spec`                                                |
-| `plan`  | `spec`, `plan`                                         |
-| `build` | `spec`, `plan`, `decisions`, `tasks`                  |
-| `prove` | `spec`, `plan`, `decisions`, `tasks`, `proof`         |
-| `vet`   | `spec`, `plan`, `decisions`, `tasks`, `proof`         |
-| `seal`  | `spec`, `plan`, `decisions`, `tasks`, `proof`, `status` |
-| `ship`  | `spec`, `plan`, `decisions`, `tasks`, `proof`, `status` |
+| phase | required sections |
+| --- | --- |
+| `frame` | *(none)* |
+| `spec`, `temper` | `spec` |
+| `define`, `plan` | `spec`, `plan` |
+| `vet`, `build`, `converge` | `spec`, `plan`, `decisions`, `tasks` |
+| `prove`, `polish`, `review` | `spec`, `plan`, `decisions`, `tasks`, `proof` |
+| `seal`, `ship`, `done` | `spec`, `plan`, `decisions`, `tasks`, `proof`, `status` |
+
+The authoritative typed definitions live in `engine/internal/state/schema.go`.
+`workflow_manifest.json` is a generated derivative for non-Go release tools;
+run `go generate ./internal/state` after editing the registry.
 
 ## `devrites-engine status <slug>`
 

package/docs/flow.md

@@ -270,7 +270,7 @@ erDiagram
         string slug PK ".devrites/work/<slug>/"
     }
     state {
-        string phase "spec | plan | build | prove | polish | review | seal | ship | done"
+        string phase "frame | spec | temper | define | plan | vet | build | converge | prove | polish | review | seal | ship | done"
         string status "running | awaiting_human | blocked | done"
         string active_slice "N — name"
         int afk_slices_remaining "from .devrites/AFK max_slices on first AFK build"