Skip to content

fix: preserve arbitrary Markdown entry content - #21

Merged
rogerchappel merged 3 commits into
mainfrom
agent/oss-90ee724d1a37-markdown-serialization
Aug 11, 2026
Merged

fix: preserve arbitrary Markdown entry content#21
rogerchappel merged 3 commits into
mainfrom
agent/oss-90ee724d1a37-markdown-serialization

Conversation

@rogerchappel

Copy link
Copy Markdown
Owner

Summary

  • serialize frontmatter strings and tag arrays with JSON-compatible YAML values
  • choose code fences longer than every captured backtick run and recover text by its indexed UTF-8 byte length
  • render source and tags as escaped, delimiter-safe code spans in stored entries and exports
  • document the updated format while retaining legacy fixed-fence reads

Commits

  • 0e05e89 test: cover arbitrary Markdown entry content
  • 94afe88 fix: serialize Markdown entries safely
  • 96c23c0 docs: describe robust entry serialization

Verification

  • npm ci
  • npm test (15/15 tests pass)
  • npm run release:check
  • git diff --check origin/main...HEAD
  • commit identity guard: all 3 commits are authored and committed by Roger Chappel miscanalysis@gmail.com

@rogerchappel
rogerchappel merged commit 7ccd3c5 into main Aug 11, 2026
1 check 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.

1 participant