docs(log): session 2026-07-03

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: gtrabanco

docs/LOGS.md

@@ -37,3 +37,10 @@ tidy past entries — they're a record.
 - **Summary:** Added the ship-roadmap demo video to both READMEs (then repositioned it above the title, centered, per feedback), then did two rounds of workflow hardening: (1) every user-facing skill now carries a `## Portability` section with generic fallbacks for agents/models without Claude Code's slash menu, per-skill model/effort, or `/loop`; (2) a much stricter pass — a brand-new 9-skill internal review pack (`review-code/-security/-verify/-debt/-design/-a11y/-brand/-perf/-seo`) so the workflow never depends on Claude-bundled or external review skills, heuristics converted to checklists and fixed "Return exactly" output contracts across the core skills, a Git-workflow convention (branches default vs worktrees) the user declares, and a Claude-tier → generic-capability-class model-equivalence table so the skills work on any model. A follow-up audit for leftover ambiguous phrasing found and fixed 5 remaining vague spots plus 3 internal planning skills missing a fixed completion-report contract.
 - **Decisions:** External review skills (code-review, security-review, design-review, etc.) demoted from implicit dependencies to optional extras — the internal `review-*` pack is now the only thing `review-change`/`product-audit` require, so the workflow works identically on any agent with zero external skills installed. Git workflow default is `branches` (one active unit, no worktrees) per the user's own preference, not `worktrees`, even though worktrees would parallelize faster — correctness/simplicity over speed for a single-operator repo. Model-equivalence table keeps Claude tiers as the *declared default* (Anthropic sets the reference bar) rather than trying to be neutral — explicit choice per the user.
 - **Next:** Validate the new formats for real — run `/plan-feature` + `/execute-phase` on a target repo (e.g. ship-lab) and confirm the fixed output blocks (`Return exactly`, checklists, PASS|FAIL) print exactly as specified, ideally once on Claude and once on a non-Claude model to check the model-agnostic claim. Optionally extend the same checklist/ambiguity audit to `docs/workflow/*.md` (out of scope this session — skills only).
+
+## 2026-07-03T22:06:01Z — main — manual
+- **Commits:** 17 (`ff437c5…6b670c0`)
+- **Files:** README.md, README.es.md, CHANGELOG.md, CHANGELOG.es.md, template/CLAUDE.md, docs/assets/nan-cloud.svg, docs/assets/nan-model-routing-cheatsheet.pdf, `.github/workflows/sync-inheritance.yml`, `skills/{execute-phase,plan-feature,plan-fix,ship-roadmap,triage-issue,audit-docs,audit-pr,product-audit,review-change,init-workspace,log-session,plan-feature-scaffold,bump-skill}/SKILL.md` (22 files, +942/-55 total)
+- **Summary:** Real-world field testing of the workflow on Hermes Agent (open-weight models via NaN.builders) surfaced several gaps this session closed: an `#inheritance` skill variant (auto-synced branch, `model:`/`effort:` stripped) so any agent inherits its own session model; a full NaN.builders model-routing section in both READMEs (concrete picks per skill, fallback ladder, a downloadable PDF cheat sheet) after the user pushed back that the first pass wasn't concrete enough; Hermes-specific install/invocation docs (global installs per agent, `hermes bundles create` since Hermes only slash-routes bundles, not bare skills); a hard dependency gate in `execute-phase` (transitive `Depends on:` closure must be merged, `--force` escape hatch) plus fix-first priority in `ship-roadmap`'s SELECT and a plan-time blocker check in `plan-feature`; then, after the user reported Hermes-driven runs skipping commits/PRs/branch discipline, a `## Turn contract` section added to the top of every user-facing skill (weak models drop end-of-document duties) with an artifact-language precedence rule (explicit instruction > project's declared docs language > English — conversation language never decides) and an explicit PR close-out contract (print the PR URL in chat, link the roadmap/fix-index row as `done · [#pr](url)`); finally, made the *detector* skills (`audit-docs`, `product-audit`, `review-change`, `audit-pr`) mechanically verify all of the above actually held, rather than assuming a frontier model's compliance.
+- **Decisions:** Model-equivalence picks for NaN.builders are dated (July 2026) with an explicit re-check warning — model names churn in months, the precedence rules don't. `#inheritance` strips `model:`/`effort:` entirely instead of setting `model: inherit` — cleaner for agents with no such concept at all, and auto-synced via GitHub Action on every push to `main` so it never goes stale. Turn contracts go at the top of each skill (not the bottom) specifically because weak models truncate/skim toward the end of a long document — this is the single highest-leverage fix from this session. PR close-out requires printing the URL in chat because "not every agent shows open PRs" (Hermes doesn't); a roadmap row of bare `done` is now treated as an unfinished unit, not a cosmetic gap. Detector skills got explicit, mechanical (grep/git log, not inference) checks for every hardening rule instead of trusting a model to notice drift — this is what actually makes the workflow self-healing across model strength.
+- **Next:** Run `/product-audit` (or `/audit-docs --fix`) against the sosfelinos project now that Hermes has the refreshed `#inheritance` skills, to reconcile the bare-`done` roadmap rows Hermes left and confirm the new checks 1-13 actually fire. Then do a live A/B: same feature, once via Claude Code and once via Hermes/NaN, to verify parity on branch discipline, commit/PR creation, and the PR-link close-out. Consider whether `bump-skill` should also auto-tag releases (`release-YYYY-MM-DD`) — it was done manually twice this session.