Repository navigation
docs(llmdoc): sync dogfood knowledge to the unified prompt contract - #41
Merged
Merged
Conversation
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
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
Follow-up to #40, running the update workflow it left for post-merge.
deltareported 5 impacted docs inlightmode with a clean worktree;recordersynced them to the current HEAD facts:architecture.mdx— the Retrieval Gate now covers both agent contracts (including investigator's native-tools handover boundary); thenpx -yexternal-tooling semantics now span every prompt surface, declared once per surface, with barenpxand--no-installcalled out as forbidden forms.plugin-packaging/claude-and-codex.mdx— the cross-host gate-consistency contract now includesagents/*.mdand.codex/agents/*.toml; recorded the current Codex-surface state: hand-synced replacement-style (bodies byte-identical, TOMLs parse), pending an acplugin ≥1.6.1 regeneration (older versions regressmodel: inheritand downgrade hooks);npx --no-installcleared from generated surfaces.plugin-packaging/development-and-release.mdx— corrected a stale fact: release.yml gates five version surfaces (cli/package.json, root package.json, .claude-plugin/plugin.json, marketplace.jsonplugins[].version, .codex-plugin/plugin.json), not three.workflows/init-and-update.mdx— new section on the recorder/workflow finalization split: recorder validates and repairs, the calling workflow runs the one-shotcommit, andfingerprint --updateonly on explicit request.workflows/prune-and-upgrade.mdx— tightened the two-phase wording (CLI reports, recorder rewrites, workflow commits); recorded upgrade's fixed finalizer order (init-statewhen no ledger survives →validate→commit --all, order not reversible).Finalized with
llmdoc commit --all: docs commit + meta follow-up commit, all 7 fingerprints refreshed, baseline advanced. No volatile facts written (no version numbers, counts, or line totals).Validation
npx -y @tokenroll/llmdoc validate— ok (gated insidecommit)statusafter commit — 0 impacted / 0 needs-review / 0 dirtyNote
statusreports growth above the gate (~3336 tokens vs the ~2003 convergence baseline). Per the update contract this run does not touch convergence state; whether to run/llmdoc:pruneis a separate decision.