Repository navigation
Reset phase 1: remove committed evidence and release ceremony, add a small CI - #142
Merged
Merged
Conversation
Prepares for deleting docs/helix/04-build/evidence from HEAD (it stays in git history): - core-ideals tests: drop the hash-of-proof loops that read metamodel-authority/history/manifest.json; keep the behaviour assertions. - core-ideals conformance tests/scripts: remove the evidence-gate checks (verify*Evidence) and keep the round-trip behaviour tests; delete key-evidence, relationship-evidence, relationship-gate-refresh and the evidence-only tests (key-evidence, facets-evidence). - tests/metamodel/current-api-corrections: read its 3 JSON cases from fixtures/metamodel/api-corrections/ (copied from the evidence tree). - python/umf_access tests: copy the 4 small JSON inputs they read to python/umf_access/tests/fixtures/; delete test_refactor_regeneration.py. - delete tests/traceability, tests/qualification and 7 tests/security files that only check evidence. - browser/conformance scripts write their output to out/ instead of the evidence tree; reference build and actions-docs stop reading evidence. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…tests Removes process machinery that proves or qualifies evidence rather than testing the software (everything stays in git history): - 30 of 31 workflows (publish/dispatch/qualification/inspector/sagas/ microsite/lakeview/... ); pr-fast.yml is replaced in a later commit. - tools/security (356 files, a Weft protocol tool tree no product code imports) and the ~40 tests that only exercised it. - tools/*inspector*, qualify_*, probe_*, intake_*, temporal_*, verify_*, prepare_*_release.py; scripts/publish_*, dispatch_*, verify[-_]*, qualify-*, check-*-boundaries.*, uuid/qualify*, relationship-integrated-*, refresh-core-checks and their tests; docker/core-replay; .githooks. - python tests of the coordinated-release/artifact-custody machinery and the receipt/hash halves of test_distribution_artifact.py; tests/rust-migration gate0/review-controls files. - scripts/rust-migration/r4/sync_codegen_resources.py moves to scripts/sync-codegen-resources.py (a real generator used by the codegen build hook). Kept although the plan listed them, because product code or kept tests read them: scripts/check-core-authority.ts (SDK packaging), scripts/saga-portable/ custody.ts, scripts/generated-page-seals.ts, scripts/uuid/qualification- inventory.ts, and scripts/rust-migration/** (SDK packaging, node/wasm tests). Co-Authored-By: Claude Fable 5.2 <[email protected]>
Deletes the process evidence tree and generated outputs that were tracked in git (all of it remains in git history; no history is rewritten): - docs/helix/04-build/evidence/** 34,606 files, 4,256 MB - docs/helix/05-deploy/microsite/dist/** 5,214 files, 111 MB (built site) - docs/helix/05-deploy/evidence/**, microsite-evidence.json, schema-explorer-evidence.json, assets/truss-browser, assets/weft-mutation - .github/release-admissions, qualification-inputs, .innsigle The 7 hand-authored site files that lived inside dist/ (index.html, docs.html, ecosystem.html, demo.html, style.css, logo.svg, og-explorer.png) move to site/ unchanged. Generated site output is now gitignored, as are out/, *.whl, *.tgz and *.zip (fixture zips excepted); .gitattributes drops the rules for the deleted paths. Tracked tree: 70,858 files / ~4.9 GB -> 30,301 files / ~492 MB. Co-Authored-By: Claude Fable 5.2 <[email protected]>
ci.yml (Linux ubuntu-24.04 only) runs on push to main and pull requests: size-guard, native-addon (Node addon, opt-level 2), rust (cargo test of the 8 workspace crates), ts (4 shards of bun test files in parallel, plus the coupled-release-version check) and python (3.11 and 3.14: ruff plus pytest for umf-core, umf-codegen, umf-access and the generator tests). A nightly job (schedule or manual dispatch) builds everything with `bun run test:prepare`, runs every Bun test file, the browser suites, the SDK package test and the whole Rust workspace. - scripts/run-tests.ts: --jobs, --keep-going, --exclude-file, --shard; no stop-on-first-failure, no per-file log hashing. - package.json: test:fast; packageManager [email protected] (matches CI). - scripts/slow-tests.txt: files that need build output beyond the Node addon (WASM, SDK, built reference site, action prerequisites) or minutes. - scripts/check-repo-size.py + .github/size-allowlist.txt: fail if a tracked file over 1 MiB is not allowlisted, if anything is tracked under the evidence/ built-site/ out/ paths, or if the tree exceeds 600 MiB. Co-Authored-By: Claude Fable 5.2 <[email protected]>
Python - ruff gate limited to real errors (syntax, undefined names); 135 style findings existed before and are not gated. - python/hatch_build.py: add the three spec files that Rust include_str! reads (arrow flatbuffer inventory, arrow-flatbuffer package, parquet- relationships package) to the sdist closure; test_python_sdist caught that an sdist build would miss them. - python/tests: move the two inspector resource fixtures out of the deleted tests/qualification tree; tools/tests drop the stale hash pins. - python/tests/known_failures.txt + conftest.py: 14 native retained-codegen and parquet-capture tests that fail on current main are skipped with a recorded reason (see the PR, Known failures). - python/umf_access/tests: delete 4 tests that only check evidence packets or source hash pins; make test_rust_target_pin independent of the Python 3.14 error-message wording; conftest.py skips the tests that need the generated `commerce`/`search_docs` clients or the downstream `weft`. - ci: install psycopg and cryptography for the umf-access tests. Rust - umf-cli codegen_cli: assert the CLI reports its own package version, not a hardcoded 0.1.0; cargo test runs with --no-fail-fast. Bun - core-scalar-types-for-version test read its fixture from the wrong directory; delete uuid-conformance.test.ts (it only verified an evidence fingerprint closure). - ts job: 12 shards x 3 jobs, python3.11, protoc and Chromium installed, 120 s default per-test timeout; files that need a build, a database service or run for minutes move to the nightly job (slow-tests.txt). Co-Authored-By: Claude Fable 5.2 <[email protected]>
… dirs, env-bound umf-access tests - python/tests/test_python_sdist: the include_str! authority check ignored pyproject's sdist force-include list (which already covers the three spec files), so it was stale; read the list from pyproject. The hatch_build.py edit in the previous commit was wrong and is reverted here. - tools/tests/test_codegen_resource_literals: drop the stale hash pins (this edit was left out of the previous commit). - umf_access test_catalog_writer: stop hardcoding the macOS /private/tmp. - umf_access conftest: also skip the tests that need the pgserver local PostgreSQL profile or bun. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…mp elsewhere Co-Authored-By: Claude Fable 5.2 <[email protected]>
…ound Bun files to nightly - rust: cargo test of umf-core alone ran over 30 minutes; use nextest in 4 partitions. - slow-tests.txt: add the files that needed protoc 36.2, the Python oracle venv, a Rust toolchain, or exceeded their in-test timeouts in the first Linux runs. The nightly job installs protoc 36.2. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…nv-bound umf-access tests - ts: 16 shards x 2 jobs; seven more borderline-timeout files move to nightly. - rust: skip umf-core-wire rdf_parity production_rdf_wire_matches_frozen_ predecessor_outcomes (blank node counter g_2 vs frozen g_1); recorded as a known failure. - umf_access conftest: test_generation_authority_physical_binding needs the local PostgreSQL profile, which is unsupported on Linux. Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
…rse-projection) Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
…ase1 Evidence, receipts, built-site output and ceremony workflows stay deleted. Main's product code, tests and fixtures win. Test imports follow main's src/index-node-v4 entry point; the evidence-hash tails stay cut; browser scripts keep writing under out/. Co-Authored-By: Claude Fable 5.2 <[email protected]>
crates/umf-cli/tests/codegen_cli.rs (version assertion) and package.json (packageManager) are hashed into spec/metamodel/generated/manifest.json. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…ve; hand the addon over via cache; pytest-xdist Co-Authored-By: Claude Fable 5.2 <[email protected]>
The merged main commit truncated this 345 KB fixture to an empty file. The Python inspection tests and the retained-codegen oracle hash pin read it; restore the content from the parent of that commit. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…ry path exists Co-Authored-By: Claude Fable 5.2 <[email protected]>
…merge; run-tests --only-file and repeatable --exclude-file known-failures.txt: assertion/error failures, skipped in the PR job and run informationally nightly. slow-tests.txt: timeouts, WASM- and PostgreSQL-fixture-bound files. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…s a hung file after UMF_FILE_TIMEOUT_MS Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Main added release admissions, publication scripts, microsite evidence and a rebuilt dist/ for 0.10.11; all of it stays deleted. No product, test or fixture file changed. Co-Authored-By: Claude Fable 5.2 <[email protected]>
…le cap) to nightly; quarantine five more failing files Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
… into reset/phase1 Main's pr-fast.yml, access-package-identity.yml and the access boundary lint stay deleted. The new generated-access-executor workflow is folded into ci.yml (python job: install the package so umf_access's generated-binding tests import, and run its stdlib unit tests). Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Phase 1 of the stack reset for UMF: take process evidence, built output and release ceremony out of HEAD, keep the software and its real tests, and leave one small CI that tests software. Everything removed stays in git history; no history is rewritten and the evidence archive release (plan WP0) is not part of this PR.
Covers plan work packages WP2, WP3, WP1 and WP4, as ordered commits on this branch. Main has been merged into the branch three times (see "Merges of main").
What was removed
docs/helix/04-build/evidence/**docs/helix/05-deploy/microsite/dist/**(committed built site) andmicrosite/evidence,schema-explorer-evidence.json,assets/{truss-browser,weft-mutation}tools/security/(Weft protocol tool tree no product code imports).innsigle,.github/release-admissions,qualification-inputs,docker/core-replay,.githooksTracked tree: 70,858 files / ~4.9 GB -> 30,265 files / 492 MiB (size guard budget 600 MiB). Clone size is unchanged (history is untouched; the rewrite is plan option (b), an owner decision).
Merges of main (CONFLICTING -> MERGEABLE)
Three merge commits, no rebase, no force-push.
09bbf7c44"Complete the Rust port and prepare UMF 0.10.11" (Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143): 1,924 files. It moves the product core to Rust (Lakeview projection, bulk actions and the remaining SDK semantics inumf-core/umf-core-wire; the TypeScript tree becomes host wrappers over the native Node addon or browser WASM viasrc/index-node-v4.ts/index-browser-v4.ts), deletes ~230 TypeScript engine files, and sets Rust, SDK, Python Core and Codegen to 0.10.11. It added no workflow or version-consistency check and was merged with CI skipped.tools/security/*modified by Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143 was re-checked withgit grepand a missing-import scan over the whole tree: nothing outsidedocs/and inert path-string lists imports it, so it stays deleted; same for thecheck-*-boundariesscripts,uuid/{composition-gates,verify-returned},security-identity-transport-spike, the boundary tests,tools/qualify_python_release_wheel.py,microsite.yml,pypi.yml).src/index-node-v4), with the PR's evidence cuts re-applied: the unusedcreateHashimport dropped in 8tests/core-ideals/*files;tests/metamodel/current-api-corrections.test.tstakes main's version (it no longer readsbefore.json) repointed tofixtures/metamodel/api-corrections/; browser scripts take main's version with their output paths kept underout/(scripts/reference/browser.ts,compilation-browser.ts);scripts/reference/build.tstakes main's version (addsbuild-reference-wasm.ts) with the evidence-inventory inputs and the deleted workflow/Innsigle inputs removed again;package.jsontakes main'simportsmap and keepspackageManager: [email protected].tests/binding/raw-profiles-receipts.tsholds inline expected values, not an evidence read).tests/rust-core/fixtures/access-inspection/cases.json. Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143 committed this 345 KB fixture as an empty file;python/tests/test_access_inspection_public.pyand the retained-codegen oracle hash pin read it (13 failures + 1 collection error until restored). Content restored from the parent of Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143. (This looks like an accident in Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143.)spec/metamodel/generated/manifest.jsonregenerated: it hashespackage.jsonandcrates/umf-cli/tests/codegen_cli.rs, both changed on this branch.bff1ed472..302b75e46(0.10.11 release records, Deploy the verified UMF 0.10.11 microsite #146 and Publish the verified UMF 0.10.11 Python archives #147): release admissions,publish_local_pypi_01011.py,verify_microsite_release_manifest.py, microsite evidence and a rebuiltdist/(4,640 files, no product, test or fixture change). All removed again;deploy-local-microsite.yml,publish-codegen-pypi.yml,publish-pypi.yml(modified on main, deleted here) stay deleted;.gitattributeskeeps main's file minus themicrosite/distrules.4cb238a5e(Add the generated access executor used by prepared PostgreSQL reads #144, Admit prepared PostgreSQL reads and receipt-backed writes #145: generated Access executor and PostgreSQL adapters): new product code (python/umf_access/**generated-binding modules and tests, new packagepython/umf_access_generated_executorwith 51 stdlib unit tests, plus accessor-refusal test fixestests/core/admission-refusal.ts). Kept in full. Its changedpr-fast.yml(now downloads the released 0.10.11 SDK to get the Node addon and WASM package, checksum-pinned),access-package-identity.ymlandcheck-access-python-boundaries.pystay deleted. Its newgenerated-access-executor.yml(ran onubuntu-latest, one stdlibunitteststep) is folded intoci.yml: the python job installs the package (--no-deps, soumf_access's generated-binding tests import instead of failing collection) and runs its unit tests. Six fixtures there are over 1 MiB (largest 1.3 MiB), allowlisted in.github/size-allowlist.txt.Not touched: versions (main already has 0.10.11 everywhere and the
umf-v0.10.11tag exists on09bbf7c44), release/pages workflows (none are added here).What was moved or kept, and why
microsite/dist/->site/unchanged. Not wired to any workflow yet.fixtures/metamodel/api-corrections/(main's test now reads two of them), 4 topython/umf_access/tests/fixtures/, 2 topython/tests/fixtures/.scripts/rust-migration/r4/sync_codegen_resources.py->scripts/sync-codegen-resources.py.scripts/check-core-authority.ts(SDK packaging) and its test,scripts/saga-portable/custody.ts,scripts/generated-page-seals.ts,scripts/uuid/qualification-inventory.ts,scripts/rust-migration/**,scripts/reference/check-boundaries.ts.tests/core-ideals/*were cut out (hash-of-proof loops), behaviour assertions kept. Evidence-only tests deleted (key-evidence,facets-evidence,uuid-conformance,tests/traceability,tests/qualification, 4 umf-access packet/hash-pin tests).0.1.0in a Rust CLI test; wrong fixture path incore-scalar-types-for-version; Python 3.14 wording intest_rust_target_pin; macOS-only/private/tmpintest_catalog_writer; sdist include-authority test; stale hash pins intools/tests/test_codegen_resource_literals.py.CI (
.github/workflows/ci.yml, Linuxubuntu-24.04only)Push to main + PRs:
size-guard;native-addon(Node addon at opt-level 2, handed to the Bun shards throughactions/cachekeyed on the Rust sources, not as an artifact: 16-24 shards downloading one artifact were flaky and an unchanged addon is no longer rebuilt);rust-build(onecargo nextest archiveof the 8 crates) +rust(8 nextest partitions run from the archive, extracted into./targetbecauseumf-clitests bake in the binary path);ts(24 shards x 2 jobs ofscripts/run-tests.ts);python(3.11 and 3.14, pytest-xdist-n 4 --dist loadfile, ruff for real errors).nightly(schedule or manual dispatch):test:prepare, typecheck, reference site build, every Bun file except the quarantined ones, the quarantined ones informationally (continue-on-error), browser suites, SDK package test,cargo test --workspace.scripts/run-tests.tsoptions:--jobs,--keep-going,--exclude-file(repeatable),--only-file,--shard; each file is killed afterUMF_FILE_TIMEOUT_MS(default 10 min, a hung file used to stall a shard for 30 min) and prints its wall time.scripts/check-repo-size.py+.github/size-allowlist.txtguard tree size.Acceptance results
43125845237onc4b89bf2d(all three merges): all 37 jobs succeeded (nightly skipped by design). Wall time 29 min start to finish, mostly the org's runner queue (37 jobs). Longest jobs:tsshards 12.8-16.1 min,python10-13 min,rustpartitions 2.5-7.4 min plusrust-build6.2 min. An earlier run on the first two merges was also fully green. So Rust and Python are now inside the ~15 min target; the Bun shards are at or just over it.umf_access_generated_executor.-n 4) 1,530 passed / 13 failed / 4 errors before restoringcases.json; after restoring it,test_access_inspection_public.py+test_retained_codegen_native.py47 passed / 9 skipped;ruffreal-error rules pass;tests/release10 pass;check-repo-sizepass; one nextest partition from a locally built archive 384 passed; one Bun shard (16/16) 36 passed, 1 failed (now quarantined). A full local Bun run was not completed (about 25 files in 17 min on the loaded machine; per-test timeouts fire under that load). Those local runs reproduce several of the quarantined failures (e.g.tests/core/field-ideals,tests/catalog-resource-profile,tests/security/evaluate) with Bun 1.4.2 as well as 1.4.3, so they are not caused by this PR or by the Bun pin.bun scripts/metamodel/build.ts --check: stale on the merge result until the manifest was regenerated (2 hashes); passes after.nightlyhas never completed. A dispatch before this merge failed atbun run test:preparewithMETAMODEL_STALE_OUTPUT(the stale manifest, now fixed); nothing after that step has run. Not dispatched again after this merge to avoid a 2.5 h job on a slow queue.Known failures (skipped or moved, each with a recorded reason)
scripts/known-failures.txt(skipped in PR CI, run informationally in nightly; the reason beside each entry is its first error line, not a diagnosis). They fail with assertion/error output on Linux after Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143's Rust port; none depends on this PR (the sources and tests are main's). Typical errors:AdmissionError: Accessor properties are not invoked during admission(8+ files), AvroSEMANTICS_UNCHECKED/AVRO_UNRESOLVED_NAME,Source structural limit exceeded,Parser response does not match the ordered prepared CHECK requests,src/domain-packs/loader.tsdeclaringgenerateDomainPackLoaderSchemawithout exporting it, uuid/bit128 association refusals. This is the main finding of the merge: Complete the Rust port and prepare UMF 0.10.11 [skip ci] #143 was merged with CI skipped and about 18% of the Bun files fail on a clean Linux run.scripts/slow-tests.txt(nightly only): need the WASM package,protoc36.2, an owned PostgreSQL fixture, or take 90 s to several minutes (or time out their 20-120 s in-test limits) on a 4-vCPU runner, plus files that hung in CI. Not yet verified in nightly.python/tests/known_failures.txt: 11 native retained-constructor tests ("Host work budget exceeded"), 2 hash-pinned resource tests,test_rust_parquet_capture(four float levels where three ints are expected). The other 13 retained-codegen failures seen right after the merge were the truncated fixture, now fixed.python/umf_access/tests/conftest.py): 20 files need generated client packages or the downstreamweft; 6 more need the pgserver profile orbun; 3 cases needcommerce.umf-core-wirerdf_parity::production_rdf_wire_matches_frozen_predecessor_outcomessees blank nodeg_2where the frozen outcome hasg_1. Skipped in the nextest filter.bun run typecheckfails onsrc/index-browser-v4.tsunless the WASM package has been built; it runs in nightly aftertest:prepare.tools/securitytree (they only exercised that tool), per the plan.Not in this PR
WP0 archive release, WP5 version bump /
set-version.py(main already carries 0.10.11 and a publishedumf-v0.10.11tag), WP6 pages and the Innsigle seal question, WP7 docs trim / README / AGENTS.md, WP8 release.yml, any macOS runner, branch or tag deletions, history rewrite. The 7 orphaned workflow registrations still needgh workflow disableby an owner. Branch protection required checks are an owner step (jobs:size-guard,native-addon,rust-build,rust (1..8),ts (1..24),python (3.11, 3.14)).🤖 Generated with Claude Code