mirror of https://github.com/runbear-io/beardrive.git synced 2026-08-25 08:08:08 +02:00

Files

T

History

Snow LeeandClaude Fable 5 3b16ca3c74 feat(hub): deletes are tombstoned, audited, and reported to PostHog

Deleting a project no longer removes its registry row: Delete(id, by)
marks it with Deleted/DeletedBy and every live-project read path skips
tombstones, so the name is immediately reusable, no content route
answers for one, and who-deleted-what-when stays queryable — the row is
the audit record. GET /api/projects?deleted=1 lists tombstones through
the same permission resolver as the live list (hub admins additionally
see tombstones of deleted orgs, the only audience left once the
memberships are gone). Each delete also writes an audit: log line and a
project_deleted / org_deleted PostHog event through the existing
Server.capture — ids only, a no-op unless analytics is configured.

The SQL backend grows deleted/deleted_by columns via the idempotent
addColumns migration, guarded: a rolled-back deleted column would
resurrect every deleted project as live with its storage already
purged. The file backend stores the whole row and needs nothing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-16 10:00:19 -07:00

cli-sync.md

post_sync: run a local command when teammates' changes land (#163 )

2026-08-13 11:04:23 -07:00

overview.md

feat(cli,docs): say that agent skills sync, and refuse ~/.claude as a mount root (BEA-117) (#138 )

2026-08-11 05:04:12 +09:00

README.md

feat(cli): "bdrive serve" replaces "bdrive web" (web stays as an alias), and the README leads with the agent install (#94 )

2026-07-30 17:46:58 +09:00

webapp-frontend.md

feat(webapp): mermaid fences render as diagrams, in the viewer and on share pages (BEA-91) (#143 )

2026-08-10 14:18:18 -07:00

webapp-server.md

feat(hub): deletes are tombstoned, audited, and reported to PostHog

2026-08-16 10:00:19 -07:00

README.md

Architecture diagrams

Mermaid diagrams of the current implementation, kept next to the code so PRs can update them alongside the change.

Convention: when a PR changes the structure drawn here (new/removed types, new seams, changed relationships), update the affected diagram in the same PR and add an "Architecture changes" section to the PR description that, per changed diagram:

names exactly which types/relationships changed and how (one sentence);
shows a Before and an After mermaid block — each an excerpt of only the affected classes and their immediate relationships, never the full diagram (Before comes from the diagram at the merge base).

The committed diagram file stays the full current state; the before/after excerpts exist only in the PR description so reviewers see the structural delta at a glance. A pre-PR hook (.claude/hooks/check-arch-diagrams.sh) reminds Claude Code sessions when server code changed but no diagram did.

Together these cover every application package in the repo — every code change lands inside exactly one detail diagram's scope (plus the overview when the package map or cross-piece wiring changes):

overview.md — system diagram: every package and surface on one page, and how they connect
cli-sync.md — class diagram of the CLI and sync engine (cmd/bdrive + internal/{syncer,store,journal,config,daemon,agenthooks,autostart})
webapp-server.md — class diagram of the bdrive serve server (internal/webapp + its internal/remote seam)
webapp-frontend.md — module diagram of the hub's React SPA (internal/webapp/frontend/src)

Not covered on purpose: web/docs (content site, no application code) and cloud/ (private nested repo — its architecture lives there).