Skip to content

docs(post-v1.2): record v1.2.0-phase4.5 ship + triage next deliverables + file follow-up issues#105

Merged
dackclup merged 1 commit into
mainfrom
chore/post-v1.2-polish
May 17, 2026
Merged

docs(post-v1.2): record v1.2.0-phase4.5 ship + triage next deliverables + file follow-up issues#105
dackclup merged 1 commit into
mainfrom
chore/post-v1.2-polish

Conversation

@dackclup
Copy link
Copy Markdown
Owner

Summary

Post-v1.2 polish — records the tag ship + triages next deliverables in the two header docs (CLAUDE.md + PHASE_STATUS.md) that contributors and Claude read first. Also files 2 Phase 4.5 follow-up issues filed alongside the docs update.

Doc updates

CLAUDE.md "Phase status":

  • Latest release tag: v1.0.0 (stale) → v1.2.0-phase4.5 with release link
  • Production commit reference: e57f09cb (chore commit) → b1588b2a (actual ship commit)
  • "Next deliverable: tag v1.2.0-phase4.5" → tag shipped; next is now a triage between 4.5e (Form 4 insider, ~3w → v1.3.0) / 4h-4k factor integrations (~6w → v1.1.0-phase4) / Phase 5 ML meta-learner

PHASE_STATUS.md "Current focus":

Issues filed (live links)

# Title Why
#103 loss_avoidance_pattern fires 0% on S&P 500 — Burgstahler-Dichev 1997 thresholds too tight for large-cap universe Phase 4.5d follow-up; PR #97 design substitution caveat now formally tracked. Recommended fix: Option A (universe-scaled thresholds NI ≤ $25M / EPS ≤ $0.25) once PR 4b §2 PBO/DSR backtest harness is wired into a calibration loop
#104 Tag-naming inconsistency: 1.0.0 should be re-tagged as v1.0.0-phase3e to match the project convention Pure housekeeping. Recommended fix: Option A (add v1.0.0-phase3e as a sibling alias tag, do not delete 1.0.0)

What this PR explicitly does NOT do

Verification ladder

  • ruff check . — All checks passed
  • pytest tests/ -m "not network"856 passed (no regressions)
  • No code changes — verification ladder reduced to lint + test sanity

https://claude.ai/code/session_015649aRyi2bvciQYZVNACd2


Generated by Claude Code

Updates the two header docs (CLAUDE.md + PHASE_STATUS.md) that
contributors and Claude alike read first, so post-v1.2 context is
current:

- Latest release tag: 1.0.0 (stale) → v1.2.0-phase4.5
- Production commit: e57f09c (incorrect — that was a chore commit;
  the ship commit is b1588b2) → b1588b2
- "Next deliverable: tag v1.2.0-phase4.5" → tag is shipped; next
  is now a triage between 4.5e / 4h-4k / Phase 5 with effort
  estimates and which slots are already reserved

PHASE_STATUS.md header section trimmed from "current focus = Phase 4
4f-implementation-next" to the post-v1.2 state with a 6-line
header pointing at issue numbers + the per-phase blocks below for
detail. Mirrors the same tightening done in CLAUDE.md.

Two new issues filed post-tag (Phase 4.5 follow-ups, both
non-blocking):

- #103 — loss_avoidance_pattern fires 0% on S&P 500 (Burgstahler-
  Dichev 1997 cohort thresholds too tight for large-cap universe);
  follow-up to PR #97 (Phase 4.5d). Recommended fix: Option A
  (universe-scaled thresholds: NI ≤ $25M, EPS ≤ $0.25) once PR 4b §2
  PBO/DSR backtest harness is wired into a calibration loop.
- #104 — Tag-naming inconsistency: 1.0.0 sits off-pattern relative
  to the v0.X-phaseN / v1.2.0-phase4.5 family; recommended fix:
  Option A (add v1.0.0-phase3e as a sibling alias tag, do not
  delete 1.0.0). Pure housekeeping.

No code changes — pure docs / metadata. Verification:
- ruff check . → All checks passed
- pytest -m "not network" → 856 passed (no regressions)

https://claude.ai/code/session_015649aRyi2bvciQYZVNACd2
@vercel
Copy link
Copy Markdown

vercel Bot commented May 17, 2026

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

Project Deployment Actions Updated (UTC)
quantrank Ready Ready Preview, Comment May 17, 2026 7:29am

@dackclup dackclup marked this pull request as ready for review May 17, 2026 07:31
@dackclup dackclup merged commit a12bd81 into main May 17, 2026
4 checks passed
@dackclup dackclup deleted the chore/post-v1.2-polish branch May 17, 2026 07:31
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.

loss_avoidance_pattern fires 0% on S&P 500 — Burgstahler-Dichev 1997 thresholds too tight for large-cap universe

2 participants