"step" is in the other-numbering word list ("step #3" is a position in
a plan), so "steps #5110" correctly stays plain. The case now tests the
range alone, and a second case pins the "step #3" reading.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A purely numeric #N is a record reference everywhere now. The tag
patterns (frontend utils/tags.ts, the editor decoration, the first-line
tag strip, tag autocomplete, backend utils/tags.py) leave digits alone,
so #3127 is no longer drawn as a tag chip linking to /notes?tag=3127.
- utils/recordRefs.ts links #N, milestone N and rule N in rendered
markdown, with the same patterns and other-numbering word list as
services/record_refs.py. A drift test reads the TS source and fails
when the two differ.
- v-record-refs (directives/recordRefs.ts) asks POST
/api/notes/resolve-refs once per body for what each id is. A link
gets the route for its kind (task, lesson, snippet, note, milestone,
rule) and its kind and title on hover. One the reader cannot open is
drawn as a dead reference, and missing vs not shared read the same.
Applied on every surface that renders markdown.
- /milestones/:id finds the project and opens its board at that
milestone (?milestone= expands it, scrolls to it and focuses it).
- Backlinks include records that cite #N in a body or a work log,
through readable_notes_clause instead of an owner-only filter, and
route by kind. The graph draws #N citations as dashed reference edges.
- create_note, create_task and add_task_log say which forms link.
There were no numeric tags to clean up: tags are stored only from the
explicit field, and none of the 200 most used is numeric.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>