Transforms dev-readyz from an inline implementation spec into an orchestrator matching the dev-multi-tenant and dev-systemplane-migration pattern. The skill now dispatches ring:backend-engineer-{golang,typescript} and ring:frontend-bff-engineer-typescript per gate; the orchestrator only detects, verifies, and enforces order.
Gate 0 runs three phases: stack detection, S1-S9 /readyz compliance audit (endpoint path, status vocabulary, aggregation rule, response fields, TLS detection, ValidateSaaSTLS, metrics, self-probe, graceful drain), and N1-N7 anti-pattern detection (response caching, /ready alias, /health/live+/health/ready split, substring TLS detection, reflection-based TLS, inline SaaS TLS checks, process.exit in Next.js instrumentation). Anti-patterns BLOCK progression until removed. Each S/N check maps to the specific gate that fixes it.
Gate 1.5 generates a visual HTML preview via ring:visualize that the user must approve before any code changes. Gate 9 dispatches 10 parallel reviewers with readyz-specific context. Gate 10 requires explicit user validation. Gate 11 generates an operator activation guide at docs/readyz-guide.md. State is persisted to docs/ring-dev-readyz/current-cycle.json for resume.
The anti-patterns encoded in Gate 0 Phase 3 were identified by auditing real implementations in matcher and plugin-br-bank-transfer: 5-second response cache layer, strings.Contains(uri, "tls=true") substring match, /ready alias path, and missing metrics emission despite otherwise-compliant /readyz handlers.
X-Lerian-Ref: 0x1
feat(systemplane): refactor migration skill for lib-commons v5 API
docs(plugin): update skill counts and keywords for new deck skill
chore(plans): remove obsolete caching and dev-cycle plan documents
Migrate authoritative sources, standards, skills, and platform mirrors from lib-commons v2/v4 to v5.0.2. ~215 line-level replacements across 26 files.
- Authority chain aligned: README, backend-engineer-golang, standards-coverage-table, and dev-team/docs/standards/golang/* now declare v5 as current.
- Code examples and import paths updated from lib-commons/v2/... and lib-commons/v4/... to lib-commons/v5/....
- Header notices added to preserve historical bodies of dev-systemplane-migration (v5 systemplane rewrite flagged), .archive/migrate-v4 (completed v2/v3 to v4 migration), and docs/plans/2026-04-14-caching-cqrs-standards (archived plan).
- OpenCode Version Gate: removed false claim that cassert, cruntime, csafe, cbackoff, and coutbox were introduced in v5 (they are v4); callout now lists v2/v3/v4 as legacy below the v5 standard.
X-Lerian-Ref: 0x1
Generated-by: Claude
AI-Model: claude-opus-4-7
The `claude-md-reminder.sh` hook, which triggered on `UserPromptSubmit`,
is removed to simplify the system and reduce token overhead.
The hook was designed to combat context drift by periodically
re-injecting core instruction files like `CLAUDE.md` into the prompt.
This strategy proved to be too costly in terms of tokens and added
unnecessary noise to the context.
Removing this hook simplifies the developer workflow. For example, the
process for updating the code reviewer pool is now a simpler seven-step
process instead of eight.
All related configuration in `hooks.json` and documentation in
`ARCHITECTURE.md` and `CLAUDE.md` are updated to reflect this removal.
Propagates the 10-reviewer peer list across agent frontmatter, Position/Critical prose, shared-patterns, skill dispatchers, gate validators, and docs — resolving drift left behind when multi-tenant-reviewer and lib-commons-reviewer were added to the pool. Also fixes broken shared-pattern paths in lib-commons-reviewer and adds substantive blocker criteria to multi-tenant-reviewer plus codebase-context severity heuristic (Lerian third-rail vs external recommendation) to lib-commons-reviewer.
X-Lerian-Ref: 0x1
Adds Rule #8 documenting the mandatory propagation path when adding or removing reviewers in the ring:codereview pool. Born from the 2026-04-18 dogfood where adding performance-reviewer left 7+ files stale, and adding multi-tenant + lib-commons cascaded into ~65 stale references across 22 files.
X-Lerian-Ref: 0x1
Increases the number of parallel reviewers from 8 to 10 for both the
frontend and backend development workflows.
This change introduces two new specialized reviewer roles:
- `multi-tenant-reviewer`
- `lib-commons-reviewer`
The "Post-cycle: Multi-Tenant" step is removed from the backend
workflow. This integrates the multi-tenancy check directly into the
main review process, ensuring it is considered from the beginning
rather than as a final adaptation step. This shift-left approach aims
to catch architectural issues earlier in the development cycle.
docs: align all documentation with the new 10-reviewer workflow
docs(lib-commons): update skill to reflect major v5.0.2 release
chore(hooks): tune context reminder hook to reduce token consumption
CLAUDE.md mandates anti-rationalization tables for files read by agents as authoritative references. gate-cadence-classification.md is high-risk for rationalization because AI under time pressure tends to reason 'running a task-cadence gate per subtask is safer — more runs'. The new table defends against four common drifts: per-subtask inflation of task-cadence gates, shifting cycle-cadence work to task end, bypassing cadence for single-subtask tasks, and using cycle brevity as an excuse to skip classification.
X-Lerian-Ref: 0x1
The skill was marked deprecated in frontmatter but three live vectors still advertised or referenced it: dev-verify-code listed it in complementary, dev-implementation cited 'merged from deprecated ring:dev-delivery-verification' in its description and cross-linked to the deprecated path for a checklist, and the deprecated skill's own body still described itself as running as live Gate 0.5 between Gate 0 and Gate 1.
Removes the complementary entry, rewrites dev-implementation's description to describe current behavior without edit history, retargets the checklist cross-reference to the inlined Step 7 and Gate 0.5G locations, and replaces the Integration-with-dev-cycle section body in dev-delivery-verification with a deprecation banner pointing to the live equivalents. The file itself is preserved as a historical reference per the original deprecation decision.
X-Lerian-Ref: 0x1
Adds explicit subtask-failure propagation to Execution Loop Structure: any terminal failure at Gate 0, 3, or 9 sets task status to failed, blocks task-cadence gate dispatch, halts remaining subtasks, and pauses the cycle at a user checkpoint. Previously this behavior was implicit in the state machine and could be silently violated by an orchestrator that advanced past a failed subtask.
Retargets the multi-tenant cross-reference from the deprecated ring:dev-delivery-verification Step 3.5G to the inlined Gate 0.5G in dev-cycle. Removes ring:dev-delivery-verification from the complementary skill list. Replaces the dead 'success_pattern: [0-5]|0.5' regex branch with '[0-9]' now that gates go 0 through 9.
Strips meta-narration from three live skills: plan-document citations (See plan Section X.Y, R3/R4/R5B markers), the prancy-bentley anchor in dev-cycle-frontend, 'as previously documented' phrases, and 'REMOVED in R4 / New (R4)' edit-history markers in dev-report. Skills describe current behavior only — plan-document references belong in the plan, not the live protocol.
X-Lerian-Ref: 0x1
The cache-first feature injected <standards> blocks into 5 reviewer dispatch prompts, but only performance-reviewer parsed them — code, business-logic, security, and test reviewers ignored the injection and re-fetched standards on every run. The orchestrator-side half shipped without the consumer-side half.
Each of the 4 default reviewer agents now has a Standards Loading (Cache-First) section implementing the canonical three-tier resolution: cache hit from state.cached_standards, cache miss via WebFetch with warning, standalone fallback to hardcoded URLs. The per-reviewer fallback URL lists are unique and derived from each reviewer's standards_slice.
The 5-way verbatim duplication of the dispatch block in codereview/SKILL.md is collapsed to per-reviewer URL-slice markers that reference shared-patterns/standards-cache-protocol.md as the single source of truth. The shared pattern now carries the canonical <standards> template, orchestrator pseudocode, three-tier protocol, rolling-standards policy, and an anti-rationalization table defending cache-first behavior. Net 117-line reduction in codereview/SKILL.md.
X-Lerian-Ref: 0x1
validate_gate_0 and validate_gate_3 previously read tdd_red/tdd_green/unit_testing from tasks[i].gate_progress.*, but the state schema places these under tasks[i].subtasks[j].gate_progress.*. Any task with subtasks was silently blocked past Gate 0 because the hook resolved an empty task-level object to 'pending'.
Both validators now iterate subtasks, exempt subtasks that have not yet reached the gate (current_gate below target), and fall back to task-level reads when subtask_count is zero. LAST_COMPLETED_GATE derivation is recomputed from the per-subtask aggregation so recovery messages accurately reflect progress. Frontend-cycle safety short-circuits the validator as a no-op when implementation scope is absent everywhere.
X-Lerian-Ref: 0x1
Gate 0.5D was orphaned when v1.56.0 merged the general delivery-verification checks into ring:dev-implementation Step 7 without bringing migration safety along. Restored as a standalone conditional gate at dev-cycle Step 12.0.5b, parallel to Gate 0.5G (multi-tenant dual-mode verification). Runs post-cycle when SQL migration files appear in the cycle diff; skipped otherwise. BLOCKING findings hard-block Final Commit; ACKNOWLEDGE findings require explicit user confirmation; WARN findings log and continue.
Introduces -- ACKNOWLEDGE: <rationale> inline SQL comment convention for intentional breaking migrations (expand-contract contract phase, ALTER TYPE on large tables). Adds state.gate_progress.migration_safety_verification (additive). Updates migration-safety.md and migration-safety-checks.md to point at the new home instead of the deprecated ring:dev-delivery-verification skill.
X-Lerian-Ref: 0x1
Orchestrator resolves standards content from state.cached_standards at dispatch time and injects <standards> block with per-reviewer URL slices into code-reviewer, business-logic-reviewer, security-reviewer, test-reviewer, performance-reviewer. Each <standard> carries its URL + <content>; reviewer reads content if present, WebFetches URL if content empty. Preserves rolling-standards architecture — URLs still point to main branch, WebFetch remains the source of truth for standalone dispatch and cache misses.
Expands standards coverage to business-logic-reviewer (domain + domain-modeling + api-patterns) and test-reviewer (quality + testing-*.md) which previously received none — explicit rules beat implicit. performance-reviewer agent neutralizes its hardcoded <fetch_required> block in favor of three-tier resolution (injected block → per-standard WebFetch → standalone fallback URL list). dev-cycle Step 1.5 pre-cache extended with golang/architecture.md and golang/domain-modeling.md so all reviewer slice URLs are cacheable.
X-Lerian-Ref: 0x1
Cross-reference audit after v1.56.0 found stale references to the removed Gate 0.5 dispatch. Critical: validate-gate-progression.sh was reading .delivery_verification.status from TASK level (no longer populated), firing false errors on every real cycle. Now reads subtask-level .gate_progress.implementation.delivery_verified. dev-cycle/SKILL.md self-description (frontmatter, overview, cannot-skip block) updated from "11 gates (0→0.5→1→...→9)" to the three-cadence model. using-dev-team marks ring:dev-delivery-verification DEPRECATED. dev-refactor-frontend artifact description swaps "1:1 mapped" for clustering.
Public docs (CLAUDE.md, README.md, WORKFLOWS.md) updated to describe subtask/task/cycle cadence instead of old per-unit linear flow. file-size-enforcement.md dispatch point corrected from Gate 0.5 to Gate 0 exit criteria (ring:dev-implementation Step 7).
Stripped meta-narration markers ("since R4", "formerly Gate 0.5", "since Prancy Bentley speedup", "absorbed from former...") from skill bodies. Skills describe current behavior; edit history lives in CHANGELOG and git log, not in agent context.
X-Lerian-Ref: 0x1
Authoritative implementation plan for reclassifying gate cadence in dev-cycle and dev-refactor. Target: ~40-50% wall-clock reduction without reducing reviewer count, coverage thresholds, or quality gates.
X-Lerian-Ref: 0x1
Fix S3 upload double-extension by using basename of source path. Add collection prefix to index name derivation in Step 3 cross-reference. Clarify idx_*/uniq_* convention semantics based on real S3 data. Fix SKILL.md filename pattern to match reference spec.
X-Lerian-Ref: 0x1
Moved out of the Multi-Tenant Standard to be referenced inside Ring Agents and Skills. Updated canonical env var count from 14 to 13 across table, .env example, Config struct, checklist, canonical file map, summary, and M2M plugin section.
X-Lerian-Ref: 0x1
