Review stale open issues after docs and product gap audit

[alonshoa]

Problem

The documentation gap audit found several existing open issues that appear partly complete or need refinement against the current implementation. The issue tracker should reflect the current product state before the next documentation/onboarding epoch starts.

Scope

• Review Ensure devcontainer PATH exposes /opt/venv/bin in non-interactive Docker runs #13 and [Bug] Devcontainer default Python/PATH points outside the pinned Manim runtime #14 against the current Dockerfile, devcontainer config, and runtime PATH tests.
• Review Implement deferred MCP deck export and full stdio runtime verification #15 against the current CLI/MCP PPTX export implementation and remaining stdio runtime verification gap.
• Review Epic: Epoch 2 — External Project Authoring Workflow #17 and make sure product dependencies are separated from documentation-only onboarding work.
• Update Epic: establish Manim Studio as a reproducible local presentation workspace #1 if earlier roadmap phases are complete or partially complete.
• Close resolved issues or add comments with current evidence and remaining work.

Acceptance Criteria

• Stale issues are either closed or updated with the current implementation status.
• Documentation-only issues are not blocked by product work unless the dependency is real.
• Product work still needed for project initialization, Windows-friendly setup, wrappers, generated MCP config, and latest-build lookup remains tracked separately.
• The roadmap communicates what is done, what is documented, and what remains aspirational.

Dependencies

Requires maintainer agreement before closing or editing existing issues.

Category

project-management, documentation, roadmap