ryan/vault-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault move: support area/category/ID codes on either side, incl. cross-level promotion

Browse Source 
- vault move now accepts any JD code kind (area/cat/ID) on both old and
  new, not just ID->ID. Enables e.g. 'vault move F.50.09 F.59' to promote
  an ID to a standalone category.
- Refuses if the source has nested JD-coded children (would orphan their
  codes -- that's a bulk renumber, a different and riskier operation).
- Also commits vault_sync_daemon.py (inotify bidirectional /vault<->/data
  sync service, with ntfy notifications on rename/archive/stub/error).
This commit is contained in:
Hermes
2026-09-15 21:56:27 -04:00
parent abf9569a9a
commit 069552d1b4
3 changed files with 634 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vault
+3 -1
View File
@@ -10,7 +10,9 @@ Subcommands:
vault search <query> find IDs/notes by code, title, or content
vault show <ID> show an ID's note + its /data home + blob count
vault create <ID> "<title>" create ID note (folder+folder-note) in /vault AND /data
vault move <oldID> <newID> renumber: rename note+folder, rewrite backlinks, move /data dir
vault move <oldCode> <newCode> renumber/promote: area, category, or ID code, either side (e.g.
cross-level "vault move F.50.09 F.59" promotes an ID to a
standalone category); rewrites backlinks, moves /data dir
vault rename <ID> "<title>" retitle in place, rewrite backlinks
vault sync-data reconcile /data skeleton to match manifest (create missing dirs)
vault manifest regenerate the topology manifest note