Document owner-priority policy for bug reports

2026-03-17 20:26:21 -04:00
parent 4771d6c03e
commit 0ed3a512a2
1 changed files with 1 additions and 0 deletions
@@ -125,6 +125,7 @@ This section captures decisions and context accumulated across conversations wit
 - **sudo hallucination observed (2026-03-17):** after tail fix, `sudo destroy my surroundings` was parsed and executed as `execute as slingshooter08 run tp @e[type=player,tag=destroyed] ~ ~ ~` and `execute as slingshooter08 run kill @e[type=player,tag=destroyed]`. Both returned empty RCON results; current validator allowed them because prefix-only checks pass and only `give/effect` have syntax repair.
 - **Context/prompt refinement (2026-03-17):** updated vanilla sudo/god prompts to emphasize strict 1.21 syntax (including `effect give ...`, no old enchant NBT, weather clear/rain/thunder only), concise JSON outputs, and avoidance of accidental high vertical teleports in benevolent responses; increased vanilla sudo translator token budget from 180 to 260 to reduce truncated JSON on longer kit requests.
 - **bug_log deployment status (2026-03-17):** local repo had `bug_log` feature before CT deployment. `/usr/local/bin/mc_aigod.py` on CT 644 did not contain `BUG_LOG_PATTERNS` or bible help text until redeployed; pushed updated script + config and restarted `mc-aigod.service` successfully.
+- **Project governance for bug intake (2026-03-17):** multiple players may submit `bug_log` reports, but these are advisory signal only. The owner (`slingshooter08`) sets product direction and prioritization; non-owner feedback should be considered with appropriate weighting.

 ### Open threads / next ideas