docs(chit): PMOVESCHIT VISUAL_TOUR interactive walkthrough - #1847
Conversation
Adds VISUAL_TOUR.md (interactive code-walkthrough tour) and wires it into the PMOVESCHIT README navigation paths (quickstart + video-rendering). Carved from scratchpad branch docs/nats-ws-port-canonical-fix — genuinely unmerged docs work. The branch's nats-ws fix is already on main via #1579. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 041a0a8c92
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ```bash | ||
| # Generate CGP from docx | ||
| python pmoves/tools/chit_backend.py yourfile.docx --out cgp.json --K 8 --S 3 |
There was a problem hiding this comment.
When a developer follows this new Quick Reference, the command will not parse: pmoves/tools/chit_backend.py defines --input, --output, --K, --bins, --backend, and --no-validate in its argparse setup (pmoves/tools/chit_backend.py:327-340), so the positional yourfile.docx, --out, and --S are unsupported, and the tool consumes JSONL chunks rather than docx. This makes the promised run-it-yourself walkthrough fail before generating a CGP; please update the tour to the current --input ... --output ... flow or add the documented docx wrapper.
Useful? React with 👍 / 👎.
| url: "http://localhost:8105/render" | ||
| alternates: | ||
| - "http://localhost:8105/render/provenance" # Direct living-doc renders |
There was a problem hiding this comment.
In this repo the A2UI renderer defaults to port 8107 (pmoves/services/a2ui-renderer/src/index.ts:7 and the PORT default) and the Remotion skill manifest also points to http://localhost:8107/render (pmoves/skills/remotion-render/manifest.yaml:50-54), while 8105 is used by Cipher in compose. Anyone following this new Remotion section or the later curl examples will hit the wrong service or get a connection failure; please change these Remotion URLs to 8107.
Useful? React with 👍 / 👎.
| curl -X POST http://localhost:8105/render \ | ||
| -H "Authorization: Bearer $JWT" \ | ||
| -d '{"a2ui_spec": {...}, "format": "mp4", "quality": "high"}' |
There was a problem hiding this comment.
Even after the port is corrected, this raw /render curl will fail because the service treats req.body itself as the A2UI spec and returns 400 unless version, animation, and scenes are top-level fields (pmoves/services/a2ui-renderer/src/index.ts:261-267). The documented {"a2ui_spec": {...}} wrapper matches the skill manifest input, not the HTTP route, so developers copying this command will not be able to render; please show a top-level A2UI spec body for direct curl usage.
Useful? React with 👍 / 👎.
1 participant
What
Adds
VISUAL_TOUR.md(interactive code-walkthrough tour) to the PMOVESCHIT docs set and wires it into README navigation (quickstart + video-rendering paths).Why
Carved from the scratchpad branch
docs/nats-ws-port-canonical-fixduring submodule/branch triage. That branch turned out to hold mostly already-merged work; this docs pair was the genuinely-unmerged remainder. The branch's own nats-ws fix is already on main via #1579.Scope
pmoves/docs/PMOVESCHIT/VISUAL_TOUR.md(new)pmoves/docs/PMOVESCHIT/README.md(3 nav references)Docs-only, no code paths touched.
🤖 Generated with Claude Code