Once the app has a repo, auth, and a live URL, the next bottleneck is maintenance. Beginners often get stuck manually editing files, guessing what changed, or trusting an agent without a rollback plan. Vibe Coding 301 teaches the repo maintenance protocol for your deployed Cypher Camp Telegram agent. The agent gets SSH access to the learner-owned GitHub repo, then works from scoped task briefs instead of vague wishes. You learn how to ask for a small change, read the diff, verify the branch, merge or push to main only when the proof is clean, and watch Vercel auto-deploy production.
The named mechanism is the Agent Maintenance Loop: scoped task brief, SSH repo access check, generated branch or diff, human review, main deploy, production smoke test, and rollback receipt. The course keeps power and safety together. The agent can do anything the repo permission allows, so the operator must give clear boundaries, require diff evidence, avoid secrets in chat, and know the revert path before shipping. By the end, your Telegram agent is not a toy chatbot. It is a repo maintainer with a repeatable support runbook, a GitHub proof trail, a Vercel deploy receipt, and a rollback checklist you can use when a change is wrong. The first hour gives you a safe agent task checklist today, then this week you reuse the same maintenance framework, review process, rollback protocol, and deploy scorecard for every repo change.
Path continuity note: 100 taught the web layers, 101 created the owned URL, and 201 added auth and memory. 301 is the safe maintenance bridge. The learner is no longer asking whether an app can exist or remember. The learner is asking how to let a Telegram agent change the repo without breaking the URL, auth, user data, deploy config, or rollback path.