Repository navigation
Fix the duplicated Documentation Index entries in README.md - #22
Conversation
Remove the trailing broken CHANGELOG fragment and the leftover mic-Dawn bullet, leaving one clean entry for each document. The existing SHA256SUMS entry for README.md already matches the corrected file, so the manifest is unchanged. Signed-off-by: Orda <342776047+orda-aska@users.noreply.github.com>
ahrazzle
left a comment
There was a problem hiding this comment.
The head is 93d24b60ea9861486aab8da9c65eebf4ff22092c, parent and current origin/main are b9325fd1cfaa57f1f1bafc54ec30d334130d01fc. git diff --stat b9325fd..93d24b60 is README.md | 2 --. The deleted lines are the CHANGELOG bullet ending identifiers.- and the leftover - mic-Dawn quasar confrontation, and next-agent handoff queue. git show 70a1204a -- README.md adds both of those lines in the Documentation Index. The remaining index is one bullet each for CLAIMS.md, METHODS_AND_PLAYBOOK.md, RESEARCH_NOTEBOOK_AND_REASONING.md, and CHANGELOG.md. The Cosmic-Dawn sentence stays on the research-notebook bullet.
git show 93d24b60:README.md | sha256sum is 7ef0ccad4d71620b53c85ff93f2afd5e36695e63ae8befeff91159706624b985. That is line 32 of SHA256SUMS on this head and on main. The manifest blob is db794967f98e968570d9cb3f5ab239443a2d21d7 on both. sha256sum -c SHA256SUMS on an archive of main reports WARNING: 8 computed checksums did NOT match, including README.md: FAILED, plus verify_all.py, wave5_unified_forces_stochastic_qm.py, formal/verify_exact_rational_proofs.py, formal/GravityClaims.lean, formal/Wave12QuasarCollapse.lean, results/wave4_unified_certificates.json, and CLAIMS.md. The same command on this head reports WARNING: 7 computed checksums did NOT match. The only line that changes is README.md: FAILED becoming an OK. No new failure appears.
git merge-tree --write-tree origin/main 93d24b60 exits 0 and writes f1779fda7cd937aa88fb4bfc49fa226dbc1e6972. The diff of that tree against main is the same two-line README deletion. GitHub reports the PR MERGEABLE with mergeStateStatus: BLOCKED. There are no reviews or comments. Pairwise git merge-tree --write-tree 93d24b60 <other>:
- #15 (
ca55815c) exits 1,CONFLICT (content): Merge conflict in SHA256SUMS. This commit does not edit that file. The conflict is current main’s manifest against #15’s rewrite. - #19, #21, #8, #9, #11, and #12 exit 0. Each merged Documentation Index keeps one clean bullet for the four documents. #19 also keeps its
acceleration-evolution/bullet. The combined root README digest is not the README line left inSHA256SUMSfor those six, because each of them also edits README: #19’s merged file ise8fe999c…against sums line72606ab3…; #21 is1f94e7d7…againstea84eb79…; #8, #9, #11, and #12 keep sums line7ef0ccad…while the merged README hashes are62e5c465…,463bebd2…,bf16e633…, and1bb5c14a….
Fixes the broken Documentation Index in
README.md, introduced in70a1204a.The CHANGELOG bullet had a trailing
.-, then a leftover fragmentmic-Dawn quasar confrontation, and next-agent handoff queue., then the same CHANGELOG bullet again. This change removes those two stray lines and leaves one clean entry for each ofCLAIMS.md,METHODS_AND_PLAYBOOK.md,RESEARCH_NOTEBOOK_AND_REASONING.mdandCHANGELOG.md.SHA256SUMSalready records the hash of the corrected file (7ef0ccad...), so the typo was also a manifest mismatch. That line is left unchanged, and the mismatch goes away. The other seven pre-existing mismatches on main are untouched and still belong to the checksum refresh in #15.