Skip to content

Version the durable-wake repair for installed MCP verification #362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ecochran76 merged 1 commit into from
Oct 26, 2026
Merged

Version the durable-wake repair for installed MCP verification #362

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/dev/plans/0176-2026-10-26-durable-scheduling-repair.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,5 @@ Added optional private host control configversion2 with native_self roots/list/c
Selected SoyLei thread is currently idle, but actual thread/mcpServer/reload dry-run is unsupported by the installed native daemon. No native restart or implicit shared fallback attempted. Existing MCP connections need their supported refresh path; fresh process qualification is separate from resident connection proof.

Source/public60-case selection PASS; curated evidence docs/dev/evidence/issue0360/acceptance.md. PR361 carries integration. Source check against HF-13/#360 confirms due/TTL and owner invariants, explicit version1 compatibility/version2 opt-in, peer filtering and effect-lock rechecks. Supported future calendar is explicit, not a24h limit. Final CI and installed connection cutover remain pending.

PR361 merged02b68e8 with identical CI-qualified treefad5868; full CI40265950701 PASS both Python versions,1728tests/1skip plus wheel gates. An install-identity follow-up advances the development version to0.22.0.dev1 so the existing mcp_catalog resource proof can distinguish a refreshed resident connection from olddev0. No behavior or wake schema change in this follow-up; exact catalog/skill and goal-continuity readbacks remain required.
14 changes: 14 additions & 0 deletions docs/releases/v0.22.0.dev1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# 0.22.0.dev1

Development build for the durable future-wake repair in #360 / PR361.
Relative wakes are not limited to24hours; delivery TTL follows due time.
Receipts show anchored due/expiry and explicit monitor ownership, pending timers
can reconcile without resubmission, and host-opted verified-self controls inspect
or cancel only their own provenance-qualified wakes.

This distinct installed version lets the existing MCP-catalog refresh check
prove that a resident connection actually changed from0.22.0.dev0. New command
symlinks and an isolated fresh catalog do not qualify an old connection. Existing
record schemas6/8 and version1 explicit control grants remain compatible;
version2 verified-self grants are private host opt-in. No recurrence engine,
catch-up/overlap default, native binary replacement or allocation renewal.
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

[project]
name = "codex-wake"
version = "0.22.0.dev0"
version = "0.22.0.dev1"
description = "Durable Codex follow-ups, tracked agent exchanges and MCP tools"
readme = "README.md"
requires-python = ">=3.11"
Expand Down
2 changes: 1 addition & 1 deletion src/codex_wake/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@

__all__ = ["__version__"]

__version__ = "0.22.0.dev0"
__version__ = "0.22.0.dev1"
Loading