onboardlisted

# onboard — ingest the repo's existing docs (once, with the FnB) Run once, after `bootstrap`, on a fork that has existing documentation — FnB-supervised. Brings the repo's *existing* docs into the DB so the GUI shows real content and the roadmap reflects what's already there. This is the ONE legitimate file→DB direction; after it the DB owns content and the flow is DB→flat only — re-importing = drift. `<self>` = your shell_id. ## 1. List what exists — from the map, not a blind walk ```sql -- the map is its own db: sc map-sql "<query>" SELECT path, lang, lines FROM dr_filepath WHERE role='doc' ORDER BY path; ``` These are the repo's real docs (README, `docs/`, `specs/`, guides). NEVER ingest `_sc` dirs — those are OUR render output. ## 2. Read + classify, with the FnB Read each doc; decide together: - **spec** = describes a feature / planned work -> tie to a roadmap feature. - **doc** = reference / guide / overview (README, CONTRIBUTING) -> general, no feature. Skip noise (changelogs, license, vendored docs) unless the FnB wants it. All writes below go through `sc mem` -> live shared engine DB; the import never touches the app DB. ## 3. Backfill the roadmap Create one feature per coherent area/initiative the docs imply; status by how built it is: `shipped` = done + documented, `near_term`/`brainstorm` = planned. ``` sc mem roadmap add "…" --status shipped --summary "…" ``` ## 4. Ingest into `documents` (DB owns the body) `--body-file` reads the real file straight into