# v1.5.0 candidate checkpoint

This record binds the candidate to the exact fifteen-skill portfolio, the
public-surface coherence gate and refreshed README/flow artifacts. It is not a
publication record.

```text
VERSION: 1.5.0
STATUS: RELEASE_CANDIDATE
VERIFIED_DATE: 2026-09-02
SKILL_COUNT: 15
PORTFOLIO: EXACT_FIFTEEN_CANONICAL_NOBRAINER_SKILLS
COHERENCE_GATE: PASS
README_COHERENCE_READBACK: PASS
MERMAID_FLOW_READBACK: PASS
SVG_FLOW_READBACK: PASS
V1.4_PUBLICATION_GAP_RECORDED: PASS
DETERMINISTIC_TESTS_TOTAL: 109
DETERMINISTIC_TESTS_STATUS: PASS
PUBLIC_SYNC: FETCH_ONLY
AUTOMATED_PUBLIC_COMMIT_PUSH: BLOCKED
MERGE: NOT_PERFORMED
TAG: NOT_CREATED
DISTRIBUTION: NOT_PUBLISHED
ACCEPTANCE: PASS_LOCAL_PR_CANDIDATE
```

## What changed

- `nobrainer-ultra` now makes a public-surface decision part of every scope:
  update affected README, docs, templates, assets and flow, or record
  `PUBLIC_SURFACE: NOT_NEEDED` with a reason. Public contract, routing and
  workflow changes use the full lifecycle and require fresh SVG and README
  Mermaid readback.
- `nobrainer-writing` now uses `ENV:` for bug/comment context, omits speculative
  bug workaround/root-cause fields and keeps feature issues to the essential
  Description, affected user, desired outcome and evidence fields.
- The quick path is limited to edits with no public contract, routing, workflow
  or portfolio impact; scope expansion escalates to the full lifecycle.
- Root workflow instructions, the routing reference, `CONTRIBUTING.md` and the
  pull-request template carry the same rule.
- README's Mermaid flow and `assets/nobrainer-workflow.svg` show the quick path
  and the public-surface coherence gate.
- The v1.4.0 publication gap is recorded in
  [`v1.4.0-publication-readback.md`](v1.4.0-publication-readback.md) instead of
  being silently rewritten.

The candidate keeps exactly fifteen skills. It also carries the portable
`STANDARD`/`EXTENDED`/`ROUTED` model policy: model, effort, budget and escalation
are explicit, and unsupported routing stays unverified rather than falling back
silently. README and compatibility docs position the candidate as an Astra Ready
Flow for current Codex and Claude Fable 5.1 / Mythos 5.1 workflows without
claiming direct provider runtime support. No automated public commit, push,
PR, merge, tag or publication is part of the repository's scheduled jobs.