docs(housekeeping): post-session 2026-05-28 — drain INFLIGHT + bump pointers + add root CONTEXT.md#296
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…main.md End-of-day Track-A3 follow-up to the post-session-housekeeping commit (0949a3c). Adds a single-file CONTEXT.md entry point at the repo root so external tools / fresh agents / vendored skills that expect the upstream mattpocock single-CONTEXT.md convention have one bridge file to read first. Reconciles docs/agents/domain.md which previously declared "QuantRank has NO CONTEXT.md" (now stale). Changes (3 files, doc-only — additive): - CONTEXT.md (NEW, ~245 lines) — bridge / live-snapshot pointer. 11 sections: Design note (explicit "not source of truth" framing) · What is QuantRank · Live snapshot (schema 0.10.8-phase4.6 · v1.4.0-phase4.6 tag · 33 declared flags · USE_SECTOR_COE=True post-#294 · cron #69 green) · Multi-file mapping (12-row file→topic + 6-row topic→file tables mirroring docs/agents/domain.md) · 8 Key invariants (Rule 16 / schema triple / Rule 18 / lockstep / rebase / mobile-only / formula sacred / orchestrator role) · Stack · Layout · Quick-start commands · 9 Standing constraints · 7 Vocabulary discipline terms · Roadmap pointer (Stage 0 → Stage 6 / v2.0) · Companion files index. - docs/agents/domain.md §"QuantRank has NO CONTEXT.md" — section header + opening paragraph rewritten to "CONTEXT.md is a pointer, not the source of truth" with the new framing (the four-file analog remains canonical; CONTEXT.md is a bridge). Topic-driven lookup table + "update CONTEXT.md inline when a term resolves" + "Use the project vocabulary" sections unchanged — their semantics still apply (updates land in the appropriate deep file, not in CONTEXT.md which is pointer-only). - PHASE_STATUS_INFLIGHT.md — appended in-flight entry per §Conventions lockstep (PR #237 convention). Design discipline: - CONTEXT.md MUST NOT duplicate content from the four canonical files (CLAUDE.md + SKILL.md + WORKFLOW.md + docs/METHODOLOGY.md) — when content drifts, the four files win and CONTEXT.md updates to point at the new location. - "Live snapshot" block IS expected to drift; the next end-of-session housekeeping commit refreshes it the same way it refreshes CLAUDE.md §Phase status. Doc-only PR — ruff / schema_check N/A; no compute / schema / scoring / valuation / frontend / Python / TS change. CLAUDE.md substance untouched this PR (CONTEXT.md is a NEW top-level file that pointers TO CLAUDE.md, not a substance change WITHIN it).
dackclup
force-pushed
the
claude/post-session-housekeeping-2026-05-28
branch
from
5dbbb3a to
eb52495
Compare
Merged
4 tasks
dackclup
added a commit
that referenced
this pull request
May 28, 2026
…rkers + bump pointers (#299) Closes today's 10-PR cycle (#286 / #290 / #291 / #292 / #293 / #294 / #295 / #296 / #297 / #298). Mirror of PR #286 (post-v1.4.0 cycle drain) for the post-cron-#71 cycle. Three stale `(in flight, 2026-05-28)` markers in PHASE_STATUS_INFLIGHT.md drained to `(merged 2026-05-28, <SHA>)`: - PR #295 (`2d2ec83e`) — Post-session housekeeping drain 6 INFLIGHT + bump pointers - PR #297 (`ecb60e64`) — Issue #287 PR A: durable timeout + cache canary + per-loop wall-clock Metadata (schema 0.10.8 → 0.10.9-phase4.6) - PR #298 (`030675e9`) — Issue #288 follow-up: cache-key bump v4 → v5 Bodies preserved (historical record). CLAUDE.md §Phase status — drained the "(In flight this PR — cache-v5)" qualifier (PR #298 merged) + added post-PR-#298 confirmation note + cron Run #71 production-verified pointer. AGENTS.md open-issues list — #288 status flipped "(fix in flight this PR)" → "(closed by PR #298 cache-v5 bump)" + clarified the silent- failure root-cause + Run #72 verification gate. Why this PR exists: without end-of-day drain, session N+1 reading CLAUDE.md / PHASE_STATUS_INFLIGHT.md would see 3 PRs still marked "in flight" despite them merging hours earlier — the same friction pattern PR #286 closed for the post-v1.4.0 cycle. Three same-day drains in one PR keeps the side-file disciplined. Scope (3 files, doc-only): - PHASE_STATUS_INFLIGHT.md — 3 header substitutions + this PR's own in-flight entry appended per PR #237 side-file convention - CLAUDE.md §Phase status pointer refresh - AGENTS.md open-issues list #288 status update Hard constraints honored: - No code / scoring / schema / valuation / Rule 16 / Top-5 invariant touched - No new defense flag · No new dep · No new env-var - Doc-only diff (Markdown only) - Schema version UNCHANGED at 0.10.9-phase4.6 (no Pydantic / TS / snapshot change) PHASE_STATUS_INFLIGHT.md side-file satisfies §Conventions "ship with every PR" lockstep per PR #237 convention. Same drain template as PR #286 (post-v1.4.0 cycle). https://claude.ai/code/session_01AGU8d6pm4u2fQQ5cebg9qa Co-authored-by: Claude <noreply@anthropic.com>
dackclup
added a commit
that referenced
this pull request
May 28, 2026
…ULD-FIX cross-doc drifts (#301) Comprehensive .md housekeeping closing today's 11-PR session day. Output of docs-reviewer (sonnet) full Tier 1 + Tier 2 audit on main (post-PR-#299) — verdict NEEDS-CROSS-REF-FIX with 14 prioritized findings; this PR applies all 8 MUST-FIX + 6 SHOULD-FIX. 3 NICE-TO-FIX deferred to follow-up. Scope (7 files, doc-only): - SKILL.md schema-version history table (line 240) — prepend 2 new rows: 0.10.9-phase4.6 (PR #297, 4 *_wall_clock_seconds fields + 195m timeout + cache canary, empirically validated cron Run #71) + 0.10.10-phase4.6 (PR #300 in flight — Issue #67 follow-up per- sector delta). Closes the canonical-history gap where PR #297 + PR #300 were absent. - PHASE_STATUS.md §Current state — schema row 0.10.8 → 0.10.9 + PR #300 in-flight note; Post-tag production patches row extended with PR #295/#296/#297/#298/#299 SHAs + one-liners; Production run pointer 0ad1d57 cron #69 → 368dccd cron Run #71 with the PR #297 wall-clock empirical numbers + Issue #288 cache-replay smoking gun (multi_class_per_class_attempt_count=0 + fundamentals_latency_p50_seconds=0.0). Recently merged block extended 6 → 11 PRs. Issue closure status updated. Next deliverables refreshed: Issue #67 flip removed (PR #294 already executed); item 2 now = Issue #287 PR B FORM4 revert; PR #300 per-sector delta added as item 3. Open issues list refreshed (#288 + #289 marked closed; #287 PR A vs PR B split). - CLAUDE.md §Phase status Recently merged block — extended 6 → 11 PRs with full SHA + one-liner per PR. New "In flight" sub-section added for PR #300. - AGENTS.md §Phase + version state — Production-verified run cron #69 (233117a, 13m 16s) → cron Run #71 (368dccd, 14m 32s, 2026-05-28 08:44 UTC, schema 0.10.7 → 0.10.9-phase4.6); 4 new wall-clock field values cited; Issue #288 cache-replay smoking gun captured; closed-issue note for #288 + #289 + #287 PR A. - CONTEXT.md §Live snapshot — schema 0.10.8 → 0.10.9 + PR #300 in-flight note; new "Post-tag patches" row listing PRs #292-#299 + PR #300 in flight; cron status cron #69 2026-05-27 → Run #71 2026-05-28; Sector-CoE row updated with empirical 132 → 109; §Roadmap Stage 0 description refreshed. - WORKFLOW.md §Agentic 6-Phase Cadence session-start protocol — inline schema 0.10.7-phase4.6 replaced with current 0.10.9-phase4.6 + pointer guidance to PHASE_STATUS.md §Current state as the canonical bump-per-schema-PR target. Closes the recurring inline- schema drift pattern. - PHASE_STATUS_INFLIGHT.md — this PR's in-flight entry appended per PR #237 side-file convention. docs-reviewer lockstep cross-check after this PR: - SCHEMA_VERSION: ALIGNED across all 6 canonical docs at 0.10.9-phase4.6 with PR #300 in-flight note where applicable - Defense layer 33 declared: ALIGNED (was already) - USE_SECTOR_COE = True post-PR #294: ALIGNED (was stale in AGENTS.md issue #67 framing + PHASE_STATUS.md Next deliverables; both fixed) - Subagent count 18: ALIGNED (was already) - Skill count 45: ALIGNED (was already) - Latest cron Run #71 368dccd: ALIGNED (was stale in AGENTS.md + PHASE_STATUS.md + CONTEXT.md; all fixed) - Issue #288 + #289 closure status: ALIGNED (was stale as open in AGENTS.md + PHASE_STATUS.md; both fixed) 3 NICE-TO-FIX deferred: - README.md Honest Limitations does not reference Phase 4.6 honest re-validation harness (PR #283). Coverage gap, not break. - WORKFLOW.md Phase 4.5 row cites v1.2.0; technically closed at v1.3.0-phase4.5e. Historical-context only. - METHODOLOGY.md USE_SECTOR_COE framing needs verification before edit. Hard constraints honored: - No code / scoring / schema / valuation / Rule 16 / Top-5 invariant touched - No new defense flag · No new dep · No new env-var - Markdown-only diff (no JSON / YAML / Python / TS change) - Schema version UNCHANGED on main at 0.10.9-phase4.6 (PR #300 will bump 0.10.10 on its merge) - AGENTS.md substance lockstep with CLAUDE.md per the established delegation pattern Verification: - ruff check . PASS (no Python touched) - python -m compute.output.schema_check PASS (no schema touched) - pytest tests/ -m "not network" N/A (no test surface) - Cross-reference grep — all 7 anchor strings consistent across all 6 docs after fix https://claude.ai/code/session_01AGU8d6pm4u2fQQ5cebg9qa Co-authored-by: Claude <noreply@anthropic.com>
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
2 participants
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
End-of-day housekeeping bundle landing two commits that close the doc-drift loop after 6 PRs landed on
maintoday (#286 / #290 / #291 / #292 / #293 / #294) AND add a root-level orientation pointer.Commit 1 —
0949a3c1· post-session-housekeeping pointer bumps (4 files)0.10.7-phase4.6 → 0.10.8-phase4.6; defense layer narrative notesUSE_SECTOR_COE = Truepost-feat(valuation): Issue #67 — flip USE_SECTOR_COE True (Damodaran 11-sector Ke) #294; new "Post-tag production patches" subsection citing PRs fix(ingest): Issue #288 — GOOG/GOOGL XBRL concept-name omission (market_cap2.2× inflated) #292 / fix(valuation): Issue #289 — retire Site-2 DQIC ceiling per Option C (NVR FP) #293 / feat(valuation): Issue #67 — flip USE_SECTOR_COE True (Damodaran 11-sector Ke) #294. "Recently merged" list prepended with 6 same-day entries; legacy "Earlier (PR feat(scoring): Issue #261 PR-A — multi_class_aggregate_shares_suspected annotate (CIK-collision detector) #264 → PR docs(release): codify mobile-only operator convention for tag releases #285)" subsection relabeled.559c5269 → 0ad1d574(cron docs(skill): frontend-design-system — capture chip / badge / palette rules #69 chore-commit).0.10.8-phase4.6(PR fix(ingest): Issue #288 — GOOG/GOOGL XBRL concept-name omission (market_cap2.2× inflated) #292 GOOG/GOOGL XBRL fix + Rule 18 disambiguator).(in flight, 2026-05-28)markers drained to(merged 2026-05-28, <SHA>). Bodies preserved.Commit 2 —
5dbbb3a7· add rootCONTEXT.mdpointer + reconciledocs/agents/domain.md(3 files)CONTEXT.md(NEW, ~245 lines) — bridge / live-snapshot pointer. 11 sections: Design note (explicit "not source of truth") · What is QuantRank · Live snapshot (schema0.10.8-phase4.6·v1.4.0-phase4.6tag · 33 declared flags ·USE_SECTOR_COE=True· cron docs(skill): frontend-design-system — capture chip / badge / palette rules #69 green) · Multi-file mapping (12-row + 6-row tables mirroringdocs/agents/domain.md) · 8 Key invariants (Rule 16 / schema triple / Rule 18 / lockstep / rebase / mobile-only / formula sacred / orchestrator role) · Stack · Layout · Quick-start commands · 9 Standing constraints · 7 Vocabulary discipline terms · Roadmap pointer (Stage 0 → Stage 6 / v2.0) · Companion files index.docs/agents/domain.md§"QuantRank has NOCONTEXT.md" — rewritten to "CONTEXT.mdis a pointer, not the source of truth" framing. Topic-driven lookup table + "Use the project vocabulary" + "Flag conflicts" sections unchanged — their semantics still apply (updates land in the appropriate deep file, not in CONTEXT.md).Design discipline (CONTEXT.md)
CONTEXT.mdMUST NOT duplicate content from the four canonical files (CLAUDE.md + SKILL.md + WORKFLOW.md + docs/METHODOLOGY.md) — when content drifts, the four files win andCONTEXT.mdupdates to point at the new location.Why this PR
0.10.7despite code shipping0.10.8, and "Recently merged" misses 6 PRs from today. Track A morning bump (PR chore(docs): housekeeping PR-B — drain INFLIGHT + bump pointers post-v1.4.0 #286) handled feat(scoring): Issue #261 PR-A — multi_class_aggregate_shares_suspected annotate (CIK-collision detector) #264-docs(release): codify mobile-only operator convention for tag releases #285; this bundle handles chore(docs): housekeeping PR-B — drain INFLIGHT + bump pointers post-v1.4.0 #286-feat(valuation): Issue #67 — flip USE_SECTOR_COE True (Damodaran 11-sector Ke) #294 end-of-day.docs/agents/domain.mddeclared "QuantRank has NO CONTEXT.md" by design, but any vendored skill / external agent that expects to readCONTEXT.mdfirst 404s. Pointer-only file satisfies the contract without compromising the four-file analog.Test plan
ruff check .— N/A (no Python touched)python -m compute.output.schema_check— N/A (no schema touched)pytest tests/ -m "not network"— N/A (no test surface)CONTEXT.md— all targets exist onmainHard constraints honored
Generated by Claude Code