Skip to content

feat(coding-agent): integrate Markdown transformer API - #27

Merged
CoderDoubleflower merged 13 commits into
mainfrom
feat/markdown-transformer-api
Jul 31, 2026
Merged

feat(coding-agent): integrate Markdown transformer API#27
CoderDoubleflower merged 13 commits into
mainfrom
feat/markdown-transformer-api

Conversation

@CoderDoubleflower

Copy link
Copy Markdown
Owner

Integrate upstream Pi PR earendil-works#7231 as an isolated feature while preserving pi-claude's Claude-style assistant marker, compact transcript spacing, prompt-height user background, task status UI, branding, release identity, TodoWrite, compaction features, and npm runtime compatibility.

The integration adds a display-only, chainable Markdown transformation API with message type, streaming state, and available terminal width context. It does not merge the rest of the pending upstream commit range.

Validation target: build, check, full tests, and packed npm installation smoke test.

Copilot AI review requested due to automatic review settings July 31, 2026 03:29

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Copy link
Copy Markdown
Owner Author

Integration validation

Integrated upstream Pi PR earendil-works#7231 as an isolated feature. The automatic three-way apply was clean for every changed file except the fork-specific assistant and user message components; those two were manually composed to preserve the Claude-style / markers, compact spacing, prompt-height background, thinking presentation, and OSC 133 zones.

Validation completed successfully in the integration job:

  • monorepo build
  • repository check/type validation
  • assistant and user message transformer tests
  • extension discovery and runner tests
  • TUI Markdown tests
  • packed npm installation smoke test

The upstream width assertions were adapted from 78/58 to 77/57 because the fork's visible message marker and configured padding consume one additional terminal column. This reflects the exact content width available to transformed Markdown.

No TodoWrite, compaction, branding, release identity, tool rendering, task-status, or npm runtime compatibility files were replaced.

@CoderDoubleflower
CoderDoubleflower merged commit 4d01220 into main Jul 31, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants