Repository navigation
fix(discord): render local source citations as readable paths - #284
Conversation
|
Merged and deployed PR #284 to production Validation: 277 targeted tests across formatter/artifact/interface/native-UI suites; typecheck, lint, format and lockfile checks passed. Full production build succeeded, Session verification: all 13 sessions present at restart restored. The baseline-to-after difference was a quiet daily automation session replaced by the old server before restart (replacement created 09:04:16 UTC, restored by new server 09:05:54 UTC). The other 12 IDs/native resume identities stayed unchanged. Worktree clean, no stashes, no dependency changes. PR typecheck/lint CI passed; its broader integration CI was still running at deployment, separate from passing targeted local checks. Newly rendered source citations receive the fix; previously posted Discord cards are not rewritten by this deployment. |
Discord displays local source citations as literal Markdown, exposing brackets and allowing underscores in long paths to be interpreted as formatting. For example,
[the current source](/mnt/.../demand_order.py:572)appears broken in response cards.Render supported local source-file references as
the current source (+ inline-code path +). Preserve the complete path and line number, public web links, image references, code examples, and uploadable output links. Skip non-link lines before scanning to preserve bounded formatting CPU.Fixes #283.
Validation: response-card payload regression using the screenshot path, public/image/code preservation, plus attachment and native UI integration suites. All 277 tests passed across four formatter, artifact, attachment integration, and native UI suites. No production deployment.
Typecheck, lint, format check, lockfile check, and whitespace checks passed. Commit:
a011ea19.