Repository navigation
chore: retire the lab: archived entry, no deploy, dead Registry workflow removed - #19
Merged
Merged
Conversation
AmrMsCLL
added a commit
to Project-Graphite/graphite-hub
that referenced
this pull request
Nov 7, 2026
Phase 8 of the hub server plan: the README and `CLAUDE.md` describe what runs now. ## Changes - `README.md` replaces the prerendered-site README: React Router 8 on Express 5, SQLite and Redis, sign-in with GitHub behind `?graphite`, the `/live` stream and the `/collab` WebSocket, all read from `server/` and `app/`. What the hub does; routes from `app/routes.ts`; server endpoints from `server/app.ts` and the webhook's handling from `server/sync.ts`; sign-in and roles; storage; background work and retention from `server/main.ts` and `server/lifecycle.ts`; observability; configuration from `server/config.ts`; local run, commands, layout, CI and deployment. - `CLAUDE.md`: two dated decision records added rather than history edited, as the file asks: scheduled work is SQLite rows and a timer with no BullMQ or page cache; releases come from GitHub Releases and Message Lab's registry entry is archived (Project-Graphite/graphite-message-lab#19). The "Off limits" list no longer names `releases/` and `src/data/registry.json`, which are gone. No code changes. Prettier does not cover the root files.
AmrMsCLL
changed the title
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.
Message Lab was folded into the hub's
/messagesfeature and itsplatform/deploy/graphite-message-lab/folder is gone, but the registry entry still saidstatus: livewith a compose host. The hub's uptime probe therefore pingedmessage-lab.project-graphite.comevery 30 seconds and showed it down: the "6 of 7 up" on/status.Changes
.graphite.yml:status: archived, a value fromplatform/schema/project.schema.json; the entry stayslisted, so the showcase remains on the hub as an archived project.deploy: {kind: none}. The showcase is unchanged..github/workflows/registry.ymldeleted: it calledreusable-sync-registry.yml, which no longer exists inactions, so it failed on every.graphite.ymlpush. The registry sync runs onplatform's hourly schedule, and sooner when the hub's webhook dispatches it.README.md: the Deployment section says the lab is retired and where its feature lives now, instead of describing the old values file, the secrets repository and sleeping.Checked
platform/scripts/sync.py'sapplyrun locally against the current registry, the organisation's repositories and members:status=archived deploy={'kind': 'none'} listed=True showcase=True, 0 problems.After merge
platform's Sync registry rewritesprojects/graphite-message-lab.ymlon its next hourly run (at :17), and the hub stops probing the host on its next registry sync after that. Themainpush still publishes images; the deploy job then finds no deploy folder and records nothing, by design.