docs(knowledge): repopulate the doc queue with the adopted enqueue roster - #1895
Conversation
…ting-5 dispositions Ten pages queued and five deferred-with-trigger records added to the Anthropic publisher profile, each carrying the reason it is where it is. thinking-troubleshooting is queued first on a corrected rationale: the check it backs is falsified, not weak — the harness carries a parallel troubleshooting surface, so the page's transfer is demonstrated rather than conjectured. Companion-doc order amended so memory digests second, on measured corpus citation load plus its now-live routing destination. The Agent SDK entry states its one-page boundary rather than leaving the thirty-page doc set to inference. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…t the what's-new deferral The previous commit's CHANGELOG asserted "ten pages queued and five deferred-with-trigger records added". Recounted at the bytes, one bullet per page: 11 queued across six groups, and 5 pages newly deferred — the deferred section holds six bullets because task-budgets predates this batch. The entry now states the counting rule alongside the figures. The previous commit message carries the superseded "ten pages" figure and is left as pushed. The two what's-new pages shared one bullet, a shape no incumbent entry uses. They are now one page per bullet, each stating its own trigger, which is also what makes the count unambiguous. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds the retention and ZDR group after the thinking group: the platform api-and-data-retention page as the API lane, plus data-usage and zero-data-retention as the harness lane. Both properties were already in scope, so the slice costs one fetch. A veto-flagged adopted row proceeds, with the veto standing as an owner surface rather than a gate needing a ratifying event, and a queue entry is trivially reversible if it fires. The CHANGELOG records the enqueue and keeps the veto disclosure. Counted at the bytes after the addition: 14 pages queued across seven groups, 5 newly deferred with triggers across a six-bullet deferred section. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ose the engineering entry's discharged contingency Verifier findings: the deferred-with-trigger block sat between queued groups, so a top-down scan reading it as the queue's end would miss the three queued pages below it — it now sits last before Artifact targets; and the engineering-post entry's veto contingency (discharged when the property edit merged in 0.10.18) is now disclosed in the CHANGELOG the way the retention slice's standing veto already was. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 2m 12s —— View job Review: PR #1895 — repopulate doc queue with adopted enqueue roster
Verdict: no blocking issues found. This is a well-scoped, internally consistent docs change. What I checked
Alignment with
|
|
Claude finished @kyle-sexton's task in 1m 7s —— View job Security review complete
No security issues found. This PR is a pure documentation/content change to the
None of the categories in scope for this review apply: no GitHub Actions workflow files are touched, no code execution paths, no secret/token/credential handling, no authorization or access-control logic, and no injection surfaces (command, SQL, path, template). This is a content-only update to a markdown context file consumed by a documentation-digest skill; it introduces no new trust boundary. |
|
Claude has reviewed this PR 3 times. The lane skips further automatic reviews after 5; deleting this comment resets the count. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6395841eb3
ℹ️ 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".
… in the queue Two review findings. The thinking-troubleshooting rationale read as counterpart-surface reasoning — the near-miss class the profile's own falsifying rule rejects; it now cites the claim-specific harness assertions (thinking-configuration 400s on errors.md, cache-miss causes on prompt-caching.md) and states that the digest still tags each claim individually. The retention group promised one fetch for three URLs, contradicting the engine's one-page-per-run rule; heading and CHANGELOG now say three page runs, one topic slice. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 1m 12s —— View job Review: PR #1895 — code-review lane
Verdict: no blocking issues. Both Codex P1 findings were already resolved by the latest commit on this branch ( Codex findings — status
Consistency checks
Scope noteThis is a docs/content-only change (a skill's context file used as a planning queue, plus its plugin manifest version and changelog) — no code, no tests, no architecture surface applicable to this lane's usual checks. Per |
|
Claude finished @kyle-sexton's task in 1m 7s —— View job Security review complete (re-run for
|
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 1m 18s —— View job Review: PR #1895 — code-review lane
Verdict: no blocking issues. Both Codex P1 findings are resolved as of the current HEAD ( Codex P1 findings — verified fixed
Consistency checks performed
Scope noteThis is a docs/content-only change to a skill's context file (a doc-fetch planning queue) plus its plugin manifest version and changelog — no code, no tests, no architecture surface. Per |
|
Claude finished @kyle-sexton's task in 1m 2s —— View job Security review complete (re-run for
|
…s, residual-risk footer (#1898) ## Summary DOC bundle 4 of the doc-corpus application campaign — the three unblocked rows (playbooks 0.6.6 → 0.6.7; knowledge 0.10.19 → 0.10.20): - **Point at a per-model matrix; never copy one** (`fable-5/context/calibration.md` + one SKILL.md line): a third source-grading axis (volatility) beside the surface and channel axes — point at the vendor page that owns a per-model table; a stated matrix carries a re-check trigger naming the next model release; table presence is not reachability where you run. Worked instance corrected at the bytes: Claude Mythos 5 is a known registry model with full gating machinery and still not selectable — exactly one non-null provider id beside **seven** null siblings (the earlier "all eight null" figure was schema-disproven; the correction and its reason are in the CHANGELOG). - **Archive-reading conventions** (knowledge profile): a dated entry is not a content-change signal (two byte-identical entries five days apart prove it); absence of bold does not prove absence of change — deltas come from diffing entries, never reading markup; note a source artifact at the row, never silently repair it (with the one reader-facing exception stated). Recheck against the UNC-1 ruling confirmed no premise moved — the ruling touched tags, these are page properties. - **Residual-risk footer** (knowledge profile): the reduce-hallucinations page's own hedge, quoted verbatim (byte-compared live), scope unbroadened — hallucinations only, no validator named — with the cite-never-restate rider for graduated chapters. Fourth commit removes a cross-plugin dependency claim and an internal-record pointer from the knowledge CHANGELOG (self-caught; disclosed). Independently verified (fresh-context, rationale withheld): SHIP, zero findings — EC-3 seven-count, UNC-1 no-retag ruling, byte-identical-entries evidence, and the footer byte-compare all re-derived by the verifier. No linked issue ## Related - #1885, #1887, #1893 — DOC bundles 1-3 (same campaign, same delivery shape) - #1895 — the doc-queue repopulation this bundle's knowledge bump follows (0.10.19 → 0.10.20) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011UarawwEnZQu7cB6i7WatJ --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Summary
Repopulates the docpage-digest Anthropic profile's doc queue with the doc-corpus campaign's adopted enqueue roster (knowledge 0.10.18 → 0.10.19):
Independently verified (fresh-context, rationale withheld): SHIP, with the two findings (deferred-block position; contingency disclosure) applied in
6395841eb3and confirmed CLOSED. All 14 queued URLs return HTTP 200 live; queue counts recounted at the bytes by producer and verifier independently.No linked issue
Related
🤖 Generated with Claude Code
https://claude.ai/code/session_011UarawwEnZQu7cB6i7WatJ