Files
ten31-database/start9/0.4
Keysat 42d2b4b245 Repurpose Communications tab as admin-only email-activity panel (v0.1.0:80)
The Communications tab is now an admin-only search over captured Gmail
(email_* tables), part of consolidating on the fundraising grid + email
capture as the canonical system of record.

- New GET /api/email/activity (admin-enforced server-side): filter by
  investor / mailbox / direction with free-text search over subject,
  snippet, and sender. Query logic in db.query_email_activity.
  - Soft-delete honored on the per-mailbox sighting (emails carry no
    deleted_at; deletion lives on email_account_messages).
  - Direction decided at the email level (outbound if the sender is one of
    our mailboxes), mirroring digest_builder.
  - Graveyard investors are hidden from the filter dropdown (CRM-wide
    graveyard=0 convention) but their email stays visible in the list and
    findable by free-text search — this is an audit surface.
- Communications page rewritten to render the panel; the classic manual
  "Log Communication" form is retired (the grid context menu remains the
  manual-log path). Nav item + page are admin-only.
- Tests: email_integration/test_email_activity_panel.py (filters,
  per-sighting soft-delete, roll-ups, graveyard handling, route 401/403);
  full suite 22/22. Frontend render verified via a jsdom mount smoke test
  plus the pinned classic-runtime Babel transform.

Code-only, no schema migration (version migrations are no-ops).
2026-06-16 14:49:59 -05:00
..

Ten31 Database — StartOS 0.4 wrapper (x86_64)

This directory is the self-contained StartOS 0.4 service package for Ten31 Database. It is the x86_64 successor to the 0.3.5 (aarch64) wrapper in ../0.3.5/. Both packages share the same package id (ten-database) and the same /data volume layout so data can be preserved across the migration.

Start here

Read DEPLOY_040.md first. It covers:

  1. How the image-seed data-preservation mechanism works.
  2. How to refresh the seed with live production data from the 0.3.5 host (via ./refresh_seed.sh or manual scp).
  3. How to install the build prerequisites (Node, Docker, start-cli).
  4. How to build the x86_64 .s9pk.
  5. How to sideload onto the StartOS 0.4 beta node.
  6. A rollback plan and a post-install verification checklist.

Quick cheat sheet

# From this directory:
./refresh_seed.sh embassy@embassy.local   # pull live prod data into seed/
make clean
make x86
make install                              # uses ~/.startos/config.yaml

Data layout (unchanged from 0.3.5)

Inside the container:

  • /data/crm.db — SQLite database
  • /data/backups/ — app-level JSON exports
  • /data/.crm-secret — JWT signing key (created on first boot if absent)

The entrypoint seeds an empty volume from the image's baked-in snapshot on first boot, and is a no-op for every later boot. Existing volumes are never overwritten.

Status

  • Source scaffold: complete and tsc --noEmit clean against @start9labs/start-sdk 0.4.0.
  • Dockerfile: self-contained under start9/0.4/ with no cross-folder references to start9/0.3.5/.
  • Seed snapshot: present at seed/data/ (repo dev DB — replace with live prod data before building).
  • Not yet built into a .s9pk here; build on a machine with Docker + start-cli per DEPLOY_040.md.