docs(playbooks): extend the orchestration snapshot note to pricing figures

[kyle-sexton]

No linked issue

Summary

The boris orchestration reference (plugins/playbooks/skills/boris/reference/orchestration.md) carries a header note classifying its benchmark figures (Sections 78 and 94) as launch-day snapshots with a re-resolve trigger. Section 94/95's Fable 5 price literals ($10/M input, $50/M output, cache write $12.50, cache read $1, full 1M context at standard rate) and Sections 78/95's relative price claims ("same price as 4.7", "exactly 2x Opus 4.8") sat outside that classification, readable as current rates.

This extends the note to classify pricing figures (Sections 78, 94-95) the same way — launch-day rates, verified still current against the live pricing page on 2026-08-04 — and routes current-rate resolution upstream. No figures added or removed; the vendored upstream mirror is untouched.

Playbooks 0.6.18: serialized one patch above unmerged #1931's 0.6.17 claim per the one-in-flight-claim-per-plugin rule; whichever lands second rebases.

Related

• docs(playbooks): re-resolve fable-5 model adaptation on Opus fallback #1931 (playbooks 0.6.17 claim, row 240)
• Doc-alignment campaign save-point: Doc-alignment roster-tail campaign — durable save-point (2026-08-04 clean-stop) #1941

🤖 Generated with Claude Code

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude finished @kyle-sexton's task in 1m 52s —— View job

---

Code review — docs(playbooks): extend the orchestration snapshot note to pricing figures

• Gather context (diff, CLAUDE.md, REVIEW.md)
• Understand the request (code review of this PR)
• Review changed files for correctness & alignment
• Post findings

Scope note: per REVIEW.md, this lane owns correctness/design/docs and defers security findings to the dedicated security lane. This PR is a pure-docs change with no security surface, so that split doesn't come into play here.

Files reviewed: plugins/playbooks/.claude-plugin/plugin.json, plugins/playbooks/CHANGELOG.md, plugins/playbooks/skills/boris/reference/orchestration.md.

Findings

None. The change is small and internally consistent:

• The extended note (orchestration.md#L16-L19) correctly cites Sections 78, 94–95 as the pricing-bearing sections — I checked each: 78 has "Same price as 4.7," 94 has the Fable 5 price literals plus "exactly 2× Opus 4.8," and 95 restates "Cost — 2× Opus 4.8." No pricing content exists outside those three sections, so the classification is complete and not over- or under-scoped.
• No figures were added, removed, or altered — confirmed via the diff; only the header note grew. This matches the PR description.
• Per CLAUDE.md's fresh-docs mandate, a skill reference file's prose body is explicitly out of that mandate's scope (only frontmatter/manifest/contract surfaces are in), so this change wasn't required to WebFetch-verify against the live pricing page — but the PR did so anyway (2026-08-04) and the CHANGELOG records that basis, which is good practice for a note whose whole point is flagging staleness risk.
• CHANGELOG.md entry follows the existing format (bold lead sentence, ### Changed, similar line-wrap width) and accurately mirrors the code change — the "Section 94's Fable 5 price literals" / "Sections 78/95's relative price claims" split in the changelog is actually more precise than the PR body's own summary (which said "94/95" for literals), since the literals only live in Section 94.
• plugin.json version bump (0.6.16 → 0.6.18) matches the CHANGELOG's new [0.6.18] entry; the skipped 0.6.17 is explained in the PR body as intentional sequencing against an unmerged sibling PR, and doesn't create any inconsistency in this repo's current state.

Nothing else stood out — no error-handling, atomicity, or test-coverage concerns apply to this doc-only change.

[claude]

Claude finished @kyle-sexton's task in 30s —— View job

---

Security review complete

• Gather context (diff, CLAUDE.md, custom instructions)
• Review changed files for security issues
• Post findings

Scope: git diff origin/main...HEAD for this PR touches exactly the 3 files listed — plugins/playbooks/.claude-plugin/plugin.json (version bump 0.6.16 → 0.6.18), plugins/playbooks/CHANGELOG.md (changelog entry), and plugins/playbooks/skills/boris/reference/orchestration.md (4 lines added to an existing header note, extending its "launch-day snapshot" classification to pricing figures).

Findings: none. This is a pure prose/documentation edit:

• No code execution paths, no scripts, no hooks, no .mcp.json, no GitHub Actions workflow changes.
• No secrets, tokens, or credentials touched.
• No injection surfaces (command, SQL, path, template) — the diff only adds a markdown note and a link to the existing, already-referenced pricing page.
• No permission or trust-boundary changes — nothing here affects hook contracts, marketplace schema, or manifest fields beyond the semver bump.
• No supply-chain surface — no dependency or action pins are added or altered.

No security concerns to report on this PR.

[github-actions]

Claude has reviewed this PR 2 times. The lane skips further automatic reviews after 5; deleting this comment resets the count.

[claude]

Claude finished @kyle-sexton's task in 2m 24s —— View job

---

Code review — docs(playbooks): extend the orchestration snapshot note to pricing figures

• Gather context (diff, CLAUDE.md, REVIEW.md)
• Understand the request
• Review changed files for correctness & alignment
• Post findings

Scope note: per REVIEW.md, this lane owns correctness/design/docs and defers security findings to the dedicated security lane. This is a pure-docs change with no security surface, so that split doesn't come into play.

Files reviewed: plugins/playbooks/.claude-plugin/plugin.json, plugins/playbooks/CHANGELOG.md, plugins/playbooks/skills/boris/reference/orchestration.md (diff at 25afa2b).

Findings

Substance is correct; one cosmetic nit in the CHANGELOG.

• Versioning is clean. plugin.json now bumps 0.6.17 → 0.6.18, matching the new [0.6.18] entry. After the merge of origin/main (which already carries docs(playbooks): re-resolve fable-5 model adaptation on Opus fallback #1931's 0.6.17), there's no duplicate ## [0.6.17] header and no version gap — I checked, only one instance each of 0.6.16/0.6.17/0.6.18 in the changelog.
• The extended note is accurate and complete. orchestration.md#L16-L19 cites Sections 78, 94–95 as the pricing-bearing sections. I re-checked each: 78 has "Same price as 4.7," 94 has the Fable 5 price literals plus "exactly 2× Opus 4.8," 95 restates "Cost — 2× Opus 4.8." No pricing content lives outside those three sections, so the classification is neither over- nor under-scoped, and no figures were added, removed, or altered.
• Minor formatting nit — CHANGELOG.md#L11-L13: the hard-wrap breaks unusually early — (playbooks ends line 11, then line 12 is just 0.6.17 → 0.6.18). The (~23 chars) before line 13 resumes at full width with header note classified.... Every other entry in this file wraps the sentence continuously near the ~90–100 char width (e.g. the 0.6.17 entry two entries below: 0.6.16 → 0.6.17). The rule resolved the running model once, at arm time, and routed it to its). Purely cosmetic — doesn't affect rendered markdown — but worth a quick rewrap for consistency with the file's established convention. Fix this →
• Per CLAUDE.md's fresh-docs mandate, a skill reference file's prose body is out of that mandate's scope (only frontmatter/manifest/contract surfaces are in), so this change wasn't required to WebFetch-verify pricing against the live page — but the changelog records that the author did so anyway (2026-08-04), which is good practice for a note whose whole point is flagging staleness risk.

Nothing else stood out — no error-handling, atomicity, or test-coverage concerns apply to this doc-only change.

[claude]

Claude finished @kyle-sexton's task in 37s —— View job

---

Security review complete

• Gather context (PR diff, CLAUDE.md)
• Review changed files for security issues
• Post findings

Scope: git diff origin/main...HEAD for this PR touches exactly 3 files — plugins/playbooks/.claude-plugin/plugin.json (version bump 0.6.17 → 0.6.18), plugins/playbooks/CHANGELOG.md (new changelog entry), and plugins/playbooks/skills/boris/reference/orchestration.md (4 lines added to an existing header note, extending its "launch-day snapshot" classification to cover pricing figures in Sections 78, 94–95).

Findings: none. This is a pure prose/documentation edit with no security-relevant surface:

• No code execution paths — no scripts, hooks, .mcp.json, or GitHub Actions workflow files are touched.
• No pull_request_target/workflow_run usage, no run: blocks, no github context interpolation — nothing in scope is a workflow file at all.
• No secrets, tokens, or credentials referenced or handled.
• No injection surfaces (command, SQL, path, template) — the diff only adds markdown prose and a link to the pre-existing, already-referenced pricing page.
• No permission or trust-boundary changes — the plugin.json diff is solely the semver field; no permissions, config, or manifest contract fields beyond version are touched.
• No supply-chain surface — no dependency or action pins added, removed, or loosened.

Nothing for zizmor's advisory lane to defer either — there's no workflow, action-pin, or trigger content in this diff for it to have covered.

No security concerns to report on this PR.