What's New in Gluecron

Every automatic fix (leaked-secret redaction, security fixes, the AI and mechanical CI repairs, post-push hygiene) now arrives as a pull request for you to review, from its own gluecron/auto-repair/ branch. Nothing is committed or force-pushed to your branches, repair pull requests are never auto-merged, and mirrored repositories are left alone. For a real leaked key you are told to rotate it, because redacting a file does not remove it from git history. What you may notice: test fixtures are no longer auto-redacted, and no repair ever marks the secret check as passed, so a repository whose tests contain key-shaped strings will see the secret check stay failed until you mark them. Add gluecron:allow-secret on each fixture line (in a comment) to clear the check. Keeping fixtures under a test path (tests/, __tests__/, fixtures/, or a *.test.* / *.spec.* file) guarantees Gluecron never proposes rewriting them, but the check still reports them until they carry the marker.

Every push runs typecheck + the full test suite on Gluecron CI, and the merge gate refuses a PR while its branch is red or still running. Non-fast-forward merges were also fixed at the resolver level.

Synthetic journeys probe the product (sign-in, session, explore), heartbeat detection notices the platform's own outages, and red probes, error spikes, failed deploys and rollbacks now notify the owner in-app and by email.

Issues, pull requests and comment threads are imported alongside git objects — single-repo and bulk — with recovery for quota-interrupted runs.

An invariant test proves every customer path works with the AI provider unreachable; AI features degrade to honest fallbacks instead of errors.

A visible pre-launch label on every page, standards-mode HTML site-wide, a single price list shared by home and /pricing, dead links resolved, and enterprise/compliance copy rewritten to what is real today versus planned for GA.

Admins can see, and revoke, every OAuth client and token that can reach their repositories. Repository slugs resolve case-insensitively across the MCP surface.

Twenty-one static rules run hourly over Gluecron's code — unguarded mutations, unawaited writes, check-then-insert races, indexes weaker than the schema declares, fetches without deadlines — and surface on /admin/selfcheck.

A CI gate that exits non-zero on drift between Drizzle and migrations, unguarded state-changing routes, or missing production configuration.

Secret scanning at push, CODEOWNERS enforced at merge, and PR workflows wired to fire on open and update.

One repo nav everywhere, grouped settings sidebar, a single admin shell, and a nav-audit tool that presses every tab on every repo to prove it renders.

New repositories start with a README, gates and labels; bulk imports are secured and scanned; the Connect Claude page points at a first real task.

Personal access tokens gained a real expiration control, and the admin token flow no longer hardcodes a seven-day life.

Three-model parallel PR review running Security, Correctness, and Style passes simultaneously — faster feedback, broader coverage.

Watch your spec become a merged PR in real time: a live progress stream shows each agent step from spec parse to gate green to merge.

Block bad commits at push time with pack-content rulesets — enforce file-size limits, banned extensions, and content patterns before the push lands.

SSH deploy to your own server directly from a merge. Register a server target in repo settings and autopilot handles the rsync.

CI runs warm from the second run. Workflow jobs can now persist dependency caches between runs, cutting install time on hot paths by up to 80%.

A pulsing Live indicator appears in the repo header whenever a push is in flight — gate runs, AI review, and deploy status update without a page reload.

Every PR branch gets an isolated preview URL. Autopilot tears down stale previews 24 hours after the branch is merged or closed.

A compact widget on /dashboard surfaces the last hour of autopilot actions across all your repos — repairs, reviews, deploys, and digest sends at a glance.

A colour-coded health score (0–100) appears in the repo header, computed from gate pass rate, stale PR count, and recent deploy success.