docs: correct stale cron schedule (Sun → Mon-Fri, 4 files) + subagent count 15→18 + INFLIGHT.md housekeeping#243
Merged
Merged
Conversation
…bagent count 15 → 18 + INFLIGHT.md housekeeping User called out a recurring error from session 7: I repeatedly stated "cron Sun 22:00 UTC" in summaries despite the actual workflow schedule being Mon-Fri only. ROOT CAUSE: the handoff prompt at session start said "Next prod cron: Sun 2026-05-24 22:00 UTC (cron-#4)" and I echoed that without verifying against `.github/workflows/compute-rankings.yml`. The YAML has read `"0 22 * * 1-5"` from initial commit (verified via `git log --all -p`). Inline comment in the workflow even says "Weekends skipped (no new trading data)". Stale "Sunday/Sun 22:00 UTC" references across 4 files corrected: - CLAUDE.md:31 §Stack — "cron Sun 22:00 UTC" → "cron Mon-Fri 22:00 UTC" - docs/RESEARCH_FINDINGS.md:854 — "WEEKLY (GitHub Actions, Sunday 22:00 UTC)" → "WEEKDAY (GitHub Actions, Mon-Fri 22:00 UTC; weekends skipped)" - docs/ARCHITECTURE.md:7 mermaid diagram — "Sun 22:00 UTC" → "Mon-Fri 22:00 UTC" + edge "run weekly" → "run weekdays" - docs/stock_ranking_knowledge.md:993 — "Weekly Sunday 22:00 UTC" → "Weekday Mon-Fri 22:00 UTC: Main compute cron (weekends skipped — no new trading data)" Companion stale-info fix found during audit: - AGENTS.md:1294 — "The 15 subagents under `.claude/agents/`" → "The 18 subagents under `.claude/agents/`". The roster expanded to 18 in PR #225 (ci-triage-engineer + vercel-preview-auditor + literature-searcher). AGENTS.md:91 already said 18 — line 1294 was unsynced drift. INFLIGHT.md housekeeping (per PR #237 convention — append-only with periodic move from "In flight" → "Merged" sub-section): - PR #241 (simulate Parts 5+6+7, `e9d7836`) → moved to Merged with consolidated 4-iteration summary preserving the QR_SKIP_OSAP + QR_SKIP_CROSS_SOURCE + timeout-45→90 history - PR #242 (light-mode soften + Strong Buy nowrap + StockLogo square, `a30c017`) → moved to Merged, original entry text intact - Duplicate "## Merged (awaiting housekeeping move to CLAUDE.md)" header at line 257 deleted (was a rebase-artifact duplicate from the PR #239 + PR #240 chronology resolution); file now has exactly ONE Merged section - Old "PR (this PR) — Simulate Parts 5+6+7" body block excised (lines 201-300 of the post-rebase file) — replaced by this PR's clean Doc-staleness sweep entry in the In-flight section Audit completeness: - Schema version `0.10.2-phase4.5e` — verified current across CLAUDE.md, PHASE_STATUS.md, AGENTS.md (no stale references) - Defense layer "32 boolean flags emitted" — verified current - Subagent file count = 19 in `.claude/agents/` (18 agent files + 1 README.md) — corresponds to 18 subagents, AGENTS.md:91 + :1294 now both consistent No compute / schema / scoring / valuation / Python / TypeScript code change. Doc-only PR. PHASE_STATUS_INFLIGHT.md side-file satisfies §Conventions lockstep. https://claude.ai/code/session_01JwntEE4PNAXSMkZxRA9BB4
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
User-triggered correction: "ฉันจะ manual ส่วนคุณแก้ใขไม่ให้ผิดพลาดอีก ทั้งเรื่องนี้และเรื่องอื่นๆ เช็คและอัพเดทข้อมูลให้เป็นปัจจุบันทั้งหมด"
I repeatedly stated "cron Sun 22:00 UTC (~7h)" / "(~14h)" / "(~19h)" in session 7 PR summaries despite the actual
.github/workflows/compute-rankings.ymlschedule being"0 22 * * 1-5"(Mon-Fri only). The workflow's inline comment even says "Weekends skipped (no new trading data)". The handoff prompt at session start said "Next prod cron: Sun 2026-05-24 22:00 UTC (cron-#4)" and I echoed without verifying against the YAML —git log --all -pconfirms the schedule has been"0 22 * * 1-5"since the workflow was created. The handoff itself was wrong.Cron-schedule corrections (4 files)
CLAUDE.md:31(§Stack)compute-rankings.yml(cron Sun 22:00 UTC)"compute-rankings.yml(cron Mon-Fri 22:00 UTC; weekends skipped — no new trading data)"docs/RESEARCH_FINDINGS.md:854docs/ARCHITECTURE.md:7(mermaid)docs/stock_ranking_knowledge.md:993Companion stale-info found during audit
AGENTS.md:1294— "The 15 subagents under.claude/agents/" → "The 18 subagents under.claude/agents/". Post-PR feat(agents): add ci-triage-engineer + vercel-preview-auditor + literature-searcher (15 → 18) #225 the roster expanded to 18 (ci-triage-engineer + vercel-preview-auditor + literature-searcher).AGENTS.md:91already said 18; line 1294 was unsynced drift.PHASE_STATUS_INFLIGHT.mdhousekeepingPer PR #237 convention (append-only with periodic move from "In flight" → "Merged" sub-section):
e9d7836) — moved to Merged with consolidated 4-iteration summary preserving the QR_SKIP_OSAP + QR_SKIP_CROSS_SOURCE + timeout-45→90 historya30c017) — moved to Merged, original entry text intact## Mergedheader at the prior line 257 deleted (rebase-artifact from PR docs: triple-doc lockstep refresh (PHASE_STATUS + SKILL + WORKFLOW) — unblock v1.3.0 release tag #239 + PR docs(workflow): housekeep PHASE_STATUS_INFLIGHT.md — move PR #238 entry to Merged section #240 chronology resolution); file now has exactly ONE Merged sectionAudit completeness (verified current, no fix needed)
0.10.2-phase4.5e— verified current across CLAUDE.md, PHASE_STATUS.md, AGENTS.md.claude/agents/(18 agent files + 1 README.md) — corresponds to 18 subagents, AGENTS.md:91 + :1294 now both consistentFiles touched
CLAUDE.mdAGENTS.mddocs/ARCHITECTURE.mddocs/RESEARCH_FINDINGS.mddocs/stock_ranking_knowledge.mdPHASE_STATUS_INFLIGHT.mdNo compute / schema / scoring / valuation / Python / TypeScript code change. Doc-only PR.
Test plan
git log --all -p .github/workflows/compute-rankings.yml | grep cron:confirms schedule has only ever been"0 22 * * 1-5"grep -rn "Sun 22:00\|Sunday 22:00"confirms 0 remaining stale refs across projectgrep -nE "## (PR|In flight|Merged)" PHASE_STATUS_INFLIGHT.mdconfirms 1 In-flight + 1 Merged sectionNote about the recurring "Sun" mistake
The handoff prompt error + my echo-without-verify propagated across 5+ session summaries in PRs #226 / #237 / #240 / #241. None of those PRs' shipped doc content has the wrong cron schedule (those PRs touched different files); the error was in my chat summaries only. Going forward I'll verify time-sensitive claims against source-of-truth files (YAML / config /
git log) before stating them.https://claude.ai/code/session_01JwntEE4PNAXSMkZxRA9BB4
Generated by Claude Code