fix: preserve runtimeStateDelta after chapter content normalization#149
Open
tank7155611 wants to merge 11 commits intoNarcooo:masterfrom
Open
fix: preserve runtimeStateDelta after chapter content normalization#149tank7155611 wants to merge 11 commits intoNarcooo:masterfrom
tank7155611 wants to merge 11 commits intoNarcooo:masterfrom
Conversation
Author
|
#146 |
Writing pipeline overhaul driven by Meta-Harness autoresearch: - Foundation Reviewer with 5-dimension scoring and reject/retry loop - New-spacetime requirements for fanfic mode - Hook seed excerpt system (replacing lifecycle pressure) - Review reject state rollback - State validation recovery with settler retry - Chapter number anchoring to contiguous durable artifacts - Audit drift isolation - Title collapse auto-repair - Hook budget hints and chapter ending trail - Mood/title/scene fatigue detection Benchmark: from-scratch novels improved from 75 to 92/100.
v1.1.0: Writing Pipeline Overhaul
- README.en.md: add Foundation Review, Hook Seed Excerpt, Review Reject Rollback sections; update audit, continuation, fanfic - README.ja.md: same sections translated to Japanese - skills/SKILL.md: bump skill version, add Phase 0 (foundation review), update pipeline description, add new commands
1. writer-repair.ts: Full Chinese/English prompt symmetry. Removed "LANGUAGE OVERRIDE" prefix approach. Every prompt string (mode descriptions, output format, system prompt, section headers) now has a native Chinese and English variant selected by book language. 2. architect.ts: generateFoundationFromImport now includes "续写方向要求" — continuation/series must design new narrative space (new conflict dimension, 5-chapter ignition, 50% fresh scenes, no repeating meetings). Also accepts reviewFeedback. 3. runner.ts: importChapters flow now goes through generateAndReviewFoundation with mode="series", so Foundation Reviewer audits continuation/import foundations too. All three creative modes (original, fanfic, series/continuation) now have new-spacetime requirements and foundation review.
When chapter content is normalized or revised (finalContent !== output.content), buildPersistenceOutput calls analyzeChapter whose output may not include runtimeStateDelta. This caused chapter_summaries.json to not be updated, making the planner repeat the previous chapter plot events on the next write. Also fix mustAdvance hook sort direction (ascending, not descending) so that the most neglected hooks are surfaced first.
b1b1c08 to
eb59f76
Compare
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.
When chapter content is normalized or revised (finalContent !== output.content),
buildPersistenceOutput calls analyzeChapter whose output may not include
runtimeStateDelta. This caused chapter_summaries.json to not be updated,
making the planner repeat the previous chapter plot events on the next write.
Also fix mustAdvance hook sort direction (ascending, not descending) so that
the most neglected hooks are surfaced first.
Summary
Type of change
Motivation (optional)
Changes
Usage (optional)
Test plan
pnpm typecheckpassespnpm testpasses (all existing + new tests)Breaking changes (optional)