Skip to content

fix: preserve explicit Note mention metadata - #13

Open
nori-sessions[bot] wants to merge 1 commit into
mainfrom
fix/preserve-note-mention-spans
Open

nori-sessions[bot] wants to merge 1 commit into
mainfrom
fix/preserve-note-mention-spans

Conversation

@nori-sessions

@nori-sessions nori-sessions Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • preserve explicit Substack mention provenance as optional structured spans without changing exported text
  • keep ordinary prose names out of mention metadata
  • document the backward-compatible artifact field and UTF-16 offsets

Validation

  • npm run compile
  • npm run lint
  • npm test (58 tests)
  • exported live Note 337946839: no mention spans for Krebs or Hegseth
  • exported 163 recent Notes: 7 explicit mention spans; all validated with text.slice(start, end) === label

@nori-sessions
nori-sessions Bot force-pushed the fix/preserve-note-mention-spans branch from 6ef47c9 to 1dd44f2 Compare September 15, 2026 23:22
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.

0 participants