External/beardrive

Fork 0

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

Files

T

History

33ca0caeab fix(sync): connecting a folder adopts the project's files instead of forking them (#159 )

A device's first cycle on a volume was treated as a concurrent edit for every
path the project already held. Whichever side's clock happened to sort higher
won -- so a joiner's seeded .bdriveignore or agent-written AGENTS.md could
replace the team's -- and the loser landed beside it as a
.bdrive-conflict-<device>-<time> file.

A first cycle is a join, not an edit. Cycle step 1b holds the scan's ops back
over the pull and demotes any whose path the project already holds to lamport
0, which sorts under every op a project can carry (scan's clock starts at 1).
The project's version then wins deterministically on every device, and
conflictCopies skips those ops the way it already skips re-asserted ones. The
local content is still journaled and pushed, so it stays in History and
`bdrive restore --list <path>` can bring it back. Reported as `adopted: N`.

Concurrent edits after the join are untouched.


Claude-Session: https://claude.ai/code/session_01GLCyEWP2XZhYjBssvdCDQm

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

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

cli-sync.md

fix(sync): connecting a folder adopts the project's files instead of forking them (#159 )

2026-08-12 16:10:10 -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

fix(hub): device binding is a provider contract, not a BuiltinAuth field (#147 )

2026-08-11 08:23:34 -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).