chore(knowledge): retire choosing-a-model doc-queue entry after digest-half completion - #1788
Merged
Merged
Conversation
…t-half completion Removes the choosing-a-model entry (and its emptied "Model selection" special-handling category) from the docpage-digest Anthropic profile's doc queue - the digest slice completed end-to-end (raw-md fetch through interview handoff, dual verification with two correction rounds, re-verified REVERIFY2: PASS by both verifiers), closing the entry's second half; its routing-vet half was already executed 2026-07-29 (#1697). The paired models-explained blog entry now points at the completed slice's handoff for its pairing observations. Bumps the knowledge plugin 0.10.7 -> 0.10.8 with a matching CHANGELOG entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 1m 22s —— View job PR Review — #1788
SummaryStraightforward maintenance PR retiring a completed doc-queue entry. All three changes are internally consistent and follow established conventions. Two minor observations below. Findings1. Unqualified issue reference in CHANGELOG.md
executed 2026-07-29 (#1697)The same routing-vet reference is fully-qualified in the profile file at line 93 ( 2. Machine-local work-root slug in the blog annotation
— pair with the completed choosing-a-model slice (work-root slug
`platform-claude-com-docs-en-abo-38ebff0f` on the machine that ran it)The "on the machine that ran it" qualification correctly flags this as non-portable. This is informational context, not a functional reference, so it won't break anything. Just worth noting that anyone picking up this queue entry on a different machine will need to locate the handoff through the linked PR/issue rather than this slug. The PR body names this as another pre-commit advisory — the wording applied seems intentional given the explicit qualification. What looks good
The CHANGELOG reference is the only actionable item. Everything else is clean. |
|
Claude finished @kyle-sexton's task in 1m 2s —— View job Security Review — PR #1788
ScopeThree files changed in this PR:
FindingsNo security issues found. All three changes are pure documentation/metadata. Checked for:
The PR is clean from a security perspective. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 984ead0404
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…ue entry The models-explained blog entry pointed at the choosing-a-model slice's interview handoff for the pairing package — a machine-local, memory-tier work root that does not exist in other clones. The seven-item cross-link contract now rides the queue entry itself (compressed but complete), so the blog run is executable from any clone; the fuller original remains available where the slice exists. Addresses the Codex P2 review thread on this PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 1m 23s —— View job PR Review — #1788
SummaryRoutine maintenance PR retiring a completed doc-queue entry. All three files are internally consistent and well-structured. One actionable finding: a bare issue reference in the CHANGELOG that should be fully qualified. Everything else is clean. Findings1. Unqualified issue reference in CHANGELOG.md — line 15 executed 2026-07-29 (#1697). The emptied "Model selection"…The CHANGELOG ships with the plugin. A consumer reading it outside Fix: Replace
What looks good
Codex review note (P2 — pairing package portability): The inlined (a)–(g) checklist in the profile's blog annotation IS the portable package Codex was asking for. The machine-local slug is a bonus pointer to the fuller original, explicitly qualified as such. No further action needed on that point. |
|
Claude finished @kyle-sexton's task in 50s —— View job Security Review — PR #1788
ScopeThree files changed:
FindingsNo security issues found. All three changes are pure documentation and metadata. Checked against the target attack surfaces:
The PR is clean from a security perspective. |
kyle-sexton
added a commit
that referenced
this pull request
Jul 30, 2026
…slice completion (#1816) ## Summary The claude-models-explained blog slice completed the full docpage-digest pipeline: rendered-channel fetch (raw-md confirmed absent per the profile's blog-post channel note) with firecrawl extraction, 7-unit digest fan-out executing the run-7 pairing cross-link contract (a)–(g), dual verification (Verifier A fable-5 + cross-vendor Codex per the #1740 recipe, two correction rounds, final REVERIFY2: PASS from both, no degraded fallback), and interview handoff (pairing results + 8 CAs + 8 OQs, all 32 digest questions mapped). Profile changes: - Models-explained blog queue entry removed per the remove-on-completion rule, taking its inlined seven-item pairing contract with it (executed; results recorded in the slice's handoff). - Vendor-blog attestation rule codified: assertion-specific `vendor-claimed (blog, <fetch date> fetch)` markers, illustrative assertion-class list — the rule the context-engineering slice's handoff recommended (its OQ-3), enforced end-to-end by both verifiers on this slice. Knowledge plugin 0.10.8 → 0.10.9 with changelog. No linked issue ## Related - #1788 — run 7 (choosing-a-model digest), whose OQ-10 pairing contract this slice executed - #1775 / #1779 — the guardrail-lane queue PRs preceding this run - #1740 — the elevated Codex Verifier B recipe used for cross-vendor verification Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
kyle-sexton
added a commit
that referenced
this pull request
Jul 31, 2026
…ry (#1868) ## Summary The thinking-steering-and-cost platform doc slice completed, so its entry leaves the `docpage-digest` Anthropic profile's doc queue per the queue's remove-on-completion rule. The now-empty "Thinking" category heading goes with it — that category held two overlapping docs digested one page per run under its own contract, and the run-9 entry's PR (#1842) removed the first while anticipating this removal taking the heading. Knowledge bumps 0.10.10 → 0.10.11 so consumers receive the queue change. ## Verification Dual verification reached PASS on both arms against **identical frozen bytes** — a SHA-256 pin of all nine slice files, with the tree quiesced before either arm audited, per the frozen-tree rule this campaign adopted after a concurrent-correction race produced a spurious MAJOR. - **Arm B (cross-vendor, Codex)** — `VERDICT: PASS`, `FINDINGS: none`, six checks PASS, three round-1 findings RESOLVED. - **Arm A (same-vendor, fresh context, rationale withheld)** — `REVERIFY2: PASS`, six checks PASS, five prior findings RESOLVED, three MINORs, all record-keeping and none touching fidelity. Fidelity was swept mechanically: all 108 quoted spans across the six digests are exact substrings of the single source line each cites, 0 misses. Tag census 41 `cc-applicable` / 28 `mixed` / 12 `api-only` = 81 rows, exactly one vocabulary tag per row. The three MINORs were remediated after the verdicts without altering any claim row: two stale self-check footer records got dated "historical as of" annotations, and the missing round-2/3 applied record was written. The slice's `interview-handoff.md` was independently re-validated against the corrected digest bytes by a separate agent and its five stale items corrected. No degraded fallback was used at any point. Three findings from this run carry to the batched dispositions interview rather than this PR: the absence of any cross-digest citation-consistency check in the verification contract, the absence of a required applied-record artifact per correction round, and a genuine unharmonized cross-source tension about where a resolved effort value physically lives. ## Related - Follows #1842 (run 9, the paired thinking doc), which removed the first entry of this category. - Same campaign as #1816, #1788, #1779, #1775, #1765, #1761, #1756, #1752. No linked issue. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
kyle-sexton
added a commit
that referenced
this pull request
Aug 1, 2026
…ge-digest queue (#1874) The `platform.claude.com/docs/en/release-notes/system-prompts` slice completed. It is the **last entry in the doc queue** — after this merges, the queue section holds only the deferred task-budgets trigger entry, which was never queued. ## What ran The largest slice this pipeline has processed: **18 digests over a 2,548-line source, 659 claim rows, 561 `api-only`.** - Seven correction rounds and five dual-verification rounds, each on SHA-256-pinned bytes with the frozen-tree rule enforced — both arms re-hash before *and* after auditing, and no correction runs while a verifier holds the tree. - Final state: both arms `VERDICT: PASS`, with a confirming round after the last corrections. - Final gates: **1,895 recorded command/count pairs replay with 0 mismatches**, 0 `<corpus>` placeholders, 659/659 rows parse with `N. Quote (line` count equal to `- Tag:` count in all 18 digests, every stated tally equal to its anchored `grep -c`, `check-quotes.py` clean. ## What the run found worth carrying forward - **Narrow-slug false absences** remained the dominant defect — a basis testing one literal while the corpus documents the same concept in other words. Rows now disclose near-misses by name and line, each produced by a command recorded in that row. - **Prose is unparsed by every gate.** Summary paragraphs, Implications bullets and Open questions carried stale counts and false statements across several rounds; two sweeps (one whitespace-normalized with an offset map back to physical lines) closed the class. - **A contested tag-ordering question is escalated, not decided** — whether selecting a positive tag requires first establishing harness applicability. It is written up as a candidate profile amendment with both readings, the evidence, and a recommendation, for the dispositions interview. Residual MINOR findings are disclosed in the slice's `interview-handoff.md` as Open questions, per the run's stopping rule. ## What this PR changes - Removes the system-prompts entry and the now-empty "Supplementary references" heading from the profile's Doc queue. - Bumps the `knowledge` plugin `0.10.13` → `0.10.14`. - Adds the matching CHANGELOG entry. No linked issue ## Related - Third and final of the serialized run-11 queue PRs, after #1872 (resources overview) and #1873 (verification-loops blog). All three touch the same profile file, so they merged one at a time. - Completes the queue drain begun in #1752 and continued through #1756, #1761, #1765, #1775, #1779, #1788, #1816, #1842 and #1868. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docpage-digestAnthropic profile's doc queue — its digest slice completed end-to-end (fetch through interview handoff) per the queue's remove-on-completion rule, closing the entry's second half. The routing-vet half was already executed 2026-07-29 (chore: effort judgment recalibration (choosing-a-model routing vet) #1697, PR chore: effort judgment recalibration (choosing-a-model routing vet) #1725) and was NOT redone; the slice checklist records that scope explicitly. The emptied "Model selection" special-handling category goes with the entry..mdappended; HTTP 200, 112 lines / 7,568 bytes — channel re-verified for this page, no degradation)..work/platform-claude-com-docs-en-abo-38ebff0f/verification/.0.10.7→0.10.8with matching CHANGELOG entry.Verification
markdownlint-cli2on changed markdown: 0 errorscheck-skill.sh docpage-digest(CHECK_SKILL_SKILLS_ROOT=plugins/knowledge/skills, baseorigin/main): PASS (1 pre-existing soft warning, SKILL.md length)check-changelog-parity.sh --check-bump origin/main: PASSNo linked issue — this PR closes no GitHub issue; the doc queue is tracked in the profile file itself.
Related
🤖 Generated with Claude Code