Skip to content

docs(cockpit-render): aimock e2e not applicable + per-cap port alignment#483

Merged
blove merged 1 commit into
mainfrom
claude/render-aimock-batch
May 20, 2026
Merged

docs(cockpit-render): aimock e2e not applicable + per-cap port alignment#483
blove merged 1 commit into
mainfrom
claude/render-aimock-batch

Conversation

@blove
Copy link
Copy Markdown
Contributor

@blove blove commented May 20, 2026

Summary

Investigation outcome for the render product line. The 6 render capability demos don't fit the aimock e2e pattern because they don't use a chat surface — they're streaming-visualization demos driven by an in-process `StreamingSimulator` over hardcoded sample specs.

What this PR ships

  • `cockpit/render/README.md` — single doc explaining why aimock e2e is not applicable for the render product line (same pattern as `cockpit/chat/debug/angular/e2e/README.md`).
  • Registry: adds `pythonPort` to all 6 render caps (5401-5406) for structural consistency with the chat/langgraph per-cap port convention.
  • proxy.conf.json: aligns each render cap's proxy target with its new pythonPort. Currently no `/api` calls hit it (StreamingSimulator bypasses), but the wiring stays consistent.

What was tried

  • Ran `scripts/generate-aimock-scaffold.ts --cap r-` for all 6 caps — succeeded.
  • Ran `scripts/record-aimock-cap.sh r- "Hello"` — recordings captured the python backends' response shapes.
  • But the Angular demos don't render `` or `` — there's nothing for the e2e helpers to drive. The demos render `` from `@ngaf/render` directly.

Coverage after this PR

  • Chat: 10/11 caps + c-debug documented.
  • Langgraph: 8/8 caps. Done.
  • Render: 0/6 caps + docs (this PR). Demo shape doesn't fit aimock pattern.
  • Deep-agents: 0/7 caps. Pending.

Out of scope

  • Render-specific e2e harness (visual regression, interactive scrubbing).
  • Wiring the render demos to actually call their python backends (would change the demo's intent).

Test plan

  • CI docs-only path: most Cockpit gates skip or no-op.
  • `Cockpit — build / test` passes (wiring spec auto-discovers; render caps have no e2e target so the cross-check skips them).

🤖 Generated with Claude Code

@blove @claude
docs(cockpit-render): document why aimock e2e is not applicable
a3cfbe1 
Investigation: the 6 render capability demos (spec-rendering,
element-rendering, state-management, registry, repeat-loops,
computed-functions) don't fit the aimock e2e pattern.

- No <chat-input>: render demos use a spec picker with hardcoded
  sample specs from app/specs.ts.
- No LLM backend wiring at the UI: python backends exist for the
  LangGraph manifest, but the Angular demo uses an in-process
  StreamingSimulator instead.
- No chat-message bubbles: renders via <render-spec>/<render-element>
  primitives from @ngaf/render directly.

Tried scaffolding via the generator + recording fixtures via the
generic recorder — both succeeded mechanically, but the resulting
e2e specs would have no chat-input to drive. Adding aimock coverage
would require a demo-shape change (give each render demo a chat
surface that feeds specs through an LLM).

What this PR ships:
- `cockpit/render/README.md` — single README documenting the gap
  (same pattern as cockpit/chat/debug/angular/e2e/README.md).
- Registry: adds pythonPort fields to all 6 render caps (5401-5406)
  for structural consistency with chat/langgraph caps. Even without
  aimock coverage, the per-cap port convention is correct.
- proxy.conf.json: aligns each render cap's proxy with its new
  pythonPort. Currently no /api calls hit it (StreamingSimulator
  bypasses), but the wiring is consistent for future use.

Out of scope:
- Render-specific e2e harness (visual diffs, scrubbing). Separate
  cycle if desired.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
threadplane Ready Ready Preview, Comment May 20, 2026 3:11am

Request Review

@blove blove mentioned this pull request May 20, 2026
Merged
3 tasks
@blove blove merged commit 3bd16e2 into main May 20, 2026
33 checks passed
blove added a commit that referenced this pull request May 20, 2026
@blove @claude
test(cockpit-deep-agents): aimock e2e for all 6 deep-agents caps (#484)
84a753d 
Final product line. Brings cockpit aimock coverage to 24 of 32 caps
(75%). All 6 deep-agents caps use composed <chat>, same shape as
the langgraph caps:

- da-planning, da-filesystem, da-subagents, da-memory, da-skills,
  da-sandboxes.

Fixtures recorded via scripts/record-aimock-cap.sh; specs send
"Hello" and assert the assistant bubble renders (smoke-level
end-to-end coverage per cap).

Registry + proxy changes: adds pythonPort to all 6 deep-agents
caps (5310-5315) and aligns proxy.conf.json with the new ports.
Same convention chat and langgraph caps follow.

Coverage after this PR + #483 (render gap doc) merging:
- Chat: 10/11 + c-debug documented = 11/11 handled.
- Langgraph: 8/8.
- Deep-agents: 6/6.
- Render: 0/6 (aimock not applicable; documented in #483).
- ag-ui-streaming: 0/1 (no Python backend by design).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@blove