Skip to content

docs(id): specify and test F13.8 client-only boundary #3846

New issue
New issue
Closed
Closed
docs(id): specify and test F13.8 client-only boundary#3846
Labels
app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/enhancementpriority/lowNice to have; do when convenient

Description

@dezren39
dezren39
opened on Nov 1, 2026

Parent: #790 (Phase 13 F13.8 topology). Phase 2 — independently mergeable authority-boundary documentation/test.

Document that id world join and other remote world client commands are client-only by default; they never start a listener or server. Serving begins only through explicit id serve (and SSH serving remains opt-in). Prefer this explicit command boundary over a redundant --client-only flag unless a real mode switch is found in current code.

Acceptance:

  • The CLI help and ID README explain the client-only default and how it differs from id serve.
  • A regression test exercises/parses the client path and proves it does not dispatch server startup; explicit id serve remains the only server entry point.
  • Document that node connectivity grants no world authority; a world capability is still required.
  • No host, listener, or authority is started merely because the client opens additional world sessions.

Grounding: Phase 13 plan F13.8 (.opencode/plans/phase-13-client-shells.md:27,70,97-107); id world join is a remote client path (pkgs/id/src/commands/world.rs:720-748) while Serve is a separate top-level command (pkgs/id/src/cli.rs:255, commands/serve.rs:728).

Activity

  1. dezren39
    added
    priority/lowNice to have; do when convenient
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    effort/mMedium: expected under 1 day of work
    kind/enhancement
    queue/queuedHas a queued task in the Supabase agent queue
    status/needs-triageNot yet triaged; needs a first look
    on Nov 1, 2026

  2. dezren39 commented on Nov 1, 2026

    @dezren39
    dezren39
    on Nov 1, 2026
    MemberAuthor

    agent-note:v1 — queued, parent #790 phase 2; queue task 5833, dedupe repo-health:v1:fix:developing-today/code:issue:3846. Resume from current main: document and regression-test that world client commands stay client-only and only explicit id serve starts a server. Filed by repo-worker-code, OpenChamber scheduled lane, 2026-11-01T17:05Z.

  3. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 1, 2026

  4. dezren39 commented on Nov 1, 2026

    @dezren39
    dezren39
    on Nov 1, 2026
    MemberAuthor

    Agent note (task 5833, lane E): implementation pushed — PR #3862 (branch queue/5833-3846-client-only-boundary, commit f2caec6). World/Serve CLI help and README now state the F13.8 client-only boundary (client commands never serve; id serve is the only server entry point; SSH serving opt-in; connectivity is not world authority — a capability is required), and test_world_client_commands_never_dispatch_serve pins it at parse level. Task parked 20m for the Codex review running on PR #3862; resume: disposition any Codex findings, confirm checks, merge, close this issue.

  5. dezren39
    added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    on Nov 1, 2026
  6. dezren39
    added a commit that references this issue on Nov 1, 2026

    docs(id): narrow the client-only boundary wording per Codex review (#…

    7e11b61
  7. dezren39
    added
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 1, 2026
  8. dezren39
    added a commit that references this issue on Nov 1, 2026

    Merge pull request #3862 from developing-today/queue/5833-3846-client…

    f7c942b

  9. dezren39 commented on Nov 1, 2026

    @dezren39
    dezren39
    on Nov 1, 2026
    MemberAuthor

    Closed by PR #3862 (merged f7c942b). The F13.8 client-only boundary is documented in the World/Serve CLI help and the README, narrowed per Codex review to hosting/authority with the ssh-tunnel and mirror listener exceptions stated, and pinned by test_world_client_commands_never_dispatch_serve (cli::tests: 117 passed on the laptop; Codex round 2 on the final head: no findings).

  10. dezren39
    closed this as completedon Nov 1, 2026
  11. dezren39
    removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/enhancementpriority/lowNice to have; do when convenient

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions