release: v0.19.7 — the Darwin boot id names the boot session, not the clock (#802) by antoinetoussaint-byte · Pull Request #858 · codefly-dev/core

antoinetoussaint-byte · 2026-10-27T19:19:54Z

Release v0.19.7

Bumps version/info.codefly.yaml 0.19.6 → 0.19.7. version-tag.yml cuts v0.19.7 from the commit main carries once the codefly core suite is green on it. Nothing else changes in this PR.

What ships under v0.19.7 (merged since v0.19.6)

Release-driving fix:

fix(runners): the Darwin boot id names the boot session, not the clock #802 — fix(runners): the Darwin boot id names the boot session (kern.bootsessionuuid), not the clock. At v0.19.6 darwinBootID() formats kern.boottime as sec:usec, which xnu re-derives whenever timed steps the clock, so processMark.alive() reads a live process as dead within one boot (measured: recorded 1792426260:726687, read 1792426260:782062). codefly-dev/service-postgres#199 waits on this tag to repin from a commit to a release.

Also included: #806, #820/#821 (PlanRuntimeContexts, Advertisement.BackendsComplete), #824, #829, #830 (CI on Go 1.27.3), #835, #836, #838, #839, #843, #844, #845, #846, #847, #848, #849, #850, #851, #852, #856.

Contract

agents/contract/contract.json: protocolVersion 1 and startupProtocolVersion 2 are unchanged. One operation contract is added, runtime-backend-declaration/v1 — an agent-side opt-in (Advertisement.BackendsComplete); an agent that does not set it advertises exactly as before. No agent rebuild or fleet repin is required by the contract.

Consumers

codefly-dev/cli main and v0.1.219 already pin a8599bd3991a (fix(runners): the Darwin boot id names the boot session, not the clock #802's merge), so 84 of the 90 commits here are already running there; the six new to the fleet are fix(services): reconcile --runtime-context against the plugin's declared backends (#820) #821's and fix(module): allow foreign methods to select their serving service #856's.
codefly-dev/service-postgres#199 repins to this tag once it exists.

Checks run

make check-version-tag: declares 0.19.7; latest published tag is v0.19.6 — ok.

🤖 Generated with Claude Code

… clock (#802) Bump version/info.codefly.yaml 0.19.6 → 0.19.7; version-tag.yml cuts the tag from the merged commit once the suite is green. Carries #802 (kern.bootsessionuuid BootID, which service-postgres#199 needs as a release), #806, #820/#821, #824, #829, #830, #835–#852, #856. Agent contract: protocol 1 / startup 2 unchanged; adds the optional operation contract runtime-backend-declaration/v1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

antoinetoussaint-byte · 2026-10-29T10:59:09Z

A lazybox agent is working on this. codex (codex-stop-final/.codefly/agents/service… + Show details

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI integration; no local parallel metadata mechanism.

• Completed /root/redis_launch_release_review

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.
• Started /root/registry_provenance_design

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg… └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… + 271 lines (⌃t to expand)
1 background terminal running · /ps to view · /stop to close

› Ask Codex to do anything

GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers… ? for shortcuts⚠ 5 warnings · f2 to view
› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI integration; no local parallel metadata mechanism.

• Completed /root/redis_launch_release_review

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.
• Started /root/registry_provenance_design

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg… └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… + 271 lines (⌃t to expand)
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov 2nd, 2026 6:05 AM.

1 background terminal running · /ps to view · /stop to close

› Ask Codex to do anything

GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers… ? for shortcuts⚠ 5 warnings · f2 to view
› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI integration; no local parallel metadata mechanism.

• Completed /root/redis_launch_release_review

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.
• Started /root/registry_provenance_design

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg… └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… + 271 lines (⌃t to expand)
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov 2nd, 2026 6:05 AM.

1 background terminal running · /ps to view · /stop to close

› Ask Codex to do anything

GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers… ? for shortcuts⚠ 5 warnings · f2 to view + Show details

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI integration; no local parallel metadata mechanism.

• Completed /root/redis_launch_release_review

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.
• Started /root/registry_provenance_design

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg… └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… + 271 lines (⌃t to expand)
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov 2nd, 2026 6:05 AM.

› Ask Codex to do anything

GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers… ? for shortcuts⚠ 5 warnings · f2 to view + Show details

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI integration; no local parallel metadata mechanism.

• Completed /root/redis_launch_release_review

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.
• Started /root/registry_provenance_design

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg… └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2… + 271 lines (⌃t to expand)
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov 2nd, 2026 6:05 AM.

› Ask Codex to do anything

GPT-6-Astra · high) started at 2026-10-27 19:42 UTC, last renewed the claim at 2026-10-29 10:59 UTC, and the claim lapses at 2026-10-29 11:59 UTC unless it is renewed again. A claim is an assertion with an expiry, not proof that a process is alive.

claim detail

Lazybox-Claim-Device: effacd542b611010656e
Lazybox-Claim-Session: b2ed85c927
Lazybox-Claim-Workspace: github-codefly-dev-core-858
Lazybox-Claim-Agent: codex
Lazybox-Claim-Model: codex-stop-final/.codefly/agents/service…     + Show details                                                                                                      

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
  readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running          readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or       backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI    integration; no local parallel metadata mechanism.


• Completed `/root/redis_launch_release_review`

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate   versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates    ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.     
• Started `/root/registry_provenance_design`

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg…  └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    + 271 lines (⌃t to expand)                                                                                          
  1 background terminal running · /ps to view · /stop to close


› Ask Codex to do anything

  GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers…  ? for shortcuts⚠ 5 warnings · f2 to view 
› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
  readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running          readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or       backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI    integration; no local parallel metadata mechanism.


• Completed `/root/redis_launch_release_review`

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate   versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates    ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.     
• Started `/root/registry_provenance_design`

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg…  └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    + 271 lines (⌃t to expand)                                                                                          
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov    2nd, 2026 6:05 AM.

  1 background terminal running · /ps to view · /stop to close


› Ask Codex to do anything

  GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers…  ? for shortcuts⚠ 5 warnings · f2 to view 
› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
  readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running          readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or       backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI    integration; no local parallel metadata mechanism.


• Completed `/root/redis_launch_release_review`

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate   versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates    ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.     
• Started `/root/registry_provenance_design`

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg…  └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    + 271 lines (⌃t to expand)                                                                                          
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov    2nd, 2026 6:05 AM.

  1 background terminal running · /ps to view · /stop to close


› Ask Codex to do anything

  GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers…  ? for shortcuts⚠ 5 warnings · f2 to view     + Show details                                                                                                      

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
  readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running          readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or       backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI    integration; no local parallel metadata mechanism.


• Completed `/root/redis_launch_release_review`

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate   versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates    ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.     
• Started `/root/registry_provenance_design`

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg…  └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    + 271 lines (⌃t to expand)                                                                                          
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov    2nd, 2026 6:05 AM.


› Ask Codex to do anything

  GPT-6-Astra high · ~/.lazybox/v2/github-codefly-dev-core/PR-858-release-v0-19-7-the-darwin-boot-id · Resolve blockers…  ? for shortcuts⚠ 5 warnings · f2 to view     + Show details                                                                                                      

› Record extension rollout warning: both CLI parseAuthenticatedRecord (pkg/processgroup/reaper.go638) and Core
  readPgidRecord use DisallowUnknownFields. Appending workspace to authenticated-v1 .pgid makes existing running          readers quarantine/remove new valid records as malformed. Please account for schema namespace/version boundary or       backward-compatible owner seam before shipping workspace provenance. Root needs exact API/record contract before CLI    integration; no local parallel metadata mechanism.


• Completed `/root/redis_launch_release_review`

• The strict-reader warning rules out adding a field to authenticated-v1. I’ll put new provenance records in a separate   versioned namespace, retain explicit support for existing v1 records, and expose scope only after Core authenticates    ownership. I’m getting fresh architecture review of that transition before giving the CLI owner a final contract.     
• Started `/root/registry_provenance_design`

• Ran sed -n '105,132p' runners/base/pgid.go; sed -n '190,245p' runners/base/pgid.go; sed -n '860,938p' runners/base/pg…  └ /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    /private/tmp/claude-501/-Users-antoine--lazybox-v2-github-obin-ai-handbook-context/46685f95-f6a6-435c-84df-6c6c6cf2…    + 271 lines (⌃t to expand)                                                                                          
■ You’ve hit your usage limit. Visit https://chatgpt.com/settings/usage to purchase more credits or try again at Nov    2nd, 2026 6:05 AM.


› Ask Codex to do anything

  GPT-6-Astra · high
Lazybox-Claim-Started: 2026-10-27T19:42:36Z
Lazybox-Claim-Heartbeat: 2026-10-29T10:59:01Z
Lazybox-Claim-Expires: 2026-10-29T11:59:01Z

antoinetoussaint-byte added the working Claimed by a lazybox agent; cleared when the session ends. label Oct 27, 2026

antoinetoussaint-byte merged commit 557f6a3 into main Oct 27, 2026
10 checks passed

antoinetoussaint-byte mentioned this pull request Oct 27, 2026

release: v0.19.8 with durable runtime ownership and verified acquisition #819

Merged

Navigation Menu

Repository navigation

release: v0.19.7 — the Darwin boot id names the boot session, not the clock (#802) - #858

release: v0.19.7 — the Darwin boot id names the boot session, not the clock (#802)#858
antoinetoussaint-byte merged 1 commit into
mainfrom
release/v0.19.7

antoinetoussaint-byte commented Oct 27, 2026

Uh oh!

Uh oh!

antoinetoussaint-byte commented Oct 29, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

antoinetoussaint-byte commented Oct 27, 2026

Release v0.19.7

What ships under v0.19.7 (merged since v0.19.6)

Contract

Consumers

Checks run

Uh oh!

Uh oh!

antoinetoussaint-byte commented Oct 29, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant