Skip to content

docs(macos): record production Dev ID FileProvider hydration PROVEN on 2026-05-18 - #372

Merged
Jesssullivan merged 1 commit into
mainfrom
jess/macos-fp-reality-devid-proven-2026-05-18
May 18, 2026
Merged

docs(macos): record production Dev ID FileProvider hydration PROVEN on 2026-05-18#372
Jesssullivan merged 1 commit into
mainfrom
jess/macos-fp-reality-devid-proven-2026-05-18

Conversation

@Jesssullivan

Copy link
Copy Markdown
Owner

Summary

Update docs/ops/macos-fileprovider-reality.md to record today's milestone: the production Developer ID FileProvider hydration path is proven end to end through a notarized .pkg install on a clean self-hosted runner.

GitHub Actions run 26061402177 of macos-postinstall-smoke.yml on the registered petting-zoo-mini-tcfs self-hosted runner installed the notarized arm64 .pkg built by run 26057944325 from main commit c08a0a4 (PR #370) and passed the full strict harness with fileprovider_testing_mode=false — the production Dev ID lane, not Mac App Development testing-mode.

Evidence:

  • harness/expected-file-index.json: status: "visible", entry_state: "committed", manifest_exists: true, size: 55, chunks: 1 — PR Add tcfs index inspect + seeded macOS FileProvider smoke gate (TIN-133, #309) #370's tcfs index inspect + require_expected_remote_index gate fired correctly before FileProvider was asked to hydrate.
  • harness/hydrated-expected-file: contains exactly the 55 expected bytes (tcfs macOS post-install smoke v0.12.12 run 26061402177).
  • harness/hydrate-read-error.log: empty (no Operation timed out, no coordinated-read failure).

What changed in the doc

  • Rewrote the lede so the top of the doc no longer asserts "production Dev ID Finder hydration is not a continuously proven release-grade desktop surface" — it now says hydrate is proven, layered proofs (evict/rehydrate, mutation, conflict/status, badges, continuous coverage) are still TIN-133 work.
  • Added a ## 2026-05-18 — Production Dev ID FileProvider hydration PROVEN section right after the lede with run ids, the index-inspect packet, the chain of four stacked unblocks (tailnet endpoint, gh secret set syntax, enforce_tls scheme derivation in commit 0b1dc0c, stale ~/Applications/TCFSProvider.app removal), and an explicit honest scope (what's proven on Dev ID now vs what's still pending).
  • Annotated the prior Dev ID hydration blocker assertions in-place with dated (Updated 2026-05-18: ...) notes pointing back to run 26061402177 — did not delete the historical context.
  • Updated the Not Yet Proven section bullets that previously claimed Dev ID hydrate as unproven.

The historical neo-local packets and May 17 catread blocker packet are retained as context, since this doc's value is the chain of evidence.

Refs

  • TIN-133 (the macOS FileProvider acceptance workstream)
  • PR Add tcfs index inspect + seeded macOS FileProvider smoke gate (TIN-133, #309) #370 (added tcfs index inspect + --seed-expected-file and the require_expected_remote_index gate that made the seeded-fixture proof possible)
  • Sibling evidence packet PR (parallel agent is archiving the full artifact tree under docs/release/evidence/; this doc references it textually)

Test plan

  • Lychee link check passes
  • Doc renders correctly under Jekyll GitHub Pages
  • Lede no longer contradicts the milestone section
  • Historical packets remain referenced in the body

…n 2026-05-18

Run 26061402177 of macos-postinstall-smoke.yml on the petting-zoo-mini-tcfs
self-hosted runner installed the notarized arm64 .pkg built by run
26057944325 from main commit c08a0a4 (PR #370) and passed the full strict
harness with fileprovider_testing_mode=false. Evidence:

- harness/expected-file-index.json: status=visible, manifest_exists=true,
  size=55, chunks=1 (PR #370 remote-index gate fired)
- harness/hydrated-expected-file: exact 55-byte expected content
- harness/hydrate-read-error.log: empty (no Operation timed out)

Update the doc lede, add a 2026-05-18 milestone section recording the four
stacked unblocks (tailnet endpoint, secret-set syntax, enforce_tls scheme
derivation in commit 0b1dc0c, stale ~/Applications/TCFSProvider.app removal),
update the prior production Dev ID Finder hydration blocker assertions
in-place with dated "Updated 2026-05-18" inline notes, and update the Not
Yet Proven section to scope what remains on Dev ID (evict/rehydrate,
mutation upload/readback, conflict/status preservation, badges, continuous
release-day coverage) — these layered proofs are TIN-133 work this week.

Historical neo-local packets and the May 17 catread blocker are retained as
context, not deleted, since this doc's value is the chain of evidence.

Refs: TIN-133, #309, #370
@Jesssullivan
Jesssullivan merged commit 84f1aa9 into main May 18, 2026
12 checks passed
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.

1 participant