feat(app): support Markdown in task details and messages #67
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/01a158a9-markdown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Task descriptions now render Markdown in authored order, with Mission Control's existing Checkbox and a separate Edit description action. Conversation and activity steps show saved state and are read-only. Quick view keeps plain notes, grouped steps and its other editing controls; description tap-to-edit is removed.
Evidence
30f0372. Quality: 129 files / 866 tests, type/lint/dependency/format checks; documentation, deployment-tool smoke and both server/agent image builds passed.972bb75showed raw task descriptions and extracted steps; before phone/desktop screenshots are attached to the task.Merge danger
Door: two-way
No schema or stored-format change. Main builds an image and updates the existing draft release; it does not publish a stable release or deploy this UI. Creating/publishing a release remains a separate approval step.
Blast radius: app
The shared renderer also serves roles, skills, routines, templates and transcripts. It retains the existing theme and native Text/View conventions. HTML is inert; unsafe link schemes are rejected; images never load inline. No new execution, privilege, auth or exposure path meets the Security Engineer trigger. No Designer sign-off was requested.
Rollback and verification
Owner self-review at
30f0372against main972bb75. Standards: no open findings; shared native/themed rendering and source-edit module follow repo conventions. Spec: reproduced and fixed CR-only line preservation, and restored completed-label styling without crossing out nested content; fix-only reviews confirm resolution. Source tests and web task/Markdown flows pass, Android/Hermes export passes. Actual Android UI/TalkBack/selection/touch acceptance remains unverified because no SDK/adb/emulator/target is available. Images only link, HTML stays inert, no new security review trigger. Release/rollout remains pending; verify native UI then approved release pipelines, live image pins/readiness and the original Markdown interactions. Roll back with a compatible revert release; no schema/source format changed.Shipped in v0.50.0, combined source
57a858b838(including #68). Main pipeline #475 and complete release pipeline #476 passed, including the signed Android APK. Apps CI #381 passed for pair-update 9695f53. Argo is Synced/Healthy at that revision; actual server and restarted agent imageIDs match the release digests, PVC remains Bound and health is ok. The original authored-order failure was reproduced on v0.49 public assets; all eight phone/desktop Markdown checks now pass against the deployed v0.50 assets using isolated local API fixtures. Native Android acceptance follows release on Morten’s device as explicitly authorized, and remains unverified until that test. Release/APK/checksum and visual evidence are on task 01a158a9.