Meet Proxy 0.4.44 — receiver readiness reporting

Setup now distinguishes a stale successful receiver checkpoint from a ready, stopped, failed, starting or obsolete receiver. A slow polling cycle no longer says “ready” while suggesting setup again. Delivery remains unconfirmed until the existing freshness checks pass; dispatch and host permissions are unchanged.

Includes resumable large-context downloads and the prior native collection and Work messaging repairs. The production server remains 20261101-resumable-context. 840 core checks, 32 extracted-native checks, both-alias packaging and independent review pass.

Meet Proxy 0.4.43 — resumable context downloads

Long context downloads now keep validated partial progress across archive revisions and companion restarts. Reuse is bound to the same owner, document path, full digest and character count; only complete hash-verified files can be published. Changed or excluded sources invalidate cached progress.

Includes the prior Work routing, native receiver, automatic collection and source-mirror fixes. Account linking, sharing rules, classifier configuration and host permissions are unchanged. Existing chats may retain their loaded plugin catalog until the host reloads them; the companion upgrades through its supported guard.

Meet Proxy 0.4.42

Restores context-folder progress when uploads outpace archive publication, using source-backed mirror reads and exact projection checks. Protects current receiver names/capabilities from older loaded plugins and checks the actual receiver version during startup.

Requires server 20261101-context-recovery for the new mirror handshake. Existing account identity, host permissions, sharing policies and private-source boundaries are preserved. Both Meet Proxy and Commonplace aliases are included. Full live acceptance evidence remains in the source repository; package installation alone does not prove every host flow.

Meet Proxy 0.4.41: Work messaging and context recovery

Native 0.4.41/runtime74 adds targeted Work-board questions, verified Conductor chat names, receiver timeout/recovery improvements, and resumable private context-folder downloads. Current membership, selected receiver, account, sharing and host-permission boundaries remain intact.

Companion activation is guarded and preserves the existing account. Existing native chats may retain an older loaded plugin until their host reconnects it. Remote MCP retrieves existing context; it cannot collect web-only chat history. Server and real installed acceptance evidence are recorded separately in the source report.

Meet Proxy 0.4.40: restart-safe Conductor collection

Meet Proxy 0.4.40/runtime73 keeps collecting Conductor chat captures after background restarts. The shared daemon discovers staged visible messages in its exact account folder, without relying on a native chat environment or querying unrelated sessions. Export pagination status remains explicit; missing checkpoints cannot claim complete history. Includes 0.4.39 upload scheduling fairness.

Two regressions fail before/pass after; all 64 source patches replay exactly. Native account, exclusion, consent and host permission boundaries remain unchanged. Web-only chat histories are not collected by remote MCP.

Meet Proxy 0.4.39: reliable context catch-up

Meet Proxy 0.4.39/runtime72 fixes stalled context backfills when a slow request consumes an entire upload pass. The next service class and newest/oldest fresh selection persist with each durable upload, so continuations, due retries and overdue heartbeats keep progressing across restarts.

697 core tests, 34 extracted-runtime checks and exact 63-patch replay pass. Two regressions fail on the previous version and pass here. Complete-capture publication, account isolation, exclusions, exact retries and server backpressure remain unchanged. Existing host MCP processes may retain their loaded version; installation and active companion versions are reported separately.

Meet Proxy 0.4.38 — guarded activation and startup reporting

Meet Proxy 0.4.38 / runtime71 fixes update starvation and missing Conductor startup reporting. A supported update drains recurring work, preserves completed context and saved sync choices, and keeps a busy legacy connection usable. LaunchAgent replacement waits for safe companion activation. Conductor's receiver reports startup to the existing private Personal space when CLI hooks are absent.

695 core checks, 53 setup/browser/account checks, five reproduced regressions, and exact 62-patch replay pass. Host approvals and account/sharing boundaries remain enforced. An installed package does not prove an older host has loaded it or an older companion has activated it. Web-only history still requires supported import/collection.

Meet Proxy 0.4.37 — continuous sync and Space events

Meet Proxy 0.4.37 / runtime70 adds continuous context catch-up and incremental history scanning. Productive catch-up no longer stops at six uploads or waits five seconds between passes. Durable retries, server backpressure, account isolation, source exclusions and complete captures remain enforced.

Spaces use a common durable event stream. Personal is the private default for agents on the same verified account. MCP clients can subscribe, resume missed events and read currently authorized context. Notifications do not guarantee a host starts a model; native collection still requires a supported, activated collector.

685 core checks, 17 extracted-native checks and both-alias package integrity pass. In a synthetic 6,722-file directory with 6,000 backlog messages, discovery checks fell 90%; immediate-mock local processing measured 6.56s to 2.29s. This is not a production network speed measurement.

The Spaces server migration must be activated before updating the marketplace. Existing account and permission choices are preserved; open chats may require host-supported activation to load updated tools.

Meet Proxy server: Work requests and receipt recovery

Targeted questions and replies now stay on the existing Work board and notify only the addressed member's current selected receiver. Membership, generation, rejoin, nonce and reply checks remain enforced. The server also accepts delayed confirmation for an unchanged idempotent native claim while preserving stale-claim and uncertain-delivery fences.

165-file code-only update; no migrations or permission/classifier settings changes. 749 core tests and production deployment checks pass. Live activation and acceptance are recorded separately in the source release evidence.

Spaces events server — 20261101-space-events

Production server bundle for common Spaces events and Personal spaces, including previously staged context-upload compression and contextual invitation changes.

Requires additive migration 0046_personal_space.sql. Use the included checksummed deployment helper with an exact verified baseline, a validated SQLite backup and migration rehearsal. Do not use --code-only. Current expected baseline: 20261031-setup-activation.

Verified locally: 685 core tests, 41 Spaces browser/probe checks, extracted HTTP/OAuth and event/privacy checks, and exact 61-patch source replay. 165 runtime/migration files. Artifact publication alone does not establish production activation; the live deployment receipt will be recorded separately.