Repository navigation
feat(tools): Repo Control — Discord Activity + Clerk contributor web - #382
Merged
Merged
Conversation
Add an isolated tools/repo-control package with snapshot analysis, capability probes, Graphify drill-in, private auth UI, and Discord Activity (view-only) docs plus a separate Render blueprint. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
telivity-otaip
marked this pull request as ready for review
October 15, 2026 20:56
Keep auth as env-only; do not document literal placeholder token values. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
cursor
Bot
changed the title
Reframe README and Discord setup so the HTTP host is Activity plumbing only, not a standalone hosted dashboard. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Add Clerk sign-up/sign-in for view-only web report access alongside Discord Activity. Discord proxy read stays Activity-scoped; arbitrary browsers require Clerk when configured. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
cursor
Bot
changed the title
Document env var names only; real Clerk/Discord secrets stay out of git. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Keep secrets out of git; Activity SDK can resolve Application ID from /api/public-config when Vite bake is missing. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Creates a repo-control voice channel once the bot is invited to a guild. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
NODE_ENV=production skips devDependencies, which broke rebuilds that need tsx and vite. Document the live Activity origin and invite URL. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Render CI uses frozen-lockfile; keep lock in sync after moving build tools into dependencies. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Bot invite alone does not list the app; URL mapping, Enable Activities, supported platforms, and Developer Mode are required. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
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
2 participants
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.
Summary
Private Repository Control dashboard for HAIP: snapshot-based analysis, Telivity UI, Discord Activity (view-only), Clerk contributor read access.
Hosted Activity origin (live)
/api/healthOK; Clerk + Discord client id wired; direct/api/snapshotreturns 401 (auth required); Discord proxy read enabled viaREPO_CONTROL_DISCORD_PUBLIC_READ.env(not in git)Discord — do these in the portal
549756863504= Manage Channels, View Channels, Connect, Use Embedded Activities):https://discord.com/oauth2/authorize?client_id=1560400786767220806&permissions=549756863504&integration_type=0&scope=bot%20applications.commands
/→telivity-repo-control-v2.onrender.com(nohttps://)After the bot is in the server, channel setup:
node tools/repo-control/scripts/discord-setup-channel.mjsFix in this branch
Render production installs skip
devDependencies;tsx/viteare now production deps + lockfile refreshed.