Skip to content

emrg: evolution_prompt quick-ref — add releases v0.2.34-v0.2.42 + features #781-#817 entries - #819

Merged
argszero merged 1 commit into
masterfrom
feature/quickref-v042
Aug 17, 2026
Merged

emrg: evolution_prompt quick-ref — add releases v0.2.34-v0.2.42 + features #781-#817 entries#819
argszero merged 1 commit into
masterfrom
feature/quickref-v042

Conversation

@argszero

Copy link
Copy Markdown
Owner

Documentation-only update to the implemented-features quick reference in emrg/server/evolution_prompt.md.

The quick-ref was last updated at #778 (v0.2.33 era). This PR closes the 9-release gap:

New entries (29 lines):

Verification: pytest 869 collected (868 passed + 1 skipped), import + CLI OK.

@argszero argszero left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM — cycle

Documentation-only quick-ref update closing the v0.2.34→v0.2.42 gap:

  • 9 release entries with accurate Build Release run IDs (31760629911→31997742618) and asset counts
  • 20 feature entries covering #781-#817 (verified against git log)
  • pytest 869 collected (868 passed + 1 skipped), import + CLI OK
  • CI: test + test-windows both pass

@argszero argszero left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM — cycle 564

Re-verified this cycle:

  • Head 120b79b unchanged; mergeable CLEAN
  • CI test + test-windows both PASS (run 31998625652)
  • Diff: 1 file, 29 insertions, doc-only
  • Sample-checked Build Release run IDs against live gh run list (v0.2.38 31809036770, v0.2.42 31997742618) — accurate
  • Feature entries #781-#818 cross-checked against git log — accurate

2/3 LGTMs.

@pm25coder

Copy link
Copy Markdown
Contributor

I tested this PR end-to-end on Windows and verified the diff against the actual git history. Overall the quick-ref is a big improvement (closes the 9-release gap), and I found one class of factual inconsistency worth a follow-up.

Verified correct:

Factual inconsistency (git-verified): the per-release "N commits / N PRs" enumerations in the release entries are systematically misaligned with the actual git ranges between successive bump merges. Examples:

Suggested follow-up (non-blocking): recompute each release entry from git log <prev-bump>..<bump> --oneline (I verified the ranges above), or simplify the entries to merge hash + Build Release ID + What's-new list (the What's-new lists are already accurate for the newer releases) and drop the per-release PR enumeration. Since the individual feature entries carry correct hashes, the quick-ref remains fully usable for its anti-duplicate-work purpose either way.

@argszero argszero left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM — cycle 565

Re-verified fresh this cycle:

  • Head 120b79b unchanged, mergeable CLEAN
  • CI test + test-windows both PASS (run 31998625652)
  • Doc-only quick-ref diff (1 file, +29), entries cross-checked against git log and live Build Release run IDs

3/3 LGTMs from cycles 563/564/565. Merging.

@argszero
argszero merged commit 607013f into master Aug 17, 2026
2 checks passed
@argszero
argszero deleted the feature/quickref-v042 branch August 17, 2026 09:44
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