coffee

This repo is the working area for the DE1 plugin path.

The current inner loop is the native macOS Decent app, not the tablet. We use the desktop app to iterate on plugin loading, settings UI, release install behavior, and basic Tcl runtime issues before doing final device testing.

Current plugin setup

• plugins/cmo_updater/ A CMO-specific updater plugin for the main CMO plugin.
• plugins/de1-plugin-cmo/ Git submodule for the main plugin repo at jeffbean/de1-plugin-cmo.
• scripts/macos-plugin-sync.sh Copies local plugin directories into the Decent app plugin folder.

Today the updater can:

• optionally pin a specific release tag, or default to latest
• check a release
• install a release into the local Decent plugin directory
• persist installed version state with an install receipt
• prompt for restart and exit the app after a short delay

Current macOS workflow

The primary local harness is the Decent macOS app bundle plugin directory:

/Applications/Decent.app/Contents/Resources/de1plus/plugins

Typical loop:

1. Edit the plugin in this repo.
2. Sync it into the Decent app:

scripts/macos-plugin-sync.sh \
  --dst "/Applications/Decent.app/Contents/Resources/de1plus/plugins"

3. Quit and reopen the Decent app.
4. Open the plugin settings page in Extensions.
5. Use Check release or Install release.

For the main plugin release path:

1. Update plugins/de1-plugin-cmo/.
2. Commit and push in the submodule repo.
3. Publish a GitHub release in jeffbean/de1-plugin-cmo.
4. Use the updater to install that release locally.

Current updater page shape

The updater settings page is intentionally minimal for now:

• Repository
• Release
• Checked
• Installed
• Status
• Last error

This is currently a manual install flow. We removed the extra timestamp-heavy detail for now.

Other project areas

• src/coffee_ingest/ Python ingestion tooling for local DB inspection and sync work.
• apps/receiver/ Go backup receiver service for future plugin payload ingestion.
• docs/ Working notes and current setup docs. The active local workflow is docs/macos-plugin-loop.md.

Notes

• Treat the macOS app as the primary development loop.
• Treat the tablet as later integration testing.
• Keep the updater simple and durable first.
• Keep CMO safe while bootstrapping the update path.