Skip to content

docs: correct stale cron schedule (Sun → Mon-Fri, 4 files) + subagent count 15→18 + INFLIGHT.md housekeeping#243

Merged
dackclup merged 1 commit into
mainfrom
claude/eager-bohr-12bQi
May 24, 2026
Merged

docs: correct stale cron schedule (Sun → Mon-Fri, 4 files) + subagent count 15→18 + INFLIGHT.md housekeeping#243
dackclup merged 1 commit into
mainfrom
claude/eager-bohr-12bQi

Conversation

@dackclup
Copy link
Copy Markdown
Owner

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.yml schedule 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 -p confirms the schedule has been "0 22 * * 1-5" since the workflow was created. The handoff itself was wrong.

Cron-schedule corrections (4 files)

File:Line Before After
CLAUDE.md:31 (§Stack) "weekly compute-rankings.yml (cron Sun 22:00 UTC)" "weekday compute-rankings.yml (cron Mon-Fri 22:00 UTC; weekends skipped — no new trading data)"
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) "GitHub Actions cron / Sun 22:00 UTC" + "run weekly" "GitHub Actions cron / Mon-Fri 22:00 UTC" + "run weekdays"
docs/stock_ranking_knowledge.md:993 "Weekly Sunday 22:00 UTC: Main compute cron" "Weekday Mon-Fri 22:00 UTC: Main compute cron (weekends skipped — no new trading data)"

Companion stale-info found during audit

PHASE_STATUS_INFLIGHT.md housekeeping

Per PR #237 convention (append-only with periodic move from "In flight" → "Merged" sub-section):

Audit completeness (verified current, no fix needed)

  • Schema version 0.10.2-phase4.5e — verified current across CLAUDE.md, PHASE_STATUS.md, AGENTS.md
  • 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

Files touched

File Δ Reason
CLAUDE.md +1 / −1 §Stack cron schedule
AGENTS.md +1 / −1 Subagent count 15→18
docs/ARCHITECTURE.md +1 / −1 Mermaid diagram cron
docs/RESEARCH_FINDINGS.md +1 / −1 Cron schedule prose
docs/stock_ranking_knowledge.md +1 / −1 Cron schedule prose
PHASE_STATUS_INFLIGHT.md +71 / −100 Housekeep PR #241+#242 → Merged + structural cleanup

No 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 project
  • grep -nE "## (PR|In flight|Merged)" PHASE_STATUS_INFLIGHT.md confirms 1 In-flight + 1 Merged section
  • Frontend (build) CI green (doc-only)
  • Python (lint + test) CI green (doc-only)
  • Vercel preview deploys green

Note 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

…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
@vercel
Copy link
Copy Markdown

vercel Bot commented May 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
quantrank Ready Ready Preview, Comment May 24, 2026 3:41pm

@dackclup dackclup marked this pull request as ready for review May 24, 2026 15:54
@dackclup dackclup merged commit af1079c into main May 24, 2026
4 checks passed
@dackclup dackclup deleted the claude/eager-bohr-12bQi branch May 24, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants