Skip to content

Consolidate visual editor, project authoring and attached CLI improvements #313

Description

@concordia-claw

Category consolidation

Requested by Joel Z. Leibo in issue #373. This is the single continuing issue for this category. Implementation and subsequent improvements stay in PR #314. Approved PRs #297, #302, #304 and #332 are exempt and remain unchanged.

Scope

  • Preserve card/inspector identity and literal multiline component text.
  • Keep lifecycle status, counters and controls authoritative across tabs and reconnects; return readable errors for rejected requests.
  • Edit, save, reopen and explicitly run a supported initial project through the existing editor and a shared normalized Config.
  • Discover/query/dispatch validated operations from the existing browser UI and concordia-session; retain revision checks, retry protection and scoped listeners.
  • Reuse attached browser sessions, lazy received-snapshot inspection and coalesced SSE wakeups.
  • Resolve the integration between project authoring and lifecycle controls: a fresh run discards the previous run's terminal state and controls before the next Simulation binds.

Bellwether-specific service handlers, fixtures and integration demonstrations belong to PR #372, not this category. This remains a bounded authoring/shared-operation foundation, not full checkpoint continuation, arbitrary project serialization, general component CRUD, or complete GUI/CLI parity.

Consolidated review history

#308, #310, #312, #316, #328, #362, #368

Superseded issues and PRs retain their original descriptions and point here. Consolidation closes duplicate review threads, not claims that pending code has landed upstream.

Follow-up improvements — 2026-09-13

Alice now uses the standard minimal prefab and Bob the standard basic prefab. Save/reopen retains Bob’s goal, and the real runtime inspector exposes his SelfPerception, SituationPerception and PersonBySituation components. New projects use conversation-v2; existing conversation-v1 documents retain their exact original two-minimal-actor configuration and saved instructions. The README explains document schema versus template revision.

Follow-up commit · Combined validated checkout.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions