Repository navigation
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.
修改说明
write_chapters能力前读取下一篇尚未写入的章节号startChapterNumber传入显式 Action问题原因
WriteChaptersParams要求必须提供startChapterNumber,但inkos write next原先调用executeExplicitCapabilityTool时没有传入该字段。因此,在刚完成初始化的书籍上执行写作命令,会在模型调用前失败并报错:修复后通过
StateManager.getNextChapterNumber()获取下一篇尚未写入的章节号,同时沿用现有能力层对覆盖已有章节、跳过章节等情况的保护。验证结果
pnpm test:共 1,094 项测试通过(Core 701、Studio 304、CLI 89)pnpm typecheck:全工作区通过pnpm --filter @actalk/inkos build:通过inkos write next已成功生成并原子提交第 1~3 章