Skip to content

chore: reconcile shared catalog against ephemeral primary + persistent (#195) #196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StefanSteiner merged 4 commits into from
Jul 12, 2026
Merged

chore: reconcile shared catalog against ephemeral primary + persistent (#195) #196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
24db9ed
docs: track in-repo planning artifacts and superpowers/ convention
StefanSteiner Jul 12, 2026
ef07a25
test: add RED regression tests for #195 shared-catalog reconcile
StefanSteiner Jul 12, 2026
494389d
chore: reconcile shared catalog against ephemeral primary + persisten…
StefanSteiner Jul 12, 2026
efe5b2a
chore: preserve catalog prose on rename within a user-attached DB
StefanSteiner Jul 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,6 +383,11 @@ Documentation is split by audience:
- **DEVELOPMENT.md** — contributor-facing: internal architecture, design decisions, how to extend, testing
- **Source code** (`///` and `//!`) — implementation details co-located with code
- **`docs/`** — cross-cutting topics: performance, benchmarks, transactions, comparisons
- **`docs/superpowers/`** — planning artifacts kept in-repo and committed: design specs
under `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and their implementation
plans under `docs/superpowers/plans/YYYY-MM-DD-<feature>.md`. Non-trivial features are
brainstormed into a spec, then a plan, before code; keeping both in the repo makes the
design rationale reviewable alongside the change that implements it.

All public items have `///` doc comments. Module-level docs (`//!`) explain architecture and patterns. Examples are in `hyperdb-api/examples/` and tested via `run_all_examples.sh`. Companion crate examples in `hyperdb-api-salesforce/examples/` and `sea-query-hyperdb/examples/`. API docs are generated via `make doc`.

Expand Down
9 changes: 9 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# CLAUDE.md — hyper-api-rust

This project's agent guidance — architecture, build/test commands, the `hyperd`
bootstrap, conventions, and the numbered codebase-specific reminders (including
"don't invent `hyperd` flags" and "never report a test as passing without real
output") — lives in `AGENTS.md`. It is the cross-tool source of truth; this file
exists only so Claude Code auto-loads it.

@AGENTS.md
Loading
Loading