Container Base Image State 5

Related plan: Container Base Image Plan 5

---

• Task 1 — Update Forge_Infrastructure.md to be a complete declarative description

  • Audit every section against live environment
  • Remove/mark stale Alpine references
  • Add missing declarative sections (volume structure, Docker build details, GHCR naming, UV_SYSTEM_PYTHON)
  • Verify document is self-contained
  • Make sure all env vars, secrets, etc. and their setup are documented (including .secrets, .internal/.env, env vars in Vercel, GitHub secrets)

• Task 2 — Create Forge/Forge_Setup.md — rebuild instructions + disaster recovery

  • Part A: Disaster recovery — what to back up (MongoDB, Typesense, volume, Docker image, env vars, DNS, Vercel)
  • Part B: Step-by-step environment rebuild instructions
  • Part C: Operational gotchas from Learnings (L5–L19) only items that don’t fit anywhere else
  • Part D: Complete and detailed post-setup verification checklist
  • Verify document is self-contained — no dangling references to the project folder
  • Double check that the environment can be set up completely and cleanly using the document
  • Link to Forge_Setup.md from AGENTS.md

• Task 3 — Clear Learnings

  • Verify every Learning (L1–L20) has a permanent home

Evaluation — Plan 5

#	Type	Description	Status	Disposition
E1	Defect	Phase doc has stale historical notes below “Plans: 6”	✅ Fixed	Update — remove everything below “Plans: 6”
E2	Gap	Project_Check and Project_Complete skills not updated with backup/Typesense prompts	✅ Fixed	Update — add to both skills (don’t change Forge_Setup.md)
E3	Defect	GITHUB_TOKEN vs GITHUB_PERSONAL_ACCESS_TOKEN inconsistency	✅ Fixed	Update — rename to GITHUB_TOKEN in Infrastructure doc, Forge_Setup, librechat.yaml, and Railway env vars
E4	Gap	Active config folder / Dockerfile location unclear	✅ No change	Erik confirms Forge/Configs/ is correct — no change needed
E5	Learning	Learnings file format concern	✅ No change	Learnings correctly cleared — no problem
E6	Defect	mongodump/mongorestore not available; use Railway backups instead	✅ Fixed	Update — use Railway backups, remove mongodump, document for agent and human, verify in Part D
E7	Defect	Railway CLI not available; use Railway MCP instead	✅ Fixed	Update — reflect Railway MCP as deferred tool, verify in Part D
E8	Defect	Recovery steps not separated by execution context	✅ Fixed	Update — clarify agent vs operator machine boundary
E9	Defect	Typesense restore via snapshot API not usable	✅ Fixed	Update — use Railway backup for Typesense, eliminate snapshot API, keep reindex alternative
E10	Defect	Backup/restore verification missing from checklist	✅ Fixed	Update — add step to verify restore from Railway backup

Fix Tasks

• Fix 1 (E1) — Remove everything below “Plans: 6” in Container_Base_Image_Phase.md
• Fix 2 (E2) — Update Project_Check and Project_Complete skills with backup/Typesense prompts
• Fix 3 (E3) — Rename GITHUB_PERSONAL_ACCESS_TOKEN to GITHUB_TOKEN in Forge_Infrastructure.md, Forge_Setup.md, librechat.yaml, and Railway env vars
• Fix 4 (E4) — No change needed — Forge/Configs/ is confirmed correct
• Fix 5 (E5) — No change needed — Learnings correctly cleared
• Fix 6 (E6) — Updated Forge_Setup.md: replaced mongodump/mongorestore with Railway backups, documented enabling for agent and human, added Railway Backup Summary section, updated Part D
• Fix 7 (E7) — Updated Forge_Setup.md and Forge_Infrastructure.md: replaced Railway CLI references with Railway MCP/forge-bash, updated Part D to verify Railway MCP
• Fix 8 (E8) — Updated Forge_Setup.md: added Execution Contexts section at top, tagged all steps [Agent] or [Operator]
• Fix 9 (E9) — Updated Forge_Setup.md: replaced Typesense snapshot API with Railway backup, kept reindex alternative
• Fix 10 (E10) — Updated Forge_Setup.md Part D: added Railway Backups section, Railway Backup Restore Verification section, Railway MCP Functional section