Sync bsd-m6-scaffolding-v0.3.2 as authoritative BSD repo baseline

[mdheller]

Objective

Make SocioProphet/bsd-proof-program the authoritative BSD Proof Program repository and ingest the uploaded bsd-m6-scaffolding-v0.3.2.zip as the v0.3.2 M6 pre-execution scaffolding baseline.

Reviewed upload

Archive: bsd-m6-scaffolding-v0.3.2.zip

Top-level tranche: bsd-m6-scaffolding-v0.3.2/

Key contents:

• README.md
• AGENTS.md
• PROGRAM_LOG.md
• HANDOFF_VERIFICATION.md
• RELEASE_NOTES_v0_3_2.md
• Makefile
• pyproject.toml
• requirements.txt
• .github/workflows/validate.yml
• scripts/smoke_test.py
• tests/test_m6_targets.py
• m6/models/m6_v0_6_models.py
• m6/scripts/m6_0_freeze_v0_5.py
• data/v0.5/*
• reports/v0.5/bsd_dataset_v0_5_validation.json
• docs/specs/*
• docs/audit/*
• docs/runbooks/M6_0_FIRST_ACTION_RUNBOOK.md
• INTEGRITY.sha256

Local verification already performed

The uploaded archive was extracted and tested locally before repo sync planning.

Smoke + syntax

python3 scripts/smoke_test.py passed all stages:

• canonical inputs exist
• dataset wrapper/counts verified
• audit correction has 313 and 353
• all four M6 target P1 points verified
• M5.1 false positives in P1 torsion orbit
• target row state verified
• rank-2 unconditional = [41, 137, 761]
• rank-1 unconditional = 14 primes

python3 -m py_compile ... passed.

Pytest

pytest -q tests/test_m6_targets.py result:

66 passed in 0.26s

M6.0 freeze

python3 -m m6.scripts.m6_0_freeze_v0_5 passed and emitted:

• reports/v0.6/m6.0/MANIFEST_v0_5.sha256
• reports/v0.6/m6.0/v0_5_ingest_report.json
• reports/v0.6/m6.0/v0_5_claim_manifest.md
• reports/v0.6/m6.0/.completed

Sync plan

1. Treat SocioProphet/bsd-proof-program as authoritative.
2. Do not use SourceOS-Linux/bsd-proof-program for this lane except as a historical/duplicate shell if needed.
3. Import the uploaded archive contents into a branch, preserving paths exactly.
4. Keep generated M6.0 freeze outputs out of the initial committed baseline unless explicitly choosing to commit a post-freeze state. The uploaded INTEGRITY.sha256 is the handoff integrity baseline; generated reports/v0.6/m6.0/* should normally be produced by CI/runtime, not precommitted.
5. Preserve binary PDFs and data artifacts from the upload. The GitHub connector can create UTF-8 text files directly, but binary/PDF files require a normal git push from a local checkout or another binary-capable path.
6. Open a PR with the full file sync.
7. CI must run:
   • make smoke
   • make syntax
   • make test
   • optional make freeze if the PR intentionally validates M6.0 in CI.
8. Do not begin M6.1 until the PR is merged and validation is observed.

Claim boundary

This sync is scaffolding and baseline capture only. It adds no new mathematics and performs no M6 descent computation. M6.3 onward remains out of scope until external PARI/Cremona/Magma execution is available.

Acceptance criteria

• All archive files are present in SocioProphet/bsd-proof-program with paths preserved.
• README clearly identifies this repo as the authoritative BSD Proof Program repository.
• Smoke test passes in CI or local reproducible run.
• Pytest passes in CI or local reproducible run.
• M6.0 freeze can be executed and emits the expected manifest artifacts.
• No accidental v0.6 promotion outputs are committed unless intentionally marked as generated post-freeze artifacts.

[mdheller]

GitOps control lane completed.

PR #2 has been merged into main:

• README.md now marks SocioProphet/bsd-proof-program as the authoritative BSD Program repo.
• IMPORT_STATUS.md records the uploaded v0.3.2 archive hash, local validation results, required final file set, and claim boundary.
• LOCAL_SYNC_COMMANDS.md records the exact binary-capable local import commands for flattening the archive into repo root and running validation.

Merged commit: 5ffeaeb4ea2749db3ec8a2b559a3fbd8b79a019e.

Remaining blocker for closing this issue: full path-preserving archive import of the binary/PDF/large-data contents still requires a binary-capable git push or equivalent file-upload path. The current connector lane completed the control import, but cannot directly push local /mnt/data binary bytes into GitHub repository files.

Claim boundary remains unchanged: no M6 descent computation, no v0.6 promotion, no new mathematical claim.

[mdheller]

Captured the newly uploaded BSD Program Lane v0.2.1 L1 registry tranche.

Opened PR #3: Capture BSD Program Lane v0.2.1 L1 registry tranche.

Branch:

capture-bsd-v0.2.1-l1-registry

Added:

reports/v0.2.1/BSD_Program_Lane_v0_2_1_CAPTURE.md
reports/v0.2.1/ARTIFACTS.sha256

Hash-locked uploaded artifacts:

BSD_Program_Lane_v0_2_1.pdf      9a058d3f464654fee3e49c00ce89b23adf0ec90680975d980440ae522f414896
bsd_registry_v021_stats.json     4cc847a7122c60f6e0e5237d43c03e4c1040efb5fdedc5eafda18e1d27bf57ef
bsd_registry_v021.csv            5cc476c1c1d6649858fc0b0a0de5433ee82df47f1dc672039ecd56e296a4346c
bsd_registry_v021.json           afe0f920625b882a36bf35d5a1490d6b24dc557484a4f860ac03ca9aba5324f4

Captured tranche facts:

N_0 = 1000
total rows = 1000
squarefree rows = 608
non-squarefree rows = 392
L_nonzero = 432
L_zero = 568
epsilon +1 / -1 = 503 / 497
corrected C5 pass = 1000 / 1000
rank >= 2 squarefree candidates = 53

Boundary: this is a capture/control PR, not BSD certification and not v0.2.2 execution. Native storage of the PDF/CSV/full JSON remains pending on a binary-capable import lane; identity is preserved by the SHA lockfile and capture manifest.