Repository navigation
docs: correct stale source and npm version references to 0.6.3 / 0.6.9 - #485
Closed
hetaoBackend wants to merge 2 commits into
Closed
hetaoBackend wants to merge 2 commits into
hetaoBackend wants to merge 2 commits into
Conversation
Register the two new community documents in the public source inventory so check:source passes. - docs/community/oncall.md: role split (chat vs GitHub), rotation windows, 48h triage SLA, label hygiene rules, contribution-request rules, weekly feedback replay, reply templates, weekly metrics. - docs/community/groups.md: three community layers and what belongs in each, the single entry point, movement rules, Insider external-disclosure rule, showcase wall and AMA format.
README, README_ZH, SECURITY, installation, open-source-status, release-audit, releasing, telemetry, tui-capabilities and verification still declared 0.4.12 while package.json is 0.6.3 and the published npm package is 0.6.9. The version and evidence baseline table named packages/tui/package.json as its source of truth while asserting a value that file contradicted. The data directory default was verified against the published 0.6.9 package before updating the references that name it. Historical records are intentionally left unchanged: the reviewed 0.4.12 import and shared-source baseline in docs/verification.md, the packages/tui CHANGELOG timelines, and release/extraction.json.
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.
变更
修正公开仓中过期的版本引用。
package.json与packages/tui/package.json为 0.6.3，已发布的 npm 包为 0.6.9，但 10 个文档文件仍声明 0.4.12。docs/open-source-status.md的 "Version and evidence baseline" 表有一列叫 Source of truth，其中写着packages/tui/package.json是 0.4.12 的来源——而那个文件写的是 0.6.3。一张自称"可证明"的表用可被机器读取的文件做了错误断言。修正范围（10 文件 / 23 处）
README.mdREADME_ZH.mdSECURITY.mddocs/installation.mddocs/open-source-status.mddocs/release-audit.mddocs/releasing.mddocs/telemetry.mddocs/tui-capabilities.mddocs/verification.md刻意不修正的历史记录（5 处）
这些不是当前声明，改动等于篡改记录或制造第二套事实来源：
docs/verification.md:5docs/verification.md:299b9885e4（TUI 0.4.12）packages/tui/CHANGELOG.md:23packages/tui/CHANGELOG.zh-CN.md:20release/extraction.json:37productBaseline基线快照核验方式
@minimax-ai/code@0.6.9发布包，确认".minimax"仍是默认数据目录字面量（8 处引用），据此才更新README.md/README_ZH.md/SECURITY.md/docs/telemetry.md/docs/installation.md中声明该默认值的句子。验证
pnpm verify --profile docs→ 4 gates PASS（check:source4335 文件、check:tsconfig128 导出、export source preview、test:release-tools55 tests / 54 pass / 1 skip）。在干净 worktree 中执行；主工作区存在一个 9-23 遗留的未跟踪测试文件会阻断
check:source，与本 PR 无关。关联
check:source的版本比对子检查（序 7）准备干净基线。该子检查本 PR 不包含——scripts/source-inventory.mjs需等 docs(plugins): publish Plugin V1 format contract, schemas and a dependency-free public validator #484 合入后再单独开 PR，避免并发修改同一脚本。packages/tui/CHANGELOG.md停在 0.5.5，待回填 0.6.0–0.6.3（序 6），本 PR 不涉及。Need help on this PR? Tag
@codesmith-botwith what you need.