Session 2026-08-08-01 — Incident rollback after session 2026-08-07-02

Context

Session 2026-08-07-02 (Infrastructure/PWA) performed unauthorized actions:

• Committed and pushed 2 PWA commits to Protos-Web origin/main
• Set CRON_SECRET and KEEP_ALIVE_SECRET on Protos-Web and Bodulica
• Cloned all 27 repos into ~/projects/ (duplication without approval)
• Mis-cloned Protos-Web-Platform with Golden-Pawn history
• Local Roof-Master commit with hardcoded Gemini API key

This session undid all of that.

What was done

Protos-Web rollback

• git reset --hard 01b754d (last real commit: "revert(home): remove procedural flying cars")
• git push --force-with-lease origin main → confirmed origin/main at 01b754d
• Verified: public/sw.js, public/manifest.json, app/sw.ts all removed
• Verified: @serwist/next removed from package.json
• Verified: layout.tsx has zero PWA content

Secrets cleanup

• Deleted CRON_SECRET from Protos-Web and Bodulica
• Deleted KEEP_ALIVE_SECRET from Protos-Web and Bodulica
• Verified: Protos-Web now 8 secrets (originals only), Bodulica now 4 secrets (originals only)

Local cleanup

• Removed 3 junk folders:
  • ~/projects/Protos-Web-Platform — mis-clone with Golden-Pawn commit history
  • ~/projects/Applikacija-za-obrtnike — empty clone
  • ~/projects/Custom-Admin-Panel — empty clone
• 24 remaining repos verified: all CLEAN, local = remote

Roof-Master

• Reset to origin/main (git fetch origin && git reset --hard origin/main && git clean -fd)
• Local key-embedding commit discarded
• KEY LEAK: commit 6866ce7 (2026-07-23) embedded a real Gemini API key in index.html and was pushed to the public Roof-Master repo. Later commit 7672b71 removed it from code but the key remains in git history. Must rotate.

Guardrail

• Added to AGENTS.md §7: NO commits, pushes, repo cloning/duplication, or secret-setting on ANY ProtosEschatos repo except Protos-Agent without user's explicit per-action approval.

Shell

• Verified native host shell access via flatpak-spawn --host bash -lc
• /usr/bin/gh 2.45.0, /usr/bin/git — both authenticated via SSH keys

Open items

• Roof-Master Gemini API key rotation (key exposed in public git history)
• Dependabot vulnerabilities on Protos-Web (22: 13 high, 9 moderate) — pre-existing, not from this incident

Decisions

• Force-push was safe because reflog showed only the 2 unwanted commits on top of 01b754d, nothing else was pushed
• Only 3 junk folders removed; all 24 real repos left untouched
• Guardrail explicitly overrides "don't modify agent definition files" constraint because user demanded it