Repository navigation
feat(token-forge): implement P1-005 safe exports - #3
Merged
Merged
Conversation
margrop
marked this pull request as ready for review
July 25, 2026 06:02
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.
What
实现 P1-005 的完全本地 Markdown / GitHub Issue 草稿导出:
token-forge-export-v1Schema 和合成 fixture;ExportActions使用;明确不包含 GitHub API 写操作、Token Forge 正式页面、真实 Analytics、网络、存储或部署。
Tracking
Verification
Product and safety
Cost / privacy / accessibility
导出完全本地且不消耗 AI Token。单个 Issue 正文上限 64 KiB,完整计划和 Issue 合集各 128 KiB。标识符和文件路径脱敏,Secret 失败关闭;固定安全文件名可由现有复制/下载组件消费。没有新增依赖、存储、Analytics、网络或 UI。
Known limitations
/token-forge/正式页面;