latest

Author: roodboi

.gitignore

@@ -32,3 +32,9 @@ report.[0-9]_.[0-9]_.[0-9]_.[0-9]_.json
 
 # Finder (MacOS) folder config
 .DS_Store
+
+
+SPECS/
+_DOCS
+TODO.md
+REVIEW.md

ARCHITECTURE.md

@@ -118,10 +118,4 @@ flowchart LR
 - Docker Compose is the execution substrate for predictability and portability.
 - Caddy routes by container label so there is no per-repo reverse proxy config.
 - Logs default to `docker compose logs` for speed, with Loki for history and filtering.
-- Config lives alongside each repo in `.hack/` to keep repos isolated and portable.
-
-## Extension points (future-friendly)
-
-- Log backends could be abstracted (`compose` / `loki` today).
-- A structured JSON output mode would enable UI and MCP integration.
-- A lightweight daemon could subscribe to Docker events for near-real-time UI updates.
+- Config lives alongside each repo in `.hack/` to keep repos isolated and portable.

README.md

@@ -296,10 +296,6 @@ hack logs --project my-project --pretty
 hack up --project my-project
 ```
 
-
-
-
-
 ## .hack and valid tld requirements
 
 OAuth providers (notably Google) require `localhost` or a host that ends with a real public suffix.
@@ -329,6 +325,7 @@ outside of Caddy.
 - Other OS: run `hack global ca` to export the CA cert path, then add it to your OS/browser trust store.
 - If you need the PEM directly: `hack global ca --print`.
 - If you are running a local service outside of Caddy, use `hack global cert <host...>` (mkcert required) to generate a cert/key under `~/.hack/certs` and wire it into your service. This is only needed for non-Caddy services that still want trusted TLS.
+- macOS: `hack global install` can optionally install mkcert (needed for `hack global cert`).
 
 Install mkcert if you don't already have it (macOS example):
 
@@ -444,6 +441,13 @@ hack --help
 ```
 This builds `dist/hack` via `bun build --compile` and installs it to `~/.hack/bin/hack`.
 
+### Check which install is active
+
+```bash
+bun run install:status
+```
+Reports whether `hack` is a dev shim or a compiled binary (and where it points).
+
 
 ### Run in place
 
@@ -464,6 +468,13 @@ bun run build
 ./dist/hack --help
 ```
 
+### Build a release bundle
+
+```bash
+bun run build:release
+```
+Produces `dist/release/hack-<version>/` with `install.sh`, assets, and checksums.
+
 ### Packaging note (gum)
 
 The repo ships gum tarballs under `binaries/gum/`. In packaged builds, ship `binaries/` alongside the binary (or set `HACK_ASSETS_DIR`).