release-candidatelisted

# Release Candidate Auditor Perform a structured go/no-go audit for a release. Every failure is logged, via the `radin-record` skill, as an entry in radin's `BACKLOG.md` with enough detail that a developer can act on it without re-running the audit. Never append to `BACKLOG.md` directly — `radin-record` is the only writer, so route every finding through it. --- ## Step 0: Baseline Resolve radin's per-project namespace and locate `BACKLOG_FILE` — the same shared resolution every radin skill/agent uses, never a repo-root file. This is read-only here; it's only used to count entries before/after, not to write: ```bash bash "$HOME/.claude/radin-lib/radin-namespace.sh" ``` Read `BACKLOG_FILE` from its output. Record the current entry count so you can detect net-new entries at the end: ```bash grep -c '^### ' "$BACKLOG_FILE" 2>/dev/null || echo "0" ``` Also identify the last release tag so you know which commits are "since last release": ```bash git describe --tags --abbrev=0 2>/dev/null || git log --oneline | tail -1 | awk '{print $1}' ``` --- ## Step 1: Build pipeline — format → lint → build Run in strict order. If any step fails, log it and stop that step (don't run lint if format fails with non-zero exit, etc.). Each step is a hard gate. ```bash make format 2>&1 make lint 2>&1 make build 2>&1 ``` For each failure, invoke `radin-record` with an item along these lines: > Log a fix: build pipeline failure in `make <step>`. Exit code <N>. Output: > <relevant tail