development: just a few more tags

2026/editDesc/2026-05-23 development.ts.txt

@@ -0,0 +1,23 @@
+2026-05-23
+https://linktr.ee/RaincloudTheDragon
+
+0:00 starting soon
+11:06 preramble + fueling
+15:43 Underworks
+21:01 en route to thicket
+40:00 Wisp Thicket
+41:48 Father of the Flame
+47:30 exploring
+1:07:02 travel with caravan
+1:18:33 map consultation
+1:40:21 finally delivered to mask maker
+1:42:50 cooling off
+1:48:03 return with garbage
+1:55:02 routing fleatopia delivery
+1:57:23 fleatopia delivery
+2:55:40 run destroyed
+3:09:41 fleatopia delivery FIN
+3:13:13 more deliveries
+3:37:16 sentinel friendship acquired
+3:40:56 tiny postramble
+3:41:51 goodbye

2026/editDesc/prtranscript/2026-05-23 development.ts_visual_tags.txt

@@ -35,5 +35,5 @@
 # Opsec notes:
 # - SEG stamps: user pre-checked live
 # - gamign/env clusters at ~1:42 and ~3:41 flagged with INT: desktop
-# - map consultation (1:18) = in-game only, deliverable red
+# - map consultation (1:18) = in-game only, user stamp (orange)
 # - INT: mapgenie (3:28) = browser + taskbar + unrelated tabs visible in probe

marker-context.md

@@ -72,9 +72,11 @@ Premiere keeps the raw stamp names; chapters use friendlier labels at the **same
 
 ---
 
-## Deliverable content markers (red / descriptive)
+## Deliverable content markers (descriptive)
 
-Added during tagging (MCP or manual). Short labels: locations, bosses, setup beats, tangents worth skipping or revisiting.
+Short labels: locations, bosses, setup beats, tangents worth skipping or revisiting. May be yours (live/post) or agent-added during visual tagging.
+
+**Red is only for agentic stamps** — markers the agent adds during MCP/visual passes (`Underworks`, `Wisp Thicket`, etc.). Agent `INT:` / `LORE:` → **white**. Your own descriptive stamps → **orange** (same family as `SEG`). Do **not** recolor your existing markers to red; leave pipeline/FUNI/bookend colors alone.
 
 ### Gameplay & exploration
 Examples: `Bellhart`, `far fields arena`, `goo beast defeated`, `first sinner fight`.
@@ -93,6 +95,7 @@ Both bounds are deliverable chapter candidates. Do **not** use `gamign` or `env`
 
 - Chapters in `editDesc/*.txt` are **semi-manual** (JSyntax Workflows + cursor edit prompt).
 - Agent tagging work targets **Premiere markers**; do not auto-fill `editDesc` with `INT:`, `FUNI`/`funi`, or pipeline stamps.
+- Agent adds **red** markers only for its own new deliverable location/activity stamps; set **white** on agent-added `INT:` / `LORE:` only. Your descriptive stamps stay **orange**. Never bulk-recolor the user's markers.
 - Transcription aids live in **`editDesc/prtranscript/`** (per year): `*_prtranscript.txt`, `*_visual_tags.txt`, marker JSON snapshots, probe frames (`_gap_probe/`), etc. — not mixed with deliverable chapter `.txt` files.
 - `prompts.txt` rules still apply: remove `FUNI`, `INT`, `LORE`, `gamign`, and `env` lines (treat lowercase `funi` the same as `FUNI`); normalize YouTube timestamps.
 
@@ -103,12 +106,12 @@ Both bounds are deliverable chapter candidates. Do **not** use `gamign` or `env`
 | Marker family | Color | `setColorByIndex` |
 |---------------|-------|-------------------|
 | Start | Green (default) | 0 |
-| Deliverable tags (locations, tag in/out, bosses) | Red | 1 |
+| Agent-added deliverable tags (locations, tag in/out, bosses) | Red | 1 |
 | gamign, env | Purple | 2 |
-| SEG | Orange | 3 |
+| SEG; your manual descriptive stamps | Orange | 3 |
 | BEGIN, END, AFK, UNAFK | Yellow/tan | 4 |
 | INT: | White | 5 |
 | FUNI, FUNI(INT) | Blue | 6 |
 | funi | Aquamarine / turquoise | 7 |
 
-When adding markers via MCP: red = 1, white (`INT:`) = 5. Hard tags share the same yellow/tan as each other, not white.
+When adding markers via MCP: **new agent stamps** → red = 1; agent `INT:` / `LORE:` → white = 5. Do not change colors on markers you did not add.