[blogger] persist post-outcomes.json runtime state - #130
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
These 6 files (draft, template docx, hero/og images for mahdar-ijtimaa-majlis-idara-ar) got swept into the previous ship commit by mistake -- they're leftover from an interrupted earlier run of this same blogger routine, targeting a keyword this session's live SERP research rejected (navigational, dominated by real NGOs' own board-minutes archives). Not part of the namuthaj refresh this PR ships. Preserved in git history (be9e555) if worth revisiting later.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a versioned blogger loop memory JSON file with scoring metadata, a winning-pattern narrative, per-post performance outcomes and diagnostics, and aggregate verdict counts with verification timestamps. ChangesBlogger outcome tracking
Estimated code review effort: 3 (Moderate) | ~15–30 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4 tasks
Smetools
added a commit
that referenced
this pull request
Jul 16, 2026
…ncile entry count (#132) R5 (approved): burn-state.json's posts_this_week was purely agent-narrated (AGENT.md/ROUTINE.md said `posts_this_week++`, no code enforced it) and drifted silently -- it read 1 for week_start=2026-07-05 while post-outcomes.json shows 2 real posts published that week (jadwal-aamal-ijtimaa-ar 07-06, how-to-do- meeting-minutes 07-08). Fix: correct the value to 2 now, add a _schema_note inside burn-state.json documenting it must ALWAYS be recomputed from post-outcomes.json (never hand-incremented), and update AGENT.md + this repo's ROUTINE.md prose (the only "logic" that ever set this field) to match. Promoted burn-state.json from gitignored to tracked (same rationale as post-outcomes.json in PR #130) so future drift shows up in a PR diff instead of vanishing untracked. total_posts (8) is separately and visibly stale vs the real count (20) -- flagged in the file's own note, out of scope for this fix. R6 (approved): reconciled post-outcomes.json's entry count. True count = 20 (node JSON.parse: posts.length=20, matches the file's own summary.total_posts: 20; no duplicate slugs). The ~19-vs-20 gap a direct read produced is best explained by one malformed entry (knowcap-vs-read-ai-otter-fireflies-mena- comparison) that has DUPLICATE JSON KEYS (impressions_28d/avg_pos_28d each appear twice -- stale pre-refresh values left in alongside the 2026-06-29 refresh's appended values). Not a duplicate OBJECT/entry, so per instructions this is flagged, not silently edited -- left untouched for Hassan's own review. Claude-Session: https://claude.ai/code/session_01L6te4iV4hTVLD1CqKVfjCz Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
2 tasks
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.
Summary
routines/blogger/post-outcomes.json(the blogger loop's runtime memory — verdicts/clicks/impressions per shipped post) which had never been committed before. Ship swept it up as an uncommitted file.mahdar-ijtimaa-majlis-idara-artopic) that ship's same sweep accidentally added in the first commit here — leftover from an interrupted earlier run, targeting a keyword this session's SERP research rejected. Net effect after both commits: only the JSON state file lands.No code changes, no blog content changes (PR #129 already shipped and merged those separately).
🤖 Generated with Claude Code
https://claude.ai/code/session_01PctRre9jyDDFkr3JuSZoGH
Summary by CodeRabbit