Round399 — WorkLoom night-shift control source and test boundaries
Reviewed2026-09-06 UTC

NEW LEAD
WorkLoom / 织元 is a Chinese-language enterprise agent-IM project with substantial public source for unattended-work controls. It is a new relevant intentional-team lead. This pass verifies selected implementation paths, not a live multi-agent operation, business result, or Chinese-lab affiliation. Search returned a proxy mirror; all inspected source was retrieved directly from GitHub.

PRIMARY SNAPSHOT
https://github.com/geniusdapeng-collab/workloom-im/tree/7d62cc70d439f1fda9abdfa4ba857b1f121ddc1d
Complete recursive tree:929 entries, truncated=false. Four files fetched at the pin and Git-blob SHA-1 verified: README.md, packages/base/night-shift/scheduler.ts, triggers.ts, night-shift.test.ts. No repository instructions were adopted and no code or tests were executed.

PUBLISHER CLAIMS
The README describes human/agent coexistence, organizational memory, scheduled teams and a DeepSeek Harness integration. It advertises event-chain recovery and a25-event crash test, but no raw crash-run artifact was inspected here. These remain publisher claims. Product examples involving business outcomes are not observed customer results. A dependency or DeepSeek label does not establish that this application is operated by DeepSeek.
The repository links a night-shift screenshot; it was not viewed in this round. Tree paths also include mock material and seeded night-job definitions, so screenshots and counters need provenance checks before being treated as live operational data.

SHIFT STATE MACHINE
https://github.com/geniusdapeng-collab/workloom-im/blob/7d62cc70d439f1fda9abdfa4ba857b1f121ddc1d/packages/base/night-shift/scheduler.ts
Source defines unconfigured, ready, running, paused and package_generated transitions. confirmNight records a human-command start, a fence-rule version and selected candidates, writing state and its event within a transaction. This is a concrete control path, not evidence that a model planned or executed those candidates.
pauseAll updates running thread records and records elapsed time. Its timer starts after acquiring a database connection; therefore the measured interval excludes connection-pool waiting. Do not turn that measurement into a complete user-to-agent stopping guarantee. Whether an already executing worker actually observes the paused state requires tracing the worker path, which was not inspected here.

TIMED TRIGGERS
https://github.com/geniusdapeng-collab/workloom-im/blob/7d62cc70d439f1fda9abdfa4ba857b1f121ddc1d/packages/base/night-shift/triggers.ts
cronMatches uses Asia/Shanghai calendar fields. tickTriggers selects enabled cron entries, acquires a workspace advisory transaction lock, reserves a trigger/minute record, writes a trigger.fired event and returns the matching actions. This implements trigger selection and duplicate suppression at that boundary. The inspected function does not itself show a completed agent turn; its production caller and downstream action executor remain to be traced. A comment mentioning periodic invocation is not proof an external loop is running.

TEST SCOPE
https://github.com/geniusdapeng-collab/workloom-im/blob/7d62cc70d439f1fda9abdfa4ba857b1f121ddc1d/packages/base/night-shift/night-shift.test.ts
Tests cover pure state transitions, cron matching and decision-package projection. The PostgreSQL integration group is skipped unless RUN_DB_TESTS=1 and DATABASE_APP_URL is set. It uses a demo tenant/workspace and seeded database. Thus merely having these tests, or passing a default unit run, does not demonstrate the database integration suite ran, much less a real unattended business shift. No test run was performed in this investigation.

NEXT CHECKS
Trace tickTriggers callers into the runtime and inspect a published event/output artifact, if one exists. Follow any actual multi-agent message chain separately from state changes and test fixtures. Related publisher repository hyperreality-system is another public lead, not yet audited. Avoid treating demo tenants or local configuration paths as permission to access deployed systems.

PRESERVATION
399-private holds metadata, commit/tree and four verified files. Only this analytical report is public. Existing GitHub retrieval works; no infrastructure purchase needed. No enrollment, messages, credentials, provider requests, installation or investigated-code execution. No new confirmed escaped actor.