feat(console): json-render views lens + activity sparkline#197
Open
Lanzelot1 wants to merge 2 commits into
Open
feat(console): json-render views lens + activity sparkline#197Lanzelot1 wants to merge 2 commits into
Lanzelot1 wants to merge 2 commits into
Conversation
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Lanzelot1
force-pushed
the
feat/console-views
branch
from
1f1128d to
601451f
Compare
…nt.publishView
A peer can publish a renderable view (a json-render flat spec: root key +
flat element map) as a { kind: "view", spec } part on an ordinary message —
no new subject, all three delivery modes. Core owns the structural wire
shape (ViewSpec, assertViewSpec); the viewer's component catalog is the
render-side guardrail. SPEC gains the third core Part shape; schema regenerated.
Lanzelot1
force-pushed
the
feat/console-views
branch
2 times, most recently
from
9db360e to
61a33a9
Compare
The console renders peer-published views through a fixed @json-render/ink component catalog (unknown components rejected with a reason); the golden-signal tiles strip now renders through the same catalog, dogfooding the guardrail (Tiles.tsx → tilesSpec + SpecView). MeshView captures view parts (deduped, windowed) and a 15-bucket / 60s message-volume series that the status bar draws as a sparkline next to msgs/s. Text-only surfaces (join, connector inbox) show a [view] placeholder.
Lanzelot1
force-pushed
the
feat/console-views
branch
from
61a33a9 to
16e5570
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Consolidates the console-TUI work (previously scattered across
feat/console-json-renderand uncommitted local iterations) into one reviewable branch, rebased onto current main.@cotal-ai/core): a peer can publish a renderable view — a json-render flat spec — as a{ kind: "view", spec }part on an ordinary message viaendpoint.publishView(spec, { channel | to | toService }). No new subject; rides all three delivery modes with a plain-text label part alongside. SPEC.md gains the third corePartshape;spec/cotal.schema.jsonregenerated.V): renders peer-published views through a fixed@json-render/inkcomponent catalog — declared components only, validated props, never code; an invalid spec shows its rejection reason. The golden-signal tiles strip now renders through the same catalog (dogfoods the guardrail).Verified
pnpm typecheck+pnpm testgreen; view/connect/spawn-from-anywhere smokes pass.publishView→ V lens renders the panel; a spec naming an unknown component (Script) is rejected with the reason; sparkline animates with traffic.Notes
feat/console-json-render(same feature, pre-drift base) — that branch can be deleted after merge.feat/tmux-extensiononly on the identicalSparkline.tsx; merges cleanly either order.(The example-02 demo assets that previously rode along were split into #212 to keep this PR focused on the feature.)