docs(status): refresh STATUS through the module substrate era

[zaridan]

STATUS.md was last updated 2026-07-12, when the engine was built but not yet live and the UI/deployment were still ahead. This brings it current with everything shipped since — every claim verified against the repo (git log, merged PRs, specs/modules/, src/db/migrate.ts), not memory.

What changed

The top-line now leads with the live, dogfooded reality (engine at desk.resonantiq.app, Agent Inbox UI at inbox.resonantiq.app, Supabase + real Gmail mailbox), and the era since 07-12 is captured under Done:

• Live deployment (HT-43) — as-deployed on Vercel + Supabase + GCP Gmail push; live-only Gmail threading bugs found and fixed (HT-49/HT-50).
• Agent Inbox UI live (HT-23, PRs fix(web): declare @types/node so web/ builds standalone (HT-23) #64–feat(web): fidelity closeout — detail skeleton, optimistic status, attachment rendering (HT-23) #66) and inbound reliability wave (HT-45–HT-48, PRs feat(mail): Gmail OAuth disconnect admin action (HT-47) #46–fix(mail): retry instead of ack on lease-held reconcile; token-scope lease release (HT-48) #49).
• Per-Agent identity, login & auth (HT-51, HT-54; PRs feat(engine): per-Agent identity, login & user management — engine layer (HT-54) #70/feat(web): per-Agent login, session identity & team management — web layer (HT-54) #71/feat(engine): mailbox-access grants + admin API; admin IA fidelity doc (HT-54) #72, migration 18) — retiring the shared operator password.
• Inbound observability (HT-44, PR feat(engine): inbound observability — health endpoint, forged-token signal, log gaps (HT-44) #73, migration 19).
• Module substrate era — open-core catalog (HT-66, PR docs(plugins): module catalog & the open-core line (HT-66) #75) and substrate v1 spec (HT-67, PR docs(modules): module substrate v1 spec — events, webhooks, assistant actors (HT-67) #76) under specs/modules/; implementation waves 1–3 (HT-68/HT-69/HT-70, PRs feat(engine): module substrate wave 1 — actor model, drafts, assistants, webhooks, event outbox (HT-68) #77/feat(engine): module substrate wave 2 — events, outbox drain, webhook delivery, admin API (HT-69) #79/feat(engine): module substrate wave 3 — assistant auth, drafts API, draft-approval (HT-70) #80, migrations 020–023 — actor model, events/webhooks, assistant auth + drafts + approval); first module scaffolded born-proprietary in Helpthread/module-draft-assistant (HT-73).

One accuracy correction worth flagging

The substrate operator guide (docs/modules/, HT-71) is PR #81 — still open, not merged, and docs/modules/ does not yet exist on main. It is therefore listed under Next, not Done. (Migrations 020–023 all landed together in wave 1 / PR #77, not spread across the three waves.)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated project status to reflect the live, dogfooded Helpthread experience with Gmail-backed threaded replies.
  • Documented the new module extension foundation, including typed events, signed webhooks, and assistant actors.
  • Refreshed details on mail delivery, inbound reliability, Agent Inbox API capabilities, deployment, and operational workflows.
  • Updated upcoming and deferred work, along with the document’s last-updated date.

[coderabbitai]

📝 Walkthrough

Walkthrough

STATUS.md is refreshed to describe Helpthread’s live mail deployment, closed-loop threading, Agent Inbox API contract, module substrate v1, operational surfaces, updated roadmap, and deferred scope.

Changes

Helpthread status documentation

Layer / File(s)	Summary
Core capabilities and contracts STATUS.md	The status narrative now documents the live mail loop, token-based threading, outbound delivery reliability, Agent Inbox v1/v1.1 behavior, and guarded PR checks.
Runtime surfaces and deployment STATUS.md	Provider adapter, deployed UI and engine, Gmail wiring, authentication, and observability descriptions are updated to reflect the current runtime.
Module substrate and roadmap STATUS.md	Module substrate v1, draft-reply assistant integration, next steps, deferred scope, and the last-updated date are revised.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• Helpthread/helpthread#24: Documents the Agent Inbox v1.1 contract details updated here.
• Helpthread/helpthread#20: Overlaps on mail-loop idempotency, delivery-worker behavior, and provider adapter status.
• Helpthread/helpthread#13: Shares updates to the closed mail loop and threading status sections.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: a STATUS.md refresh for the module substrate era.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/ht-status-refresh

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@STATUS.md`:
- Around line 9-10: Update the AI actor terminology in STATUS.md to use
“Assistants” consistently, including the prose references near the changed
“assistant” text and the additional indicated occurrences. Preserve “Agents” for
human support staff and leave any literal repository or path identifiers
unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c3702b51-b11c-4627-ad3b-7a8d86952080

📥 Commits

Reviewing files that changed from the base of the PR and between 475b60e and 23f7567.

📒 Files selected for processing (1)

• STATUS.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use “Assistants” consistently for AI actors.

These changed prose references use lowercase assistant for AI actors. Apply the required vocabulary consistently, while preserving literal repository and path names if they are identifiers.

Proposed wording

-assistant (AI) actors
+Assistants (AI actors)

-draft-reply assistant
+draft-reply Assistant

As per coding guidelines, human support staff must be referred to as “Agents” and AI actors as “Assistants”; never conflate them in schemas, code, documentation, or prose.

Also applies to: 22-25, 72-72, 76-76

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@STATUS.md` around lines 9 - 10, Update the AI actor terminology in STATUS.md
to use “Assistants” consistently, including the prose references near the
changed “assistant” text and the additional indicated occurrences. Preserve
“Agents” for human support staff and leave any literal repository or path
identifiers unchanged.

Source: Coding guidelines