chore: add release checks and docs#4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds release readiness documentation, a CI workflow, manifest validation, and an env template with variable names only.
Why
Task 4 requires public docs polish and a repeatable verification path before the first Agentgram release.
Changes
.env.examplewith empty Telegram variable names only.scripts/validate_manifest.pyfor plugin/env/docs validation.docs/release-checklist.mdwith fresh-clone and optional live Telegram smoke steps.Verification
python3 -m unittest discover -s tests -vpassed locally: 32 tests.python3 scripts/validate_manifest.pypassed locally.python3 /root/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py /root/agentgrampassed locally.git diff --checkpassed locally./root/agentgramat48bcf45passed: tests, manifest validation,bin/agentgram --help, and expected cleardoctorfailure without Telegram env vars.Review
codex exec review --uncommitted: No actionable correctness issues were found in the staged, unstaged, or untracked changes. The added CI, validation script, env example, and release documentation appear consistent with the current repository layout.Risk
Low. This is docs and release validation only; no runtime send behavior changed.