manage-tags

Command — Manage Tags

Session reads: event_list, event_details_cache Session writes: event_details_cache, existing_tags

Rename or delete existing Lexicon tags. Execute silently.

---

Phase 1 — Fetch Existing Tags

Build existing_tags and show the user the current tag list with event counts.

Ensure the required Session reads are loaded; load any that aren't.

Build existing_tags: unique tag names from event_details_cache, each with event count.

If zero tags → output ℹ️ No tags found in this project. → return to Execution loop.

Display:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  TAGS — [Project Name]  ([N] tags)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  #  │ Tag Name          │ Events
  ───┼───────────────────┼────────
  1  │ Commerce          │ 12
  2  │ Navigation        │ 8
  ...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

(a) Rename a tag  (b) Delete a tag  (c) Done

---

Phase 2 — Rename

Rename a tag, with a merge fallback when the new name already exists.

User picks tag by number or name, provides new name.

Confirm: Rename "[old]" → "[new]" across [N] events?

Atomic rename (preferred): rename the tag at the project level. The change propagates to every event automatically.

Merge fallback: if a tag with the new name already exists, the atomic rename will error. In that case: for each event with the old tag, replace [old] with [new] in its tag array (preserving every other tag the event had). Then delete the now-unused old tag from the project.

Update event_details_cache and existing_tags to reflect the renamed/merged tag.

---

Phase 3 — Delete

Delete a tag from the project.

User picks tag by number, name, or range ("1-3").

Confirm: Delete tag "[name]"? This removes it from [N] events.

Delete the tag at the project level. The change propagates to every event automatically.

Update event_details_cache — remove the deleted tag from every event's tags array. Update existing_tags.