Repository navigation
[kb-docs] docs: document knowledge-base v1.3.1 - #10
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This branch has not been deployed
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.
Caution
Protected files were modified in this change.
This pull request is in
request-reviewmode and requires explicit human scrutiny before merge.Protected files:
.kb-sync/features.ymlAllow intentional protected-file changes
If this workflow is intended to modify these files, add specific filenames or folder prefixes to
safe-outputs.create-pull-request.protected-files.excludein the workflow Markdown frontmatter. For example, to allow.changeset/*, exclude the folder using.changeset/:Keep your existing policy and exclusions. Folder exclusions use path prefixes, not glob patterns, and allow all files beneath that folder, including subfolders. Other protected files still require review. If
allowed-filesis configured, these paths must also match it. Rungh aw compileafter updating the workflow.Mode and range
full— initial sync →v1.3.1(f95eb35b47051b66fb0154319780aefe4431ba17, 2026-11-06).Features
docs/index.md,docs/kb/how-it-works.mddocs/kb/onboarding.mddocs/kb/single-page.mddocs/kb/packaged.mddocs/kb/manifest.mddocs/kb/rules.mddocs/kb/actions.mddocs/kb/style-tokens.mddocs/kb/agent-skill.mddocs/kb/registry.mddocs/kb/building.mddocs/kb/deployment.mddocs/kb/docker-nginx.mddocs/kb/private-networks.mddocs/kb/embedding.mddocs/kb/changelog.mddata/showcase.yml.kb-sync/features.ymlsyncedset tov1.3.1;kb-docs.jsonpagesregenerated by the build.python scripts/pack.py --headlesssucceeds with no warnings. The Docs Template pages were not touched.Upstream disagreements (prose vs code)
contract/STYLE_GUIDE.mdtells authors to load Inter from Google Fonts, butcontract/RULES.md(KB-CSP-001) andnginx.headers.confblock third-party fonts and styles. Documented as: bundle the font.contract/DEPLOYMENT.mdlists the headlinekb-build.jsonexample without theheadlessandiframesfields thatscripts/build-vite.js(writeProvenance) writes. The guide documents what the code writes.contract/RULES.mdandcontract/ARTIFACT.mdsay an unknown icon falls back tobook-open;contract/kb-docs.schema.jsonmakesiconanenum, so schema validation (KB-MAN-001) rejects it first.src/utils/registry.jsis the only place the fallback applies.contract/DEPLOYMENT.mdsays the Knowledge Base build needs Node 24; the actions run on Node 20 (actions/*/action.yml). Both are documented separately.Changes needed outside my area
.github/workflows/pack.ymlis unchanged and still valid for v1.3.1.docs/index.md.newis a stray scratch file I created and could not delete becausermwas denied in the sandbox; it is not committed. Please ignore it.Release Notes