Skip to content

Blocked handoff: integrate Codectx App with an accepted host #14

Description

@greygoody

Implementation workcell handoff

Status

workcell_id: codectx-app-host-integration-v0
state: blocked
scope: implementation
blocked_by:
  - greygoody/codectx#13
  - accepted host app/runtime contract

Mission

Install and supervise Codectx through one accepted host runtime, maintain a live projection from at least two lenses, process one explicit move, and prove correct state behavior across compositor or bearer restart.

Host-selection gate

Before implementation, record:

  • candidate hosts inspected;
  • app identity and lifecycle contract;
  • capability boundary;
  • event/subscription model;
  • app-local state and persistence acknowledgement;
  • failure and resource model;
  • selected host and rejected alternatives.

Orb is preferred only after its app/runtime contracts are accepted. Codex is eligible only if it exposes equivalent bounded integration. No host is selected by this issue today.

Required scope after unblocking

  • one host-specific Codectx App adapter;
  • compositor lifecycle management;
  • bounded lens registration and subscriptions;
  • projection delivery to one continuously subscribed or ambient surface;
  • explicit move routing;
  • persistence of one eligible explicit state item;
  • restart and degraded-state handling;
  • version and capability rejection tests;
  • complete execution trace.

Required scenario

  1. host installs and starts the Codectx App;
  2. repository and managed lenses connect;
  3. healthy state collapses;
  4. urgent or contradictory update appears without manual query;
  5. one explicit move is accepted;
  6. bearer or compositor restarts;
  7. eligible explicit state is restored;
  8. derived state is recomputed;
  9. managed source state is re-observed rather than treated as Codectx-owned history;
  10. current v1 CLI remains usable as recovery and inspection surface.

Non-goals

  • multiple production hosts;
  • distributed projection federation;
  • contacts or social semantics inside Codectx;
  • a general app marketplace;
  • rewriting host architecture;
  • production deployment;
  • source-system authority inside Codectx.

Required proof

  • selected-host contract and version;
  • capability matrix;
  • lifecycle, subscription, restart, and degraded-state traces;
  • compatibility proof for existing CLI and packets;
  • contribution-only evidence recorded in greygoody/orb-eval.

Stop conditions

Stop and report when host contracts are unstable or implicit, durable writes cannot be acknowledged, compositor semantics must move into the adapter, undeclared capabilities are required, freshness cannot be preserved, or restart requires persisting derived projection as authority.

Completion

The workcell closes only when Codectx is continuously available through one real host while preserving host neutrality, source authority, compatibility, and declared state lifetimes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions