chore: bootstrap lean sysadmin-chronicles repo

Import the runnable game code, content, docs, scripts, and repo guidance while leaving local agent state, dependency installs, build output, and backup copies out of the published tree.
This commit is contained in:
2026-05-02 11:49:07 -04:00
commit 0265afa054
252 changed files with 37574 additions and 0 deletions
+44
View File
@@ -0,0 +1,44 @@
{
"id": "marcus-Q003",
"character": "marcus",
"quest_id": "Q003",
"series_id": "marcus-main",
"series_position": 3,
"messages": [
{
"stage": "intro",
"trigger": "quest_activated",
"body": "Dave's report is vague but something is wrong on hermes. I'd start by looking at resource utilization before assuming it's the application."
},
{
"stage": "hint_1",
"trigger": "player_requested_help",
"body": "Check disk. df -h is your friend. Web servers write logs constantly and nobody always remembers to set up rotation."
},
{
"stage": "hint_2",
"trigger": "player_requested_help_again",
"body": "If you find a big file, don't just delete it — figure out why it got that big. Is logrotate configured for nginx? Check /etc/logrotate.d/."
},
{
"stage": "hint_3",
"trigger": "player_requested_help_again",
"body": "The default nginx logrotate config is in the nginx package. dpkg -L nginx | grep logrotate might give you somewhere to start. Or just write a correct one — it's about ten lines."
},
{
"stage": "complete-clean",
"trigger": "world_flag:hermes_logrotate_healthy",
"body": "Nice. That was the right call — clearing the space and fixing what caused it. Logrotate problems have a way of coming back if you don't actually fix them."
},
{
"stage": "complete-norotate",
"trigger": "world_flag:hermes_log_pressure_pending",
"body": "Space is back. But if you didn't fix the rotation config that log is going to grow again. Something to keep an eye on."
},
{
"stage": "complete-down",
"trigger": "world_flag:hermes_web_down",
"body": "nginx is inactive now? That's worse than the disk problem. Restarting it without fixing why it died isn't a fix, it's a delay. Check what happened before you start it again."
}
]
}