Skip to content

Dated complete/ archive + drop done originals (PR-B, #71) - #73

Merged
Jammy2211 merged 2 commits into
mainfrom
feature/lifecycle-migrate
Jul 13, 2026
Merged

Dated complete/ archive + drop done originals (PR-B, #71)#73
Jammy2211 merged 2 commits into
mainfrom
feature/lifecycle-migrate

Conversation

@Jammy2211

@Jammy2211 Jammy2211 commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

PR-B: dated complete/ archive + prune active/ to in-flight (#71)

Follows PR-A (#72, merged). Builds the token-light dated archive and cuts active/ down to genuinely in-flight work. Merge stays human.

What it does

  • complete.md → 557 per-task rich records under complete/<YYYY>/<MM>/<slug>.md (lifecycle.py split-complete): 2026/04·05·06·07·unknown = 144·212·28·161·12. 43 fold in their original prompt. The token-light Phase-2 wiki substrate.
  • active/ 440 → 7. Dropped the done/legacy prompts, keeping only those matching a live active.md in-flight task:
    • 147 provably-done originals (filename-stem == a complete.md slug),
    • then 287 more done/legacy (51 numbered early-workflow prompts, 81 complete.md-cited, and the token-overlap-to-a-shipped-record remainder).
    • All recoverable from git history; their knowledge lives in the complete/ records.
  • complete.md KEPT (not retired) and paired 1:1 by slug to the dated records — lifecycle.py check enforces record ↔ complete.md entry.
  • create_issue: mkdir -p active/ before git mv (fresh spawned templates ship no active/).
  • lifecycle.py check: OK.

Remaining kept in active/ (7, in-flight)

lifecycle_state_split, benchmark_calibration_runs, euclid_eceb_editorial_revision, keck_ao_acceptance_checks, pyautoreduce_slacs1430_acs_comparison, release_yml_testpypi_rehearsal_mode, workspace_version.

One small follow-up (optional)

For new completions to also get a paired dated record (not just the complete.md append), ship_* should write the record into complete/<YYYY>/<MM>/ as it appends complete.md. Small lifecycle.py/ship_* enhancement; its own PR.

🤖 Generated with Claude Code

…ginals (PR-B, #71)

- lifecycle.py split-complete: complete.md (557 entries) → one rich record per
  task under complete/<YYYY>/<MM>/<slug>.md (04/05/06/07/unknown =
  144/212/28/161/12); 43 fold in their original prompt. This is the token-light
  dated archive (Phase-2 wiki substrate). complete.md kept as the ongoing ledger
  backstop for now (retirement + ship_* record-write conversion = follow-up).
- Dropped the 147 provably-done active/ originals (filename-stem matches a
  complete.md slug) — knowledge now lives in the records; git history preserves
  the files. active/ 440 → 293.
- create_issue: mkdir -p active/ before git mv (fresh spawned templates ship no
  active/ dir).

lifecycle.py check: OK.

Remaining (parked for human review, see #71): the 293 unclassifiable legacy
active/ prompts (mostly old numbered prompts; only 3 match a live active.md
task, filename↔record linkage too weak to auto-sort the rest).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
#71)

Per user direction ("293 is too many, most are done"). Kept only the prompts
matching a live active.md in-flight task (generous token match, protects
in-flight); dropped the rest — 51 numbered early-workflow prompts, 81
complete.md-cited, and the token-overlap-to-a-shipped-record remainder. active/
293 → 7. All recoverable from git history; their knowledge lives in the
complete/<YYYY>/<MM>/ records. lifecycle.py check: OK.

complete.md is KEPT (not retired) and paired 1:1 by slug to the dated records
(lifecycle.py check enforces record <-> complete.md entry).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

1 participant