Landmarks: prepare local Swiss capture for expanded categories

[timohueser]

Parent: #2026. Tracker: #1978.

Prepare the local source and content needed for the ten new landmark categories. The category code is merged in #2050. This task needs neither the board nor an owner action.

Scope:

• Use a clean current develop checkout and its pinned Swiss boundary and OSM extract. Record exact source, compiler, policy, and input identities.
• Run the documented OSM-first capture into a new local directory. Preserve all older captures. Use the existing rate limits, maxlag, and Retry-After handling. Do not publish the raw archive or register it as a fixture.
• Compile the finished capture twice offline into separate empty directories. Compare all outputs. Distinguish source failures, unresolved identities, acquisition counts, and usable content counts. Do not claim incomplete coverage as a zero count.
• Report per-category usable article/photo counts and identify actual hut and tower content for later visual acceptance. Compare compiled sizes with the applicable resource policy. Do not relax a resource limit.
• A separate Sol agent reviews the provenance, completeness, output comparison, and reported limits. Record the evidence in this issue; do not add an evidence or notes file to the repository.

Publication, fixture re-pinning, dependent map rebuilds, and actual-content visual acceptance stay in #2026. Do not use production credentials, publish to R2, modify the installed map/card, or touch hardware. If the existing tools fail, report a bounded defect before expanding this task into source changes.

Acceptance: a complete locally retained capture plus reproducible compiled content, with reviewed hashes and counts; or a precise external blocker with resumable work preserved. No claim closes the parent content refresh.

Requirements: none

[timohueser]

Bounded overnight capture record

The immutable preflight review passed. The run used a clean origin/develop checkout at bd279d4ffb913584ed91ea028ae93b49885c4b09.

Inputs:

• Swiss PBF: e6ae53a3cfeb8fbefbab291073e61f0906b03576e773b7403ab9b6d6232a8e88
• Swiss boundary: 1b36c21d52a4419d410893ea41dd522d36238ada0b253c7fe78b81d2ef1edd5b
• Category policy: ce6aad265cf8fee09939f91eafd882c35cb59572de446fa671c449f677b1701c
• OSM candidate file: 8270fe6b13177e86cec25e18df1219d357a9f6ed44aec264aa8ad12f80a0d91c
• Candidate identities: 37,122. Rejected OSM tags: 11.
• Pinned compiler: 581277bc115991e9f33c44f0ff11e202617dbb715b374f8270a3cdc5ab74745e
• Compiler content-policy/input digest: 1ecc7adfbcdfe518ca7c752752948af57e62b84569d752a52f41b044063baa1a
• Unique production-selected candidates before asset usability: 2,031.
• Recipe: OSM-first, no sweep, en, de, fr, and es.

The capture ran from 2026-09-22T23:13:56Z to 2026-09-23T05:50:42Z. It completed 176 of 2,031 selected place files. It wrote 18,935 request outcomes: 18,918 successful outcomes and 17 transport errors. The errors are 7 read timeouts and 10 connection resets. They affect 15 image or metadata requests and 2 article requests. They remain first-pass outcomes. No retry pass ran, so attempts/ is empty.

The current manifest is the checkpoint written before selected-asset acquisition. It records:

• entity_coverage_complete=true
• 37,116 acquired entities
• 6 unresolved identities
• query_coverage_complete=true
• no sweep queries
• no missing classes
• asset_phase_complete=false
• country_complete=false

The manifest still reports zero request failures because the tool did not reach its next manifest write. The 17 immutable outcome files are the current failure record. Do not read them as zero failures.

The process received SIGINT at the bounded overnight stop. Python exited with KeyboardInterrupt, and no capture or compiler process remains. The latest completed request is 2026-09-23T05:50:42.824723Z. The retained capture has 38,036 files and 681,611,045 logical bytes. Its manifest.json SHA-256 is c178f3741e7b34580a52bf32ddc198f9235746c2211886cb4b959c8db84a70ca. The 8 GiB free-space stop threshold stayed active. Free space was 39,244,748 KiB at the stop.

Retained paths:

• Capture: /Users/timo/.cache/openbikecomputer/bake/landmarks/switzerland-2095-bd279d4
• Pinned compiler: /Users/timo/.cache/openbikecomputer/bake/toolchains/2095-bd279d4/obc-bake
• Candidate input: /Users/timo/.cache/openbikecomputer/bake/runs/2095-bd279d4/switzerland-candidates.json
• Clean source checkout: /Users/timo/Documents/OSM-agents/codex-switzerland-capture-2095
• Older locked capture: /Users/timo/Documents/OSM-agents/ra08-source-capture/.artifacts/country-source-switzerland

These are the exact arguments of the stopped first pass. Do not resume this capture until #2106 resolves the category-pagination completeness defect and the owner selects a compatible resume or fresh-run path:

cd /Users/timo/Documents/OSM-agents/codex-switzerland-capture-2095
python3 tools/landmark_capture.py \
  --boundary /Users/timo/.cache/openbikecomputer/fixtures/by-id/assistant-osm/switzerland-boundary.geojson \
  --candidates /Users/timo/.cache/openbikecomputer/bake/runs/2095-bd279d4/switzerland-candidates.json \
  --policy host/obc-pack/src/landmarks/policy.json \
  --select-with /Users/timo/.cache/openbikecomputer/bake/toolchains/2095-bd279d4/obc-bake \
  --out /Users/timo/.cache/openbikecomputer/bake/landmarks/switzerland-2095-bd279d4

If the owner later selects a compatible resume, run one --retry-failed pass only after the complete first pass exits. Do not start the retry while the first pass is incomplete.

Correction: the wall-clock duration does not support the earlier multi-day estimate. A read-only check of pmset -g log parsed the recorded duration of each Sleep entry that overlaps 2026-09-22T23:13:56Z through 2026-09-23T05:50:42Z. The 21 clipped sleep intervals total 17,968 seconds (4:59:28) of the 23,806-second wall interval (6:36:46). Only 5,838 seconds (1:37:18) are outside recorded Sleep intervals, including DarkWake periods. The long request-start gaps align with those sleep intervals. There is no reliable awake-time completion estimate from this partial run.

The metadata request counts remain valid. The Commons category pagination defect also remains valid: one captured category returned 500 members and an unconsumed cmcontinue token. #2106 owns that fix and the completeness rule. No compile ran because the first pass is incomplete. This does not pass acceptance, close this issue, or close the parent content refresh.

Requirements: none

Pagination-safe resume after #2108

PR #2108 merged after exact-head review and green CI. The resume uses exact merged source
a926b7735573b8175ab1137812349f4a580bdb1e. No raw record or manifest was edited by hand.

New immutable identities:

• Capture tool SHA-256: febb24858b49a14f9182fcd8a6494d209c28ee71fea0a067586077c7afd5db47.
• Pinned compiler: /Users/timo/.cache/openbikecomputer/bake/toolchains/2095-a926b773/obc-bake.
• Compiler SHA-256: 263c67057a5d9be792fa7677746f75dc28247e35df620eac546c11476cea27d2.
• Compiler content-policy/input digest: 38b394550ecb0c9e38223d466ddb613125ee3cd8cba9faa2ffabb7ced63ff559.
• Selection document SHA-256 after the schema upgrade: 32b954fed61a41da87c1fb657f239efabbd085a50a7fb9992c8f7334ed1725b3.

The boundary, candidate, category-policy and language hashes still equal the first-pass values above.
The old source, compiler, selection hash and raw outcomes remain part of the provenance chain. The old
compiler is not reused because the corrected capture writes manifest schema 2 before production
selection.

The initial pass resumed at 2026-09-23T07:52:50Z with this command and without
--retry-failed:

cd /Users/timo/Documents/OSM-agents/codex-switzerland-capture-2095
/usr/bin/caffeinate -i -- /opt/homebrew/bin/python3 tools/landmark_capture.py \
  --boundary /Users/timo/.cache/openbikecomputer/fixtures/by-id/assistant-osm/switzerland-boundary.geojson \
  --candidates /Users/timo/.cache/openbikecomputer/bake/runs/2095-bd279d4/switzerland-candidates.json \
  --policy host/obc-pack/src/landmarks/policy.json \
  --select-with /Users/timo/.cache/openbikecomputer/bake/toolchains/2095-a926b773/obc-bake \
  --out /Users/timo/.cache/openbikecomputer/bake/landmarks/switzerland-2095-bd279d4

The tool verified and reused the retained request records, wrote schema 2 atomically, and selected the
same 2,031 production candidates. The first schema-2 checkpoint reports the 17 retained transport
failures instead of the stale zero in the interrupted schema-1 checkpoint. Its SHA-256 is
8dbcffb1d3812392383fb563fe64d10eedd62741ca1c1ad61f8d71d1a2d33d08. Acquisition is live;
the last observed source progress is 22 of 2,031 place files. This is a progress fact, not an ETA.

A process-scoped caffeinate -i assertion prevents idle sleep only while this command runs. A
controller checks the existing 8 GiB free-space floor every 60 seconds, stops the process group if
the floor is crossed, and makes the retained capture read-only on exit. The initial free space was
18,255,511,552 bytes. Controller PID 93450 owns acquisition process group 93453. Live status is
/tmp/obc-2095-a926b773-resume-status.json; output is
/tmp/obc-2095-a926b773-resume.log. No publication or content compile has started.

Resume paused at the disk floor

The controller stopped the initial resume pass when free space crossed its 8 GiB floor. At
2026-09-23T08:14:51Z, it measured 7,532,466,176 free bytes against the
8,589,934,592-byte floor and sent SIGINT to the acquisition process group. Python exited with
KeyboardInterrupt and code -2. The controller finished at 2026-09-23T08:15:11Z and made the
whole retained capture read-only. The controller, capture, caffeinate, and compiler processes are
all absent.

Closed controller artifacts:

• Output log SHA-256: c30091b82eec83e3f65d659b4a5171009d964eb0e199cf834909eefe8836fab5.
• Status SHA-256: f30c52b637f0bcef35837a6ece4f875b597aa737fd3cae15d59529f99b5a1d26.
• Controller SHA-256: e1073be030b3198aa91c3d01afb70dfb80147de4114fd7d998a65b7e8b698ed9.

The last emitted progress record is place 236 of 2,031, Q685650. Atomic place files form a
contiguous prefix of 239 selected identities through Q686516; the next identity, Q686528, has
no place file. The outcome directory now has 23,315 immutable outcomes: 23,298 successful and the
same 17 first-pass transport failures. The failures remain 15 image/article-metadata paths and two
article paths: ten connection resets and seven read timeouts. No retry ran and attempts/ remains
empty.

The retained completed place files contain 227 complete category records across 228 pinned pages.
One category has a second continuation page. No completed record is marked with incomplete category
coverage. These are resumable filesystem facts, not country-completeness evidence.

The manifest is still the initial schema-2 checkpoint written before the asset loop. It has SHA-256
8dbcffb1d3812392383fb563fe64d10eedd62741ca1c1ad61f8d71d1a2d33d08, 37,116 entity
place skeletons and only the 18,935 outcomes present before this resume. It correctly says
asset_phase_complete=false and country_complete=false. Its
category_coverage_complete=true is vacuous at that pre-asset checkpoint. It does not yet include
the 239 place files or 4,380 new successful outcomes, so do not use it as an asset census or a
complete source manifest.

The retained capture uses 850,004 KiB on disk. Later free-space reclamation raised available space,
but the run stays paused until sufficient headroom is deliberately restored. Do not resume, retry,
compile, or publish from this state. All raw data, the pinned compiler, the source checkout, and the
closed log/status/controller artifacts remain preserved.

[timohueser]

Raw acquisition resumes after firmware build cleanup restores disk space. Source remains a926b7735573b8175ab1137812349f4a580bdb1e, with the same pinned compiler, input hashes, policy, and 2,031-place selection. Preflight verifies the retained 239 place files and 23,315 outcomes: 23,298 successful outcomes and the same 17 older transport failures. There is no retry pass or manual manifest change.

The new controller is /tmp/obc-2095-a926b773-resume2-controller.py, SHA-256 90be459d5cac5893ef9f94aba554ea41c8ca12447dc62be63cf001b194ef6f88. Live status is /tmp/obc-2095-a926b773-resume2-status.json; the acquisition log is /tmp/obc-2095-a926b773-resume2.log. It uses process-scoped sleep prevention, checks the 8 GiB free-space floor every 60 seconds, stops acquisition if the floor is breached, and relocks the capture on exit.

At startup, the capture reuses the retained entities and runs selection with the pinned compiler. This is acquisition progress, not country completeness. No country content compilation or publication is claimed.

[timohueser]

Overnight continuation: retained first pass and compiler profile transition

The old acquisition controller disappeared while its capture and compiler children continued. A separate guard restored the 8 GiB disk floor and process-scoped shutdown checks. The old process group is now absent. The guard confirms recursive read-only retention at 2026-09-23T21:41:40.067337Z.

The stopped first pass retains 2,031 place files and 69,208 request outcomes: 69,191 successful outcomes and the same 17 transport errors. attempts/ is empty. The manifest SHA-256 is 3e50e0dfafee4e20056691b05a480d118d57b7fea4ac51f5d6635412abab6d29. This is an interrupted initial pass. Intermediate article/photo counts and manifest asset flags are not final country-completeness evidence.

The compiler was a development build. Merged PR #2160 corrects the capture recipe to use an optimized build. The retained run keeps source a926b7735573b8175ab1137812349f4a580bdb1e, the same lockfile, tool, boundary, candidates, category policy and language inputs. Only the compiler profile changes:

• Retained development compiler SHA-256: 263c67057a5d9be792fa7677746f75dc28247e35df620eac546c11476cea27d2.
• New release compiler: /Users/timo/.cache/openbikecomputer/bake/toolchains/2095-a926b773-release/obc-bake.
• Release compiler SHA-256: 326d9c4de41197fac98cf331c7999e2eef9221b237163b45acb903d28ef65b44.
• Lockfile SHA-256: 1354e374de0626fa9c017e05371be0793c770f49e8f4e6c07ebb84f1fa5bf8c6.

A frozen, captured photo-fallback case for Q176775 produces byte-identical normal and photo-request outputs with both compilers. A separate GPT-5.6 Sol reviewer verified the outputs, compiler and source identities. This is a bounded compatibility check, not the final two full-country compiles. The worker recorded a successful release build and 462 passing obc-pack tests in the session transcript.

The separately reviewed controller completed an offline release-compiler preflight against the stopped manifest. The exact 2,031-candidate order and content-policy digest pass. It preserved the stopped manifest, selection and compiler identities before it unlocked the capture. At 2026-09-23T21:50:37.088604Z, it launched the same initial pass without --retry-failed, as child process group 65077. The controller owns the child session and uses process-scoped sleep prevention, the 8 GiB disk floor, bounded shutdown and recursive relock. Startup free space is 33,735,860,224 bytes.

This is a resumed initial pass, not a completed capture. Runtime selection, final acquisition exit, retry and country completeness still need verification.

Controller SHA-256: 321e54438b24862e2823f6af77f2e85a7bc9004b0529507cb2fa0d40cd533459.

Retained and live paths:

• Controller: /tmp/obc-2095-a926b773-release-controller.py.
• Preflight output: /tmp/obc-2095-a926b773-release-controller.out.
• Acquisition log: /tmp/obc-2095-a926b773-release.log.
• Acquisition status: /tmp/obc-2095-a926b773-release-status.json.
• Transition provenance: /Users/timo/.cache/openbikecomputer/bake/transitions/2095-a926b773-release.

The capture remains local. One retry pass follows only after the initial pass exits. Final completeness, two independent offline outputs, category counts and resource limits still need separate Sol review. Publication and the parent content refresh remain outside this task.

[timohueser]

The initial capture now resumes with the reviewed compiler from #2163. This is still the initial pass. No retry has run.

The previous controller stopped at 00:09:01 UTC. Its complete status confirms that the child process group drained and the capture was locked. The stopped census is 2,031 place files, 69,583 successful outcomes, 17 transport errors, and no retry records. The stopped manifest SHA-256 is 23de557586ac436f4d76f71864fecacbd31c3b9d61d72d4bcb025b211ed93e9c.

The new child started at 00:09:49 UTC. Its source is the reviewed, merged PR head bca69f52f8415a23e392019acc4fac870a6d110e; the binary is built from that head, not the merge commit. Its SHA-256 is f4572ccdcabbc6f4cfc31632bcb2d6a3df217628eaaa1f0492db1d61bf1cfb16. The selection now reports policy 0074c8caede43bef40d985c744ef2ff5124cf0d080009cac94efb9fd55e6c51a and the same ordered 2,031 QIDs. The category, language, boundary, candidate and recipe inputs retain their recorded identities. The 8 GiB floor, process-group drain and lock verification remain active.

A separate GPT-5.6 Sol reviewer checked both parts of the compiler transition:

• The frozen intermediate capture has identical ordinary content under the current pre-optimization compiler and Avoid repeated landmark photo preparation #2163, except the expected policy fingerprint. All 1,317 output paths and all 1,316 RGB files match. All 1,056 full photo requests match in order. All four compiler commands exit successfully.
• Compared with the older a926b773 compiler, merged feat(landmarks): structured, word-wrapped Sources credits #2123 intentionally changes the Sources credit format. The audit accounts for 12 additional usable records, nine additional language variants, two higher-ranked usable photos, and removal of the old display-page field. There are no unexplained content differences. The old-to-current comparison remains recorded as unequal.

These are compatibility checks on a frozen intermediate capture. They do not establish final country completeness or reproducibility. The remaining work is to finish this current-policy request loop, run the single retry pass, and compile the finished capture twice.

The transition provenance is retained at /Users/timo/.cache/openbikecomputer/bake/transitions/2095-bca69f52-resume. It includes the old stopped manifest and selection, runtime status and log, exact source/compiler identities, semantic inventory, compatibility comparison and all compiler result receipts. The separately reviewed launch controller SHA-256 is 96155b381f5a4c3243d33c5e1795fd32a724ca475834850bed41013d45f79902. No archive, fixture or map was published.

[timohueser]

Local preparation is complete. A separate GPT-5.6 Sol agent independently reviewed the final provenance, completeness, two output trees, category counts, resource limits, and hut/tower sources. The review passes. This closes #2095 only. Publication, fixture re-pinning, dependent map rebuilds, and actual-content UI acceptance remain in #2026.

Capture and retry

• The optimized initial pass finishes with 17 transport failures. Exactly one retry resolves all 17. The original failure records remain in attempts/.
• Final coverage is complete for entities, queries, assets and categories. Current outcomes contain 69,647 successful requests and no source failures. No class is missing.
• Source identities: 37,122 explicit OSM-linked candidate identities, 37,116 acquired entities, and six unresolved identities. The unresolved identities are reported separately from transport failures.
• The production selection contains 2,031 ordered QIDs. There are 2,031 selected place capture files and 3,616 acquired photo originals. These are acquisition counts, not usable-content counts.
• Both controllers drain their child process groups and lock the capture. The final recursive writable-file check is zero. No second retry runs.

The reviewed compiler transition preserves the earlier capture and records the intentional #2123 Sources-credit change separately from the #2163 optimization. The final source is the reviewed, merged PR head bca69f52f8415a23e392019acc4fac870a6d110e; the binary is built from that head, not the merge commit.

Offline result

Two fresh normal landmark-content invocations compile the same locked manifest with the same pinned release binary into distinct empty directories. Both exit 0. The first takes 287.228 seconds and the second takes 285.746 seconds. Their actual file sets and bytes match. Each receipt matches its own outputs and log.

• 1,331 files in each output: content.json and 1,330 RGB222 photos.
• Each output totals 81,068,551 bytes: 12,121,351 bytes of content JSON and 68,947,200 raw photo bytes.
• Usable content: 1,453 landmark records and 2,492 language variants. A record count is a distinct usable place, not a language count.
• Tree SHA-256: dc935d6de88b38f887ce920e23d47b62c666e9660875ed2444e90a8d72a3461f.
• Content SHA-256: 3f03f5574b7870cd6da4e9035ae6ed942cc686df2b161ce7b6d464285a65256d.
• The accepted final validator exits 0. It binds content to the exact manifest and boundary bytes, the captured category policy, and the final source coverage. It checks each image size, pixel bits and hash.

Category	Usable records	Language variants	Photos
Natural curiosities	66	113	52
Castles and fortifications	729	1288	694
Archaeology and megaliths	48	76	40
Monasteries and abbeys	67	123	64
Cathedrals	12	33	12
Passes	193	416	157
Mountain huts	218	282	194
Observation towers	38	46	37
Covered bridges, viaducts and aqueducts	35	53	35
Dams	26	35	26
Industrial heritage	12	17	12
Pilgrimage churches and hermitages	4	5	4
Lighthouses	0	0	0
Boundary oddities	3	3	3
Ghost towns	2	2	0
Hot and mineral springs	0	0	0

The zero lighthouse and hot/mineral-spring counts are usable-content results from a complete capture. They do not mean acquisition is incomplete.

Resource checks

Bound	Largest observed	Limit
Name bytes	141	256
Pages per variant	4	4
Bytes per page	184	1,024
Encoded text bundle bytes	635	4,118
Raw notice bytes	7,866	8,192
Structured credit bytes	694	1,024

Each photo is exactly 51,840 RGB222 bytes (216 × 240), with the top two bits clear. Each derived credit has four fields. These checks use the current #2123 credit format. No resource limit changes. No map section, compressed map size, firmware resource baseline or card package is measured here; map assembly and actual-content acceptance stay in #2026.

Content for later visual acceptance

• Mountain huts: Capanna Grossalp (Q166779). de article, revision 219433662; photo source. Retained RGB file: Q166779.rgb222; SHA-256 3b2514ae6a350a5a3510ee76ce5579c1c2818cc7af28952027dd0871ec0c50c9.
• Observation towers: Aussichtsturm Chuderhüsi (Q587831). en article, revision 1186392269; photo source. Retained RGB file: Q587831.rgb222; SHA-256 4b3d78b9d84b54c51e4425ceb55ca6a584a64e55408ff6905597c9ce7a105c2f.

Both article identities match retained manifest entries. Both photo hashes match actual compiled files. This is source/content evidence, not a simulator or device UI acceptance result.

Retained identities and files

Raw capture: /Users/timo/.cache/openbikecomputer/bake/landmarks/switzerland-2095-bd279d4.

Final outputs and receipts: /Users/timo/.cache/openbikecomputer/bake/transitions/2095-final-bca69f52. first-result.json and second-result.json contain the exact commands, true exits, log hashes and every output-file hash. validation.log contains the full checked counts and limits. The copied manifest.final.json matches the current locked manifest.

Identity	SHA-256
Compiler	f4572ccdcabbc6f4cfc31632bcb2d6a3df217628eaaa1f0492db1d61bf1cfb16
Content policy	0074c8caede43bef40d985c744ef2ff5124cf0d080009cac94efb9fd55e6c51a
Manifest	aed9b3615a4b0948836f3d89107f337351b5911297954994379c74cb9ecfa257
Manifest + boundary input	0451f541a91310ecc4f12727d09be7a22ce02a3738f7dcd00193eecc670871e1
Boundary	1b36c21d52a4419d410893ea41dd522d36238ada0b253c7fe78b81d2ef1edd5b
Category policy	ce6aad265cf8fee09939f91eafd882c35cb59572de446fa671c449f677b1701c
Candidate input	8270fe6b13177e86cec25e18df1219d357a9f6ed44aec264aa8ad12f80a0d91c
Recipe	d2f36fc44239b5706cd05813f8d5871081c745440789a11756365e542eadf5a9
Selection	a23189abdd6fa05bd76a7a64c170ac06a9d78e9b20e67765e05b72e2d24d9a87
identity.json	1c3b34cd6127e6902b73ad0047d5c5472d5c03eb432932074538c6b64d4447be
first-result.json	6e04b1156b1225b2150caaa81f1f295f46424d473da2faf6564612b8ef153b87
second-result.json	a1a6c9972006a923f4ea543b25f073247f2dc74a2fbb2b8900afd934922d7f9e
validation-result.json	5eb9cc44fcf04229f9cd202b668a6419ad724f9c3c88f575844c6b0b3c42c44e
validation.log	5267ab2ec55fce1a1057d8648d2f8c8f47d97e9b668bacfcbd3814a62044556e

The source/compiler identity, initial-pass transition and retry provenance remain in sibling directories 2095-2163-source, 2095-bca69f52-resume and 2095-bca69f52-retry. All older capture and compatibility records are preserved.

No raw archive was published, no fixture was registered or re-pinned, no production credentials were used, and no map/card or hardware was changed.

Requirements: none

[timohueser]

Post-session cleanup is complete.

The two detached capture worktrees and the four completed-task local branches are removed. Their commits remain reachable from origin/develop. The corresponding remote branch heads are absent. Temporary compatibility build output is removed. Unrelated worktrees and branches are unchanged.

The completed raw capture, final compiled outputs, pinned compiler binaries and compatibility evidence remain in place. The final manifest and content hashes are unchanged.

Source provenance no longer depends on retaining Git worktrees:

• /Users/timo/.cache/openbikecomputer/bake/transitions/2095-source-archives contains verified source exports for a926b773, bca69f52 and 29e9794c. identity.json records full commits, tree identities and archive hashes.
• The exact original compatibility build source is retained separately as current-base-actual-source.tar.gz, SHA-256 73345e970b6b0f74c421be1d4a207a6ba81667eedc6f45bb6958f32eb0f6a36b. Fresh extraction reproduces the original 2,021-file tree digest bf70a4fc79dacd154e6ffde7f35605f40f1d371ce693753f4773cafff8adf8ac. It includes unrelated iOS files and is distinct from the clean Git source export.
• /Users/timo/.cache/openbikecomputer/bake/transitions/2095-session-receipts retains verified copies of the completed session scripts, status files and logs. Its identity file maps the historical /tmp execution paths to the retained paths and hashes.

The old worktree and /tmp paths in earlier execution records are historical locations. The source archives and retained receipt paths above replace them for provenance. No capture data or final artifact is discarded.