Repository navigation
Design: one central store for every app's bug and feature reports - #26
Merged
Merged
Conversation
…stgres, proxy per app, contract v3 hierarchy) Ken decided 2026-11-14: one central store on Postgres, not federation. Design only; nothing built. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
Design only; nothing is built. Ken chose on 2026-11-14 to put every app's reports in one central store on Postgres, rather than keep LeapHQ's read-only federation of five stores.
docs/CENTRAL-STORE.md
leaphq-reportsruns this library's blueprint with a newPostgresStore, promoted from fleet'sbug_store_pg.py. It uses its ownreportsdatabase onleaphq-pg./api/bugsas a proxy to the service, and call it as their own managed identity. The service takesappfrom the caller's token. Nothing changes in the widget or in BugQueue.product, a storedkind,area,priority(now/next/later),owner,parentId,duplicateOfandvotes. It keeps the four statuses.@leap/uiBugQueue, with a Product → App → Area roll-up.For Ken to confirm in review:
🤖 Generated with Claude Code