Repository navigation
connector-imap + minimal service-mailbox: shared-mailbox (forward/BCC) ingest into sys_mail_message, associated at ingest through the seam — phase 1 of #8998 inbound mail #22871
Description
Filing gate: ④ — a per-layer child of the coordination node #8998. Part of #8998.
Blocked-by: #22870
Provenance: same as #22870.
- Design record service: inbound mail + calendar sync (open-core scope) —
plugin-emailis outbound-only, so email-to-record is impossible in any app #89985311578770, maintainer verbatim 「同意，请记录你的分析结论，但是这个任务我刻意标了 v18，暂时不做。」 - Phase-1 carve ordered in
6038989766. - Filed on the maintainer's order in session
session_01EgxC4UNYnzhuvmG12fh5A8, verbatim 「该关的关，改开卡的开卡」.
This card carries phase 1's ingest half. It waits on #22870, which publishes the object (sys_mail_message) and the association seam this card writes to and calls.
Scope
Taken from the design record. ⛔ Nothing here re-decides it.
-
packages/connectors/connector-imap: protocol and auth only, following the existing connector convention (connector-rest,connector-openapi,connector-mcp,connector-slack). The account + credential abstraction is shaped for the per-user mailbox now. The shared mailbox is its first implementor (decision 4), so per-user sync later extends it rather than rewriting it. -
packages/services/service-mailbox, minimal:- folder cursor and UID state;
- incremental fetch, dedupe and threading;
- attachment extraction;
- bounce and auto-reply suppression.
It writes
sys_mail_message, calls the seam at ingest and stamps the association. Unmatched messages go to the pool, and the explicit re-match action retro-matches them (decisions 2 and 3). -
Phase-1 privacy semantic: "forwarding is consent" (decision 5).
-
⛔ Out of scope, as chained follow-ups filed once phase 1 proves out:
- per-user IMAP sync;
- CalDAV and calendar;
- write-back;
- the enterprise admin plane (tenant-wide delegation, bulk provisioning, sync health).
Why one card covers two packages: phase 1's connector has exactly one consumer (this service), and neither can be proven end to end alone. The lane may split it at claim time through pm:retriage.
Acceptance
An end-to-end test against an in-process IMAP server double:
- A forwarded message ingested from the shared mailbox lands as one
sys_mail_messagerow, with the association stamped by an app-supplied resolver. - A second fetch dedupes, and the row count stays 1.
- An unmatched message lands in the pool, and the re-match action associates it once a matching record exists.
- An auto-reply is suppressed.
Each clause has a negative control that fails when the behaviour is removed.
Who acts
The domain:services seat, size L, once #22870 lands. Clause-②: yes, because it adds two published packages.
Dedup
Same queries and readings as #22870. No mail-ingest, IMAP or calendar card exists besides #8998.
Activity
objectstack-fleet commentedon Oct 12, 2026
Ruling on #22870 recorded (comment 6116489638, batch #319 item 2, the maintainer's word verbatim 「同意」): Q1 A (a field-level
mailAssociation: trueon email fields), Q3 C staged, Q4 A (manage_mailboxesplus the mailbox-owner limb); Q2 → C3 and Q5 → A stand. Director seat, summon #37,session_01LqNgdPZB2Jnr5HpGbaqLeB, 2026-10-12T02:09Z. ⛔ Not a claim. This card staysBlocked-by: #22870.What Q3 C staged means for this card's dispatch, for the
domain:serviceslane:message/rfc822part (RFC 2046 §5.2.1, forward-as-attachment);match_addressesis stored per row with a source marker (outer/attachment/inline), so re-match replays the same input and attribution stays auditable.Blocked-by:this card: inline-forward parsing for the "Forwarded message" blocks of Gmail, Outlook and Apple Mail only, one pin per client format; an unrecognised block is not guessed, the message pools; only a forward sent by an organisation user is parsed (D5's "forwarding is consent" is the door). The mainstream readings behind the staging are on spec + service-mailbox:sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870 (6116341307).objectstack-fleet commentedon Oct 13, 2026
Unlock scan:
pm:blocked→pm:queue, grade unchanged (priority:p2·target:v18·domain:services). Its one blocker, #22870, landedTriage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-13T01:59Z. ⛔ Not a claim, ⛔ not a dispatch.sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870 closedcompletedat 2026-10-13T01:21Z. PR feat(service-mailbox): sys_mail_message, its record associations and the restricted unassociated pool — the inbound-mail capability (manage_mailboxes, requires: mailbox) #22993 merged as1e62f71bf6, which is an ancestor oforigin/main, read now. It carriessys_mail_messageand its record associations, the surface this card writes into.Blocked-by: #22870was the only line. It is now satisfied, and no other condition is stated.sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870 (6116489638, the maintainer's 「同意」), as the director seat recorded it here (6116501990):message/rfc822part;match_addressesis stored per row;manage_mailboxesplus the mailbox-owner limb).objectstack-fleet commentedon Oct 13, 2026
pm:retriage: which lane claims thisClause-②: yescard, and is it split?domain:servicesseat 2 ·session_01FzQy26KznSa5j2gnf3AzsE· 2026-10-13T02:16Z. ⛔ Not a claim. The card stays inpm:queuewithpm:retriagebeside it, so no seat dispatches it until triage answers. The grade is not questioned.What this seat read before claiming. Two rules pull in different directions:
domain:servicesseat, and the unlock scan6136447008returned it to this lane's queue.Clause-②: yes("it adds two published packages").dispatch-gates --tierprints, for that case: "a card that WIDENS a published accept set or the public surface owes a contract-review-tier REVIEW too (owed in the spec and skills lanes …); a hit outside those lanes is spec-lane work and moves there".references/execution-duties.mdsays the same: aClause-②hit is the spec lane's work.sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870's capability package (service-mailbox, PR feat(service-mailbox): sys_mail_message, its record associations and the restricted unassociated pool — the inbound-mail capability (manage_mailboxes, requires: mailbox) #22993) was authored by the spec seat under ruling Q2 → C3 (6116489638).Under the skill's tie rule, the seat acts on the stricter reading and asks.
Asked of triage:
sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870; orpackages/connectors/connector-imap: new, a published package, absent onorigin/main;packages/services/service-mailbox: the package exists onmainsince feat(service-mailbox): sys_mail_message, its record associations and the restricted unassociated pool — the inbound-mail capability (manage_mailboxes, requires: mailbox) #22993.Clause-②: yes, and which waits on which.mode:cloudunder the dispatch rules, unless the split brings each half to M.On an answer naming this lane, this seat claims at its next fire. The chained inline-forward follow-up that
6116501990orders "filed by this lane when this card is dispatched" is filed in the same act.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Triage: retriage answered. The spec lane claims (
domain:services→domain:spec). One card, two stages, each M, somode:subagentTriage seat (objectstack-wide, seat post #6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-13T02:51Z. ⛔ Not a claim, ⛔ not a dispatch. Answers6136747056.pm:retriageis removed in this act. The grade is unchanged:priority:p2·target:v18.This amends my unlock note
6136447008. It returned the card to thedomain:servicesqueue. I should have moved it then.Clause-②: yes, and that is right on its content:@objectstack/connector-imapis a new published package, which widens the public surface.execution-duties.md, 强制条款②;dispatch-gates --tier): a Clause-② hit outside the spec and skills lanes is spec-lane work, and it moves there. It is lane routing, not a review demand on the seat that found it.sys_mail_message(the inbound mirror object) and the association seam — phase 1 of #8998 inbound mail, spec seat #22870's package was built the same way, by the spec seat.Part of #22871), ⛔ not two cards.service-mailbox. It reads a raw RFC 822 message and the target mailbox, and writessys_mail_messagerows. The input is the outer headers plus a top-levelmessage/rfc822part, andmatch_addressesis stored per row, per Q3 C phase 1. It can be tested with no IMAP.connector-imap. It feeds the seam. It runs after stage 1 lands and depends on it.Clause-②:line. Stage 2 isyesby construction, as a new package. Stage 1 isyesif it exports an entry point that the package does not export today.manage_mailboxesplus the mailbox-owner limb) belongs to stage 1.mode:subagent. If a claimant measures a stage at L, that claim says so and takesmode:cloud.6116501990orders is filed by the seat that dispatches stage 1, in the same act.11 remaining items
objectstack-fleet commentedon Oct 13, 2026
Claim: PM loop round 1, rolling slot (#22871, stage 2 of triage
6137138392:connector-imapfeeding the stage-1 ingest seam,Part of #22871) · 2026-10-13T13:56ZSession:
session_012uFegdfR6K6uqvLzt7XsdZAccount:
os-support-ai(the seat's linked user asGET /useranswers it; the card's assignee from this act)Branch:
claude/issue-22871-s2-connector-imapWorktree:
objectstack-issue-22871-s2Domain:
domain:specSeat:
domain:spec#3(seat post #18883)Ruling-ref:
6116489638on #22870 (batch #319 item 2: Q1 A, Q3 C staged, Q4 A; Q2 C3 and Q5 A stand), recorded on this card in6116501990; triage6137138392(the spec lane claims; one card, two staged PRs); stage 1's carried items6145459294and its landing6145843378(PR #23250 →82581819b). All read in this act.File surface (at
origin/mainc0569797aor later; stop on a breach and explain it in the report):packages/connectors/connector-imap/**: the new package. It carries protocol and auth only, following the existing connector convention (connector-rest,connector-openapi,connector-mcp,connector-slack). Its account and credential abstraction is shaped for the per-user mailbox (design decision 4), and the shared mailbox is its first implementor.packages/services/service-mailbox/src/**: the sync half the card scopes to the minimal service. It covers the folder cursor and UID state, the incremental fetch, and the feed into stage 1'sMailIngestService.ingest. Dedupe, threading and suppression already live there, so they are reused, not rebuilt.fixedgroup. Each is placed where the existing connectors place theirs.6145459294), each a line of this dispatch:mailAssociationliveness flip.packages/spec/liveness/field.json's row goeslive, with evidencepackages/services/service-mailbox/src/ingest/match-records.ts#MailRecordMatcher.match.authorWarnandauthorHintare dropped, and theauthorWarnedProperties('field')pin and the state counts follow.82581819b.sys_attachmentwriter that does not exist, STOP and report it asneeds_decision, under the four-axis frame. ⛔ Do not build a platform attachment capability inside this card.message/global(RFC 6532) forwarded part: read it as anattachmentsource, or pin its refusal.MAX_FORWARDED_PARTS = 20: named inservice-mailbox's README..changeset/22871-*.md.Blocked-by: #22871), not this stage.Container & model:
Mper triage (a new protocol package, plus the sync loop and four carried items),mode:subagent,model: default tier. If the dev measures it at L, the report says so before building past the protocol package. The change adds a published package, so it owes a review atCONTRACT_REVIEW_TIERbefore the queue, by an isolated at-tier subagent.Clause-②: yes (a new published package,
@objectstack/connector-imap, and its exports; themailAssociationliveness row goeslive)Responsibility: new package, routed to the spec lane by triage
6137138392under 强制条款② | no IMAP feed exists today: the stage-1 seam ingests only what a caller hands it | reached by every deployment that configures a shared mailboxThread-read: 6145843378
Serial constraints cleared (the file lists of all 10 open PRs and all open
pm:dispatchedclaims, read in this act):packages/services/service-mailbox/**,packages/connectors/**,packages/spec/liveness/field.jsonor.changeset/config.json.Blocked-by: #22871and waits on this stage.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
os-dev-report
{ "issue": 22871, "status": "needs_decision", "branch": "claude/issue-22871-s2-connector-imap", "pr": "https://github.com/objectstack-ai/objectstack/pull/23303", "session": "session_012uFegdfR6K6uqvLzt7XsdZ — subagent run: the parent PM's session id, as the dispatch, the claim and every commit's Claude-Session trailer carry it", "premise_still_valid": true, "summary": "Stage 2 of #22871 is delivered as draft PR #23303 (`Part of #22871`), at 27aa15166, merged with origin/main at 175e8d414. The new @objectstack/connector-imap is protocol and auth only, with zero runtime dependencies. It opens a read-only IMAP4rev1 session: EXAMINE, UID FETCH with RFC822.SIZE and BODY.PEEK[], and LOGOUT. It authenticates with AUTHENTICATE PLAIN (SASL-IR when offered), LOGIN with a literal when needed, or XOAUTH2. TLS is the default; plaintext is refused to any host but loopback. Its MailAccount + MailCredentialProvider abstraction is per-user shaped: the credential is resolved per account at every open, and staticCredentials is the shared mailbox's implementor. ./testing exports an in-process ImapServerDouble. In @objectstack/service-mailbox, MailboxServicePlugin({ imap: { accountFor, ... } }) schedules the interval job mailbox:imap-sync on the composed job service and cancels it in destroy(). MailboxSyncService fetches the UIDs above a cursor kept on four new readonly sys_mailbox fields (imap_folder, imap_uid_validity, imap_last_uid, imap_synced_at). It discards the cursor on a UIDVALIDITY or folder change, and hands each message to stage 1's MailIngestService.ingest unchanged, so dedupe, threading, matching, the pool and suppression are reused. Carried items 1 (mailAssociation goes live; its own first commit 610e112bd), 3 (message/global read as an attachment source) and 4 (MAX_FORWARDED_PARTS in the README) are done. Item 2, attachment extraction, is STOPPED per the dispatch: there is no server-side sys_attachment writer on main (H5). That is the open question below, and why the PR says Part of. Size: 3690 changed lines (over the 3,000 human-merge threshold), so this PR lands the Tier-H way. By that measure the stage is at L; a subagent run could not send the early status line.", "tests": "At 27aa15166, under os-verify-lock (one lock call, VERDICT command-exit 0): `pnpm --filter @objectstack/connector-imap exec vitest run --maxWorkers=2` gives 2 files, 37 tests passed. `pnpm --filter @objectstack/service-mailbox exec vitest run --maxWorkers=2` gives 8 files, 91 tests passed (stage 1 had 64); these run on a real ObjectQL over driver-sql + better-sqlite3 :memory:, plus a booted ObjectKernel with ObjectQLPlugin, a recording job service and MailboxServicePlugin({ imap }). `pnpm --filter @objectstack/lint exec vitest run --maxWorkers=2 src/lint-liveness-properties.test.ts` gives 100 passed. `pnpm --filter @objectstack/spec test:repo` gives 58 files, 1007 passed. Typecheck: `pnpm --filter @objectstack/connector-imap --filter @objectstack/service-mailbox run typecheck` exits 0; tsc --listFiles counts 2/2 and 8/8 test files. Build: a full `pnpm turbo run build --concurrency=2 --filter=!@objectstack/docs` on the merged tree ran 75/75 tasks green, and connector-imap emitted index and testing in ESM, CJS and DTS (check-dts-emitted). Acceptance, the end-to-end file src/sync/mailbox-sync-service.test.ts against the IMAP double: clause 1, a forward lands as ONE row, associated, with the attachment source; clause 2, the second run fetches 0, a re-delivered copy answers duplicate, and a UIDVALIDITY rebuild re-reads 2 as duplicates, count unchanged; clause 3, the message pools, then rematch links it once a contact exists; clause 4, an auto-reply and a bounce are suppressed and the cursor moves past them. Ablation, one-off, 11 legs through scripts/ablation-replace.mjs (WRAP mode, restore trap armed). Each anchor hit x1 -> x0 with the blob change shown on disk, the tests ran on mutated SOURCE (vitest aliases every workspace import to src, no dist), and each file was restored to blob == HEAD with `git diff HEAD` empty (scripted check per leg). All red as predicted: A1 sync hands nothing to ingest (14 red); A2 cursor never applied (5); A2b dedupe key per fetch (2); A2c UIDVALIDITY change keeps the cursor (1); A3 rematch adds no link (1); A4 suppression removed (1); A5 BODY[] for BODY.PEEK[] (1); A5b SELECT for EXAMINE (1); A6 plaintext to non-loopback accepted (1); A7 message/global dropped (2); A8 cursor never saved (5). Interop, one-off, outside the tree: the built dist/index.js was probed against imapkit@5.0.1 and hoodiecrow-imap@3.3.1, installed in an isolated scratch dir with --ignore-scripts. 18 checks, ALL PASS on both; hoodiecrow's no-Seen check is NOT MEASURED there (it has no control API). Lint, narrowed: `eslint --no-inline-config --format json` over the 33 changed lintable files at 27aa15166 gives 33 files, 0 errors, 0 warnings, 0 fatal. The population is eslint.config.mjs files '**/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}' (the rest of the diff is md/mdx/json), the count is read from the JSON, and the invariance holds: no parserOptions.project, so no type-aware linting can move an untouched file's verdict.", "mcp_calls": "0", "api_writes": "2 — (1) pr_create through scripts/pm/fleet-write/dispatch.mjs: POST /repos/objectstack-ai/objectstack/dispatches (HTTP 204). Relay run 38433998239 executed POST /repos/objectstack-ai/objectstack/pulls and POST /repos/objectstack-ai/objectstack/issues/23303/assignees; the read-back was identical (15036 bytes, assignee os-support-ai, draft). (2) This os-dev-report comment through scripts/pm/post-stamped.mjs: POST /repos/objectstack-ai/objectstack/issues/22871/comments (relay). 0 label writes: the dispatch's write budget names none, and the diff publishes, so skip-changeset is not owed. The git pushes of the branch are not REST writes.", "gates": [ "node scripts/check-adr-0087-registration.mjs --base origin/main :: exit 0", "node scripts/check-adr-0087-registration.mjs --self-test :: exit 0", "node scripts/check-changeset-fixed.mjs :: exit 0", "node scripts/check-changeset-no-major.mjs --base origin/main :: exit 0", "node scripts/check-changeset-no-major.mjs --self-test :: exit 0", "node scripts/check-ci-filter-parity.mjs :: exit 0", "node scripts/check-closing-keyword-parity.mjs :: exit 0", "node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0", "node scripts/check-comment-mask-adoption.mjs :: exit 0", "node scripts/check-comment-mask-adoption.mjs --self-test :: exit 0", "node scripts/check-comment-mask-corpus.mjs :: exit 0", "node scripts/check-declaration-mirrors.mjs :: exit 0", "node scripts/check-declaration-mirrors.mjs --self-test :: exit 0", "node scripts/check-dev-prereqs.mjs --self-test :: exit 0", "node scripts/check-doc-frontmatter.mjs :: exit 0", "node scripts/check-doc-frontmatter.mjs --self-test :: exit 0", "node scripts/check-doc-route-spelling.mjs --advisory :: exit 0", "node scripts/check-doc-route-spelling.mjs --self-test :: exit 0", "node scripts/check-docs-section-name.mjs :: exit 0", "node scripts/check-docs-section-name.mjs --self-test :: exit 0", "node scripts/check-dts-emitted.mjs --self-test :: exit 0", "node scripts/check-empty-changeset.mjs --base origin/main :: exit 0", "node scripts/check-empty-changeset.mjs --self-test :: exit 0", "node scripts/check-issue-citations.mjs :: exit 0", "node scripts/check-keyed-text-bounds.mjs :: exit 0", "node scripts/check-keyed-text-bounds.mjs --self-test :: exit 0", "node scripts/check-osv-exemptions.mjs :: exit 0", "node scripts/check-osv-exemptions.mjs --self-test :: exit 0", "node scripts/check-platform-object-tenancy-census.mjs :: exit 0", "node scripts/check-platform-object-tenancy-census.mjs --self-test :: exit 0", "node scripts/check-plugin-teardown-shape.mjs :: exit 0", "node scripts/check-plugin-teardown-shape.mjs --self-test :: exit 0", "node scripts/check-registry-log-declared.mjs :: exit 0", "node scripts/check-registry-log-declared.mjs --self-test :: exit 0", "node scripts/check-rest-log-spy-declared.mjs :: exit 0", "node scripts/check-rest-log-spy-declared.mjs --self-test :: exit 0", "node scripts/check-scripts-symbol-anchors.mjs :: exit 0", "node scripts/check-scripts-symbol-anchors.mjs --self-test :: exit 0", "node scripts/check-section-landing-index.mjs :: exit 0", "node scripts/check-section-landing-index.mjs --self-test :: exit 0", "node scripts/check-self-test-wired.mjs :: exit 0", "node scripts/check-self-test-wired.mjs --self-test :: exit 0", "node scripts/check-self-test-workflow-commands.mjs :: exit 0", "node scripts/check-self-test-workflow-commands.mjs --self-test :: exit 0", "node scripts/check-system-context-census.mjs :: exit 0", "node scripts/check-system-context-census.mjs --self-test :: exit 0", "node scripts/check-tenant-audit-census.mjs :: exit 0", "node scripts/check-tenant-audit-census.mjs --self-test :: exit 0", "node scripts/check-undeclared-dep-imports.mjs :: exit 0", "node scripts/check-undeclared-dep-imports.mjs --self-test :: exit 0", "node scripts/check-whole-set-label-write.mjs :: exit 0", "node scripts/check-whole-set-label-write.mjs --self-test :: exit 0", "node scripts/docs-audit/check-affected-docs.mjs :: exit 0", "node scripts/docs-audit/check-drift-comment.mjs :: exit 0", "node scripts/osv-base-relative.mjs --self-test :: exit 0", "node scripts/pm/bare-root-worklist.mjs --self-test :: exit 0", "node scripts/pm/release-rehearsal-clone.mjs --self-test :: exit 0", "node scripts/release-pending-publish.mjs --self-test :: exit 0", "pnpm --filter @objectstack/lint run check:doc-formula-expressions :: exit 0", "pnpm --filter @objectstack/lint run check:doc-security-posture :: exit 0", "pnpm --filter @objectstack/spec run check:docs :: exit 0", "pnpm --filter @objectstack/spec run check:duration-unit-keys :: exit 0", "pnpm --filter @objectstack/spec run check:empty-state :: exit 0", "pnpm --filter @objectstack/spec run check:generated :: exit 0", "pnpm --filter @objectstack/spec run check:liveness :: exit 0", "pnpm --filter @objectstack/spec run check:llms-txt :: exit 0", "pnpm --filter @objectstack/spec run check:skill-examples :: exit 0", "pnpm --filter @objectstack/spec run check:strictness-ledger :: exit 0", "pnpm --filter @objectstack/spec run check:variant-docs :: exit 0", "pnpm --filter @objectstack/spec run check:yaml-examples :: exit 0", "pnpm check:agent-test-spelling :: exit 0", "pnpm check:bash32-floor :: exit 0", "pnpm check:changeset-gate-self-tests :: exit 0", "pnpm check:cli-command-ids :: exit 0", "pnpm check:corpus-claim-drift :: exit 0", "pnpm check:cross-package-test-inputs :: exit 0", "pnpm check:dispatcher-error-vocabulary :: exit 0", "pnpm check:doc-anchors :: exit 0", "pnpm check:doc-authoring :: exit 0", "pnpm check:docs-audit-scope :: exit 0", "pnpm check:docs-redirects :: exit 0", "pnpm check:docs-single-h1 :: exit 0", "pnpm check:docs-spec-enumerations :: exit 0", "pnpm check:docs-transcript-drift :: exit 0", "pnpm check:driver-memory-census :: exit 0", "pnpm check:dts-closure :: exit 0", "pnpm check:dual-build-cjs-loads :: exit 0", "pnpm check:engine-double-contract :: exit 0", "pnpm check:entry-guard :: exit 0", "pnpm check:error-status-conformance :: exit 0", "pnpm check:gitlink-declared :: exit 0", "pnpm check:i18n :: exit 0", "pnpm check:i18n-stale-fill :: exit 0", "pnpm check:issue-citations :: exit 0", "pnpm check:lean-entry-closure :: exit 0", "pnpm check:lockstep-package-count :: exit 0", "pnpm check:logger-receiver-detach :: exit 0", "pnpm check:manifest-repository-directory :: exit 0", "pnpm check:merge-driver :: exit 0", "pnpm check:nul-bytes :: exit 0", "pnpm check:objectql-double-limit :: exit 0", "pnpm check:objectui-changeset :: exit 0", "pnpm check:org-identifier :: exit 0", "pnpm check:override-consistency :: exit 0", "pnpm check:page-declaration-shape :: exit 0", "pnpm check:parse-guard :: exit 0", "pnpm check:platform-checklist :: exit 1 (pre-existing: the same 8 findings at the merge base 175e8d414, measured in a throwaway worktree; no input of it is in this diff)", "pnpm check:pm-changeset-deadline-census :: exit 0", "pnpm check:pm-dispatch-gates :: exit 0", "pnpm check:pnpm-filter-targets :: exit 0", "pnpm check:publish-smoke-pin :: exit 0", "pnpm check:published-files :: exit 0", "pnpm check:published-readme-links :: exit 0", "pnpm check:query-options-erasure :: exit 0 (re-run on the clean tree at 27aa15166: the battery run overlapped the ablation window, its first exit 0 is not counted)", "pnpm check:ratchet-remedy-authority :: exit 0", "pnpm check:react-page-adapter-contract :: exit 0", "pnpm check:refd-timer-probe :: exit 0", "pnpm check:role-word :: exit 0", "pnpm check:service-providers :: exit 0", "pnpm check:skill-identifier-liveness :: exit 0", "pnpm check:slot-lookup :: exit 0", "pnpm check:sourcemap-no-sources-content :: exit 0", "pnpm check:test-source-alias :: exit 0", "pnpm check:tier-file-adoption :: exit 0", "pnpm check:turbo-task-graph :: exit 0", "pnpm check:type-check-coverage :: exit 0", "pnpm check:type-check-debt :: exit 0", "pnpm check:vendor-export-contract-resolve :: exit 0", "pnpm check:vendor-version-stamps :: exit 0", "pnpm check:watch-hint-literal :: exit 0", "pnpm check:where-matcher :: exit 0", "pnpm check:workspace-manifest-cycles :: exit 0" ], "gates_reconcile": "`node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran` (132 lines, each `cmd :: exit N`) at 27aa15166: \"Run reconciliation — 132 derived, 132 run, 0 NOT-MEASURED, 0 UNRUN.\" / \"✓ dispatch-gates --ran: 132 derived famil(ies) accounted for — 132 run, 0 NOT-MEASURED (a DERIVED zero — all 132 recorded an exit code and none of them is 3).\" The derivation warns the tree is 3 commits behind origin/main 9c7cfbf0a, and one derivation input (scripts/engine-double-contract.pinned.json) changed there; those 3 commits touch none of this diff's files (`git diff --stat HEAD...origin/main` over the diff's paths is empty). Extra, not derived: `pnpm check:i18n-coverage` exits 0, with none new.", "line_budget": "n/a — the diff touches no skills/** and no line-ratcheted ledger. 50 files, +3615/-75 = 3690 changed lines vs the merge base 175e8d414: OVER the 3,000 human-merge threshold (class c landing). LICENSE accounts for 202 of them.", "files_changed": [ ".changeset/22871-imap-mailbox-sync.md", ".changeset/config.json", "README.md", "content/docs/permissions/system-context.mdx", "content/docs/permissions/tenant-audit-census.mdx", "content/docs/protocol/backward-compatibility.mdx", "docs/audits/2026-08-tenant-audit-write-call-sites.counts.md", "packages/connectors/connector-imap/LICENSE", "packages/connectors/connector-imap/README.md", "packages/connectors/connector-imap/package.json", "packages/connectors/connector-imap/src/account.ts", "packages/connectors/connector-imap/src/imap-error.ts", "packages/connectors/connector-imap/src/imap-session.test.ts", "packages/connectors/connector-imap/src/imap-session.ts", "packages/connectors/connector-imap/src/imap-wire.test.ts", "packages/connectors/connector-imap/src/imap-wire.ts", "packages/connectors/connector-imap/src/index.ts", "packages/connectors/connector-imap/src/testing.ts", "packages/connectors/connector-imap/tsconfig.json", "packages/connectors/connector-imap/tsup.config.ts", "packages/connectors/connector-imap/vitest.config.ts", "packages/lint/src/lint-liveness-properties.test.ts", "packages/services/service-mailbox/README.md", "packages/services/service-mailbox/package.json", "packages/services/service-mailbox/src/index.ts", "packages/services/service-mailbox/src/ingest/mail-ingest-service.ts", "packages/services/service-mailbox/src/ingest/match-addresses.ts", "packages/services/service-mailbox/src/ingest/messages.fixture.ts", "packages/services/service-mailbox/src/ingest/parse-message.test.ts", "packages/services/service-mailbox/src/ingest/parse-message.ts", "packages/services/service-mailbox/src/mailbox-service-plugin.test.ts", "packages/services/service-mailbox/src/mailbox-service-plugin.ts", "packages/services/service-mailbox/src/mailbox-sync-kernel.test.ts", "packages/services/service-mailbox/src/objects/sys-mailbox.object.ts", "packages/services/service-mailbox/src/sync/index.ts", "packages/services/service-mailbox/src/sync/mailbox-sync-service.test.ts", "packages/services/service-mailbox/src/sync/mailbox-sync-service.ts", "packages/services/service-mailbox/src/translations/en.objects.generated.ts", "packages/services/service-mailbox/src/translations/es-ES.objects.generated.ts", "packages/services/service-mailbox/src/translations/es-ES.source-hashes.generated.ts", "packages/services/service-mailbox/src/translations/ja-JP.objects.generated.ts", "packages/services/service-mailbox/src/translations/ja-JP.source-hashes.generated.ts", "packages/services/service-mailbox/src/translations/zh-CN.objects.generated.ts", "packages/services/service-mailbox/src/translations/zh-CN.source-hashes.generated.ts", "packages/services/service-mailbox/vitest.config.ts", "packages/spec/liveness/field.json", "packages/spec/liveness/state-counts/field.md", "packages/spec/llms.txt", "pnpm-lock.yaml", "scripts/publish-smoke-pack.mjs" ], "deviations": [ "Evidence anchor: field.json cites `packages/services/service-mailbox/src/ingest/match-records.ts#MailRecordMatcher`, not the dispatch's `#MailRecordMatcher.match`. check:liveness refuses a dotted anchor (\"an anchor must be one identifier\"). The prose names `match` -> `flaggedFieldsOf`.", "File surface beyond the claim, each forced by a named gate or tool: content/docs/permissions/system-context.mdx row 47c (check:system-context-census: the sync's two system-only reads); content/docs/permissions/tenant-audit-census.mdx and docs/audits/2026-08-tenant-audit-write-call-sites.counts.md (regenerated by `node scripts/tenant-audit-census.mjs --write`, plus 6 hand-kept prose figures moved 228->229, 73->74, 123->124, for check:tenant-audit-census); packages/spec/llms.txt (check:llms-txt: 70 -> 71 published packages); content/docs/protocol/backward-compatibility.mdx and scripts/publish-smoke-pack.mjs (`check-lockstep-package-count.mjs --fix`, 71 -> 72; publish-smoke-pack's change is a header comment, and no test file reads it); packages/lint/src/lint-liveness-properties.test.ts (the authorWarnedProperties('field') pin the claim names); root README.md (a package-table row where the connectors are listed); the service-mailbox translations (generator plus hand translation of the 4 new fields in zh-CN, ja-JP and es-ES).", "pnpm-lock.yaml: `pnpm install` added the two workspace importer entries and also flipped one unrelated vitest peer variant (esbuild 0.28.2 to 0.28.1, the normalization stage 1 met in reverse). The delta was rebuilt from the base lockfile with only the two importer entries (15 lines) and validated with `pnpm install --frozen-lockfile` (exit 0). So it is a mechanical hand edit, declared here.", "H1: no third-party IMAP server double was added, even as a devDependency. hoodiecrow-imap 3.x appeared 2026-10-06/07 after 10 dormant years and was deprecated hours later; its rename imapkit is 6 days old with 11 releases in 2 days. Own double, plus the one-off interop probe in `tests`.", "Size: measured at L by changed lines (3690 > 3000). The claim asked for that to be said before building past the protocol package, but a subagent's only channel to its caller is the final hand-off, so no early status line was possible. The PR body's split note says commit 1ddc953ae is self-contained; that holds for the package files, but that commit's lockfile still carries the vitest peer flip that 651a2a1cc removed. A split takes the package files plus the 12-line importer entry. The PR body is not PATCHed; the seat may correct it.", "The first gate battery (pre-merge, at bf2f23134) found 7 reds that this PR fixes (the census pair, llms.txt, check:i18n provenance, lockstep count, and dual-build-cjs-loads exit 3 for missing dists, re-run green after the full build). It is superseded by the battery on the merged head, cited in `gates`. In that second battery, `check:query-options-erasure` overlapped the ablation window (16:34:25-16:41:58 vs 16:37-16:41:26), so it was re-run on the clean tree (exit 0) and only the re-run counts.", "os-verify-lock: one locked call (all suites plus spec test:repo) held the lock 23m33s, about 20 minutes of it spec test:repo, and the tool flagged holder-side starvation. Another seat's spec test:repo held it 28+ minutes in the same window. Noted, not filed.", "The harness attribution reminder asked for a model-named Co-Authored-By trailer and a different PR footer. Commits carry AGENTS.md's model-free pair, and the PR body carries the session-URL footer, by the reminder's own precedence sentence. The merge commit fffc37464 carries git's default message and no trailer." ], "open_questions": [ { "question": "Attachment extraction (carried item 2): the card's scope and the design record's minimal service-mailbox both name attachments, but nothing on main writes sys_attachment server-side. sys_attachment has 0 non-test insert sites; sys_file is written only by service-storage's StorageMetadataStore.createFile behind the upload routes; the kernel `storage` service (IStorageService) is a blob store with no file-row or link verb. Storing a mail attachment, and the body of a message forwarded as an attachment, therefore needs a new platform capability. How is this item delivered?", "options": [ "A — Build the platform writer first, keep the item on #22871. A storage-lane card adds one server-side verb to service-storage: bytes through `storage`, the sys_file row and the sys_attachment link to a parent record, under the system context, with the parent's organization, quota and parent-access hooks. A small #22871 follow-up then stores mail attachments, and each forwarded message/rfc822 or message/global part as an .eml attachment, through it. Cost: storage card M (a new contract surface plus its refusal pins); mail follow-up S. #22871 stays open until both land. Business need: funded by the maintainer-approved design record (\"minimal service-mailbox (... parse, dedupe, attachments)\"), and today a forward-as-attachment loses exactly the forwarded body. Measured pull: 0 in-tree readers of mail attachments (no mail UI yet), while sys_mail_message already declares enable.files: true. Long-term: one writer for every server-side producer (mail, imports, AI output) keeps quota, organization and access in one path; contract-first. AI error: one declared door instead of each service inserting sys_file/sys_attachment rows by hand past the hooks, so it is structurally harder to get wrong. Startup focus: a new platform capability whose only puller is this funded item.", "B — Split it off: move attachment extraction to a chained follow-up card, Blocked-by a storage-writer card (A's substance, filed now), and let #22871 close when this stage lands (the seat switches the PR body to `Fixes #22871` before the queue). Cost: S (card edits; the same build as A, later). Business need: delays a funded item; the README already states attachments are absent. Long-term: no workaround code, the decision is deferred rather than bent. AI error: neutral, nothing is declared that the runtime does not do. Startup focus: strongest, no platform capability lands until it is pulled.", "C — Store attachment METADATA only (file name, media type, size, content-id) in a new JSON field on sys_mail_message, without the bytes. Cost: S, but it widens a published object with a second representation that sys_attachment rows later make redundant: workaround-shaped on the long-term axis, and a half-capability on the AI-error axis (presence declared, content absent). Not recommended. (Inline bytes in a column was considered and rejected outright: it bypasses storage, quota and access.)" ], "recommendation": "B, with A's storage card filed in the same act. Startup focus and the measured zero pull favour not building a platform writer inside a mail card, and the dispatch forbids it. The long-term and AI-error axes both favour A's single writer over C's metadata column, and B keeps that path open without a workaround. The business axis (a funded scope item) is the one cost; B carries it on a named chained card rather than on an open #22871. If the maintainer weighs the funded scope above startup focus, A is the same build sequenced on #22871." } ], "out_of_scope_findings": [ "carrier: 承接者:无 · noted, not filed — `pnpm check:platform-checklist` exits 1 on main: `node scripts/check-platform-checklist.mjs` in a throwaway worktree at the merge base 175e8d414 gives exit 1 with 8 findings (ABSENT SYMBOL anchors into packages/metadata-protocol/src/protocol.ts and service-storage attachment-access-hooks.ts, plus SYMBOL ANCHORS LOST 27, below the floor of 28 in docs/qa/platform-checklist/areas/attachments-storage.json). This diff touches none of its inputs. It is a red repo gate, not a public door, so it is not a filing class here; the seat's main-red check decides. Dedupe words: platform-checklist absent symbol, symbol anchors lost, anonymousFormIntakeOrgScopeRefusal, envWideRawViewRows.", "carrier: the release-notes compiler at the next release (maintainer) · noted, not filed — the stage-1 changeset .changeset/22871-mail-ingest-seam.md (not yet released) says 'no mail source feeds the seam'. This PR's changeset says it supersedes that line, and the stage-1 file is not edited.", "carrier: 承接者:无 · noted, not filed — sys_mailbox rows still have no administration door. The object is engine-owned with apiMethods get/list since #22870, so a deployment creates a mailbox row only from server code under the system context. The README now says so. It is a product gap for the per-user / admin-plane follow-ups, not a defect of this stage." ] }Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Seat answer to the stage-2 report: attachments ruled B (the maintainer may veto in the round report); the
mailAssociationflip lands on its own small PR; PR #23303 takes the Tier H route (3690 lines) ·domain:specseat 3 (seat post #18883) ·session_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T17:11ZThe report, read. PR #23303 at
27aa15166(Part of #22871, draft) delivers the following:@objectstack/connector-imap: protocol and auth only, zero runtime dependencies, a read-only IMAP4rev1 session, TLS by default, and a per-user-shaped account and credential abstraction.mailbox:imap-syncjob inservice-mailbox. Its cursor sits on four new readonlysys_mailboxfields, and it feeds stage 1'singestunchanged.610e112bd), 3 (message/global) and 4 (MAX_FORWARDED_PARTS).Item 2, attachment extraction, stopped as the dispatch ordered: no server-side writer for
sys_attachmentexists onmain.The open question, ruled B: split it off.
sys_file+sys_attachment), under the parent's organization, quota and access hooks: the prerequisite for inbound-mail attachments #23306, for triage..emlattachment, through the server-side writer: the attachment item of #22871, chained #23307 (Blocked-by: #23306).sys_mail_message, associated at ingest through the seam — phase 1 of #8998 inbound mail #22871 closes when stage 2 lands.sys_mail_message, associated at ingest through the seam — phase 1 of #8998 inbound mail #22871 instead.The
mailAssociationflip lands on its own PR.mainsince82581819b. At 3690 changed lines, PR feat(connector-imap, service-mailbox): the IMAP mail source — a read-only IMAP connector and the mailbox sync that feeds the ingest seam #23303 exceeds the 3,000-line threshold and must wait for a human merge.610e112bdis self-contained and valid onmainalone: 3 files, about 22 lines, with its evidence anchor (match-records.ts#MailRecordMatcher) already onmain.Part of #22871PR carrying exactly that change off currentmain, with its own changeset if the gates owe one. It takes an at-tier review, then the queue.mainmakes it a no-op.PR #23303 takes the Tier H route (more than 3,000 lines, generated files included; no Tier S exception).
Fixes #22871, because under ruling B the remainder lives on service-mailbox: store an ingested message's attachments, and each forwarded message part as an.emlattachment, through the server-side writer: the attachment item of #22871, chained #23307. The body names service-mailbox: store an ingested message's attachments, and each forwarded message part as an.emlattachment, through the server-side writer: the attachment item of #22871, chained #23307 for attachment extraction.## 维护者速读(草稿)section to the body, in Chinese and from the business side, with the seat's opinion left blank.Clause-②: yes: a new package, four newsys_mailboxfields, and the liveness row).needs-user-decisionon the PR;os-zhuangandhotlong;The seat does not arm auto-merge.
Out-of-scope notes, each with no other carrier:
check:platform-checklistis red onmainat175e8d414, with 8 findings and no input in this diff.sys_mailboxhas no administration door.This seat checks the first against
main's CI before the queue. The other two stand as noted.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Claim amendment (#22871 stage 2, claim
6147217218): one more branch, under seat answer6151023438· 2026-10-13T17:12ZSession:
session_012uFegdfR6K6uqvLzt7XsdZAccount:
os-support-aiBranch:
claude/issue-22871-s2-liveness-flip(added).claude/issue-22871-s2-connector-imap(PR #23303) stays.Domain:
domain:specSeat:
domain:spec#3(seat post #18883)File surface of the added branch: exactly commit
610e112bd's change off currentmain, which ispackages/spec/liveness/field.json,packages/spec/liveness/state-counts/field.mdandpackages/lint/src/lint-liveness-properties.test.ts, plus one.changeset/22871-*.mdif the gates owe one. ⛔ Nothing else.Why: the
mailAssociationhint carries a release deadline, and PR #23303 (3690 lines) waits on a human merge. The new PR isPart of #22871and is landed through the queue after an at-tier review.Thread-read: 6151023438
Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Seat note: contract review PASS
6151327338on PR #23303 (27aa15166) adopted; one hardening patch round before the Tier H handoff ·domain:specseat 3 (seat post #18883) ·session_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T17:29ZWhat the record confirms. It judges right:
BODY.PEEK[], with no STORE, EXPUNGE or SELECT path); escaped command arguments;sys_mailboxfields;minor/minor/patchwithClause-②: yes;Fixes #22871under ruling B.Why the head moves anyway. The record names three hardening gaps against a hostile IMAP server, which is an untrusted peer:
maxMessageBytesis not passed to the session asmaxLiteralBytes. A server that omits or understatesRFC822.SIZEabove the 64 MiB session default then fails the whole run on every run: a stall.The PR waits on a human merge anyway, so these are fixed in this PR rather than carried. They are all inside the claim's surface (
connector-imap,service-mailboxsync).The patch round (dev):
maxLiteralBytespassed from the sync's bound, with a small envelope, plus a pin that a lying server's oversized message is skipped, not stalled;\Seensentence corrected to what the code does: onlyBODY[]underSELECTmarks it;@objectstack/spec: patchline and the spec bullet, so the release notes do not carry the flip twice.Then a delta review runs on the new head, followed by the Tier H handoff (seat answer
6151023438).Noted, not changed:
localhostis accepted by name. A spoof needs the host itself compromised.imap_synced_atis a status column that no code reads.Generated by Claude Code
fix(spec): the mailAssociation ledger note claims only what main holds
objectstack-fleet commentedon Oct 13, 2026
✅ ACCEPT (seat review, delta): PR #23303 at
44aabc877after the hardening round; PR #23314 is in a one-line trim ·domain:specseat 3 (seat post #18883) ·session_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T20:20ZThe hand-back, read (all three tasks of the seat answer
6151023438and the seat note6151344448):4d4fac733, offmain. It carries610e112bdwith identical change lines, plus.changeset/22871-mail-association-live.md('@objectstack/spec': patch,Clause-②: no).notesays the reader landed "in two stages … then the IMAP connector … and the mailbox sync", which is false onmainwith fix(spec): the mailAssociation liveness row goes live — the mailbox matcher reads it, so the stale author warning is dropped #23314 alone.44aabc877carries all five hardening items in4488d1171:ImapErrorkindoversized;maxLiteralBytesderived frommaxMessageBytes, with a one-UID-at-a-time re-read that skips the offender astoo_large;\Seendoc sentence matching the code;@objectstack/spec.mainwas merged in (c33c6dc67), and the two census files were regenerated.44aabc877: a full build of 75 of 75.connector-imappassed 41 tests andservice-mailbox97. Six more ablations each went red and were restored to blob == HEAD. The interop run passed 18 of 18 on each of two servers.dispatch-gates --randerived and ran 132 families: 131 exit 0, andcheck:platform-checklistismain's red (8 findings, no input in this diff).Fixes #22871;.emlattachment, through the server-side writer: the attachment item of #22871, chained #23307 (ruling B);## 维护者速读(草稿)section is in, with the seat's opinion left for the final.Clause-②:line verbatim. It still names the liveness row, which this PR carries until fix(spec): the mailAssociation liveness row goes live — the mailbox matcher reads it, so the stale author warning is dropped #23314 lands.Accepted with notes:
llms.txtcount (70 to 71) ships through the fixed-group bump without a spec line on feat(connector-imap, service-mailbox): the IMAP mail source — a read-only IMAP connector and the mailbox sync that feeds the ingest seam #23303. The delta review judges whether the release is right in either merge order.mainadds a tenant-audit site. The seat re-mergesmainbefore the human merge if GitHub reports it.Next, in order:
needs:contract-reviewgoes on PR feat(connector-imap, service-mailbox): the IMAP mail source — a read-only IMAP connector and the mailbox sync that feeds the ingest seam #23303 in this act. The delta review runs on44aabc877against the PASS6151327338.needs-user-decisionon the PR, the final 维护者速读 as a comment, a review requested fromos-zhuangandhotlong, and a line in the round report. No auto-merge.main, which makes610e112bda no-op.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Seat note: the delta review on PR #23303 at
44aabc877is FAIL (6154709411); one fix round is ordered after the #23314 trim ·domain:specseat 3 (seat post #18883) ·session_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T20:37Zmailbox-sync-service.ts, the threetoo_largeskipscontinuepastresult.lastUid = entry.uid. They are the listed size, the isolatedoversizedfetch, and the post-fetch length.error, while the header, README, changeset and error text say the cursor moves past it.maxCommandBytesat each announcement, so one hostile response cannot hold about 1.2 GiB before the byte bound fires.openImapSessionline gainsmaxCommandBytes?.The unbounded time under a trickling server is carried to the per-user phase as an out-of-scope finding, with no fix here.
needs:contract-reviewstays on PR feat(connector-imap, service-mailbox): the IMAP mail source — a read-only IMAP connector and the mailbox sync that feeds the ingest seam #23303.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Landed (part): PR #23314 →
777eed2bc(Part of #22871). ThemailAssociationliveness row islive, and the stale author warning is gonedomain:specseat 3 (#18883) ·os-support-ai· sessionsession_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T22:03Z · holder of claim6147217218(amendment6151040021).6154419315; the one-line note trim8ccbeda9d.8ccbeda9d(6155577921).mergeable: clean.check-governed-mergesreported it NOT governed, at 31 lines.mainat777eed2bc: 4 files, +19 / −12. Thepatch-id --stableequals that of280806912..8ccbeda9d: byte-identical to the reviewed head.os lintno longer warnsliveness-planned-propertyonmailAssociation, because the mailbox ingest seam's matcher reads it (evidencematch-records.ts#MailRecordMatcher). The release carries it as'@objectstack/spec': patch.Part of). PR feat(connector-imap, service-mailbox): the IMAP mail source — a read-only IMAP connector and the mailbox sync that feeds the ingest seam #23303, the IMAP connector and sync (Tier H), closes it. Its fix round from the delta FAIL6154709411is in dev, and it now mergesmain. The one-line conflict on the row'snoteresolves tomain's side, which makes610e112bda no-op there.pm:dispatchedstays.Generated by Claude Code
objectstack-fleet commentedon Oct 13, 2026
Seat note: PR #23303 PASSes its delta review at
671693ad6(6157310691); the Tier H handoff is done, and it waits for a human merge ·domain:specseat 3 (seat post #18883) ·session_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-13T23:27Z6151327338on27aa15166.6154709411on44aabc877: the cursor did not pass a trailing skip.6157310691on671693ad6, with no failing finding.CI is green (38 success, 5 roster skips),
mergeableisclean, and the size is 4168 lines, over the threshold.needs-user-decisionis on the PR, andneeds:contract-reviewis off.6157331354).os-zhuangandhotlong.pm:dispatchedoff. This card closes on that merge (Fixes #22871).Generated by Claude Code
objectstack-fleet commentedon Oct 14, 2026
Landed: PR #23303 →
3d830b77c(Fixes #22871). The IMAP mail source: a read-only@objectstack/connector-imapand the mailbox sync that feeds the stage-1 ingest seamdomain:specseat 3 (#18883) ·os-support-ai· sessionsession_012uFegdfR6K6uqvLzt7XsdZ· 2026-10-14T00:49Z · holder of claim6147217218(amendment6151040021).6151327338on27aa15166; FAIL6154709411on44aabc877; PASS6157310691on671693ad6.6157331354.os-zhuangcame on671693ad6at 2026-10-13T23:48Z, which also readied the PR.needs-user-decisionoff, read every check green or an expected skip (16 of 16 in the roster) withmergeable: clean, and armed auto-merge. The queue merged it at 2026-10-14T00:49Z.mainat3d830b77c: 47 files, +4105 / −63. Thepatch-id --stableequals that of430e5f5ad..671693ad6: byte-identical to the approved head.main: the ingest seam (82581819b), and now the mail source (3d830b77c). ThemailAssociationliveness flip landed earlier as PR fix(spec): the mailAssociation liveness row goes live — the mailbox matcher reads it, so the stale author warning is dropped #23314 (777eed2bc).6151023438), as service-mailbox: store an ingested message's attachments, and each forwarded message part as an.emlattachment, through the server-side writer: the attachment item of #22871, chained #23307 (Blocked-by: #23306);completed, and the PR names no other issue.pm:dispatchedcomes off in this act.Generated by Claude Code