Background
Capture applies the per-vault `captureText` tag role on save (auto-tags with the configured value, e.g. `quick`). NoteNew does not — notes created via `/new` skip the role-based default.
This is a small inconsistency that surfaces if an operator uses both routes: their Capture-created notes get the captureText tag; their NoteNew-created notes don't.
What to ship
In NoteNew's save path, read `useTagRoles(activeVault?.id ?? null).roles.captureText` and apply it to the note's tags on save (unless the user has explicitly modified the tags, in which case respect their input).
Small change, ~10-20 LOC. Mostly a port from Capture's pattern.
Acceptance
- NoteNew-created notes carry the configured `captureText` tag.
- Tests cover the role-application + the user-override case.
- Behavior is consistent between Capture and NoteNew.
Related
- notes#123 — where this consistency gap was noted.
- `captureText` Tag Role defined in
src/lib/vault/tag-roles.ts.
Background
Capture applies the per-vault `captureText` tag role on save (auto-tags with the configured value, e.g. `quick`). NoteNew does not — notes created via `/new` skip the role-based default.
This is a small inconsistency that surfaces if an operator uses both routes: their Capture-created notes get the captureText tag; their NoteNew-created notes don't.
What to ship
In NoteNew's save path, read `useTagRoles(activeVault?.id ?? null).roles.captureText` and apply it to the note's tags on save (unless the user has explicitly modified the tags, in which case respect their input).
Small change, ~10-20 LOC. Mostly a port from Capture's pattern.
Acceptance
Related
src/lib/vault/tag-roles.ts.