[gino-m]

Collect One review series: C01 Repo scaffolding (1/60)

Tracking issue: #2629 · Stacked on: c1 · Reviewer: @rfontanarosa
FYI: @gino-m @shobhitagarwal1612

Context

Collect One is the Kotlin Multiplatform successor to Ground: a single shared codebase for the web console, the mobile app (Android, iOS, browser), and a Spanner-backed user-data service. Forms use ProtoForms, a lossless proto3 encoding of ODK XForms.

The work happened on wip/baobab, which is now frozen at collect-one-review-base (b7fd5917). Rather than replaying its 236 iterative commits, the series lands the final tree as 60 path-disjoint slices. Each slice is a PR stacked on the one before it, so every diff shows only that slice's files. Slices merge (squash) into the integration branch c1, which starts empty. master keeps shipping Ground 1.0 and isn't touched by this series. #2629 has the full queue, dependency graph, and reviewer assignments.

This first PR adds only top-level repository files, so that the other PRs have a README, contributor guidelines, formatting tooling, and CI to build on.

What's in this PR

• README.md: overview of Collect One, directory structure, and how the shared modules, platform hosts, server, and dev tools fit together.
• shared/README.md: table of the shared modules (protos, core, ui, map, app, web, mobile) and their dependency layering.
• GEMINI.md: contributor and agent rules for the repo: open-source purity, Apache 2.0 headers, KMP module placement, Material 3 / Compose Multiplatform usage, and the ProtoForms ↔ XForms compatibility boundary (ODK XForms spec first, then ODK Entities, XLSForm, OpenRosa, W3C XForms / XPath 1.0).
• LICENSE (Apache 2.0), AUTHORS, .gitignore.
• scripts/ktfmt.sh: pinned ktfmt (Google style) check and fix across all of the repo's independent Gradle builds.
• scripts/buf-format.sh: pinned buf format check and fix for shared/protos.
• .github/workflows/check.yml: CI check job (ktfmt + buf) on every PR.

Where it fits

Foundation for every other slice. Later PRs add the modules that the READMEs describe, and new modules wire their own CI jobs into check.yml (the server job comes back in S1).

Not in this PR

• Product docs, terminology, and UX guidelines → D1
• Proto schemas → P1–P3; Kotlin modules → K*, U*, M1, A*, W*, MB*; server → S1–S4; hosts → H1–H3; dev launchpad and e2e tests → E1–E2

Suggested reading order

1. README.md and shared/README.md (orientation)
2. GEMINI.md (the conventions later PRs follow)
3. scripts/ktfmt.sh, scripts/buf-format.sh, .github/workflows/check.yml

Focus areas

• Are the conventions in GEMINI.md (module placement, theming, ProtoForms compatibility rules) the ones we want to hold reviews to?
• CI: is ktfmt + buf on every PR the right baseline? Module build/test jobs arrive with their modules.

Safe to skim

• LICENSE, AUTHORS, .gitignore

Size

Source	Tests	Data	Files
~860	0	0	9

Testing

bash scripts/ktfmt.sh --check: PASS (no Kotlin files yet). CI: check.

Deviations from the frozen tree (CI wiring only, needed because c1 starts empty):

• check.yml: added c1 to on.push.branches.
• check.yml: the buf step runs only once shared/protos/**/*.proto exists (scripts/buf-format.sh fails without it; protos land in P1).
• check.yml: the server tests job is left out until the server lands (S1).

[gemini-code-assist]

Code Review

This pull request establishes the initial scaffolding, documentation, and formatting scripts for the Collect One project, including the project guidelines, licensing, and shared module structure. The review feedback is highly constructive and should be addressed: it suggests adding a directory check to buf-format.sh to prevent failures when shared/protos is missing, pruning the .git directory in ktfmt.sh to optimize file searches, and correcting target platform inconsistencies for the shared/mobile module within shared/README.md.