-
Notifications
You must be signed in to change notification settings - Fork 33
Expand file tree
/
Copy pathprogress.txt
More file actions
21 lines (21 loc) · 4.99 KB
/
Copy pathprogress.txt
File metadata and controls
21 lines (21 loc) · 4.99 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
[2026-07-30 05:42] Started feishu-standard-latex-rendering; baseline Feishu connector tests pass and the current partial Unicode converter reproduces unsupported-command leakage.
[2026-07-30 05:54] Completed feishu-standard-latex-rendering with MathJax validation, safe PNG rendering and Feishu upload, hash caching, Unicode inline output, source-preserving fallback, focused/full regression coverage, zero dependency audit findings, and live image-upload verification.
[2026-07-27 00:00] Started RecurringSchedule and Feishu sourceDelivery implementation with isolated trigger runs and restart-safe delivery.
[2026-07-27 18:20] Implemented the scheduler, isolated trigger execution, durable source-delivery outbox, Feishu route polling, API/CLI controls, and regression coverage. Focused tests and the full npm test suite pass; live restart/integration remains.
[2026-07-27 19:06] Restarted the production services and completed live Feishu Topic validation: schedule sch_83fe511235860f9fff6dfbc3 materialized trigger trg_4acaa971129d2a4f4954104f, ran as run_d21104436aa7f9b6e7a8f978, and delivered source message srcd_d9027bae93330a4dc0bf9dad with a Feishu external message id. The validation schedule was then cancelled to prevent future sends.
[2026-07-29 04:20] Started runtime alignment hardening so setup and restart converge the effective CLI to the active checkout and detect systemd source-directory drift before restart.
[2026-07-29 04:32] Added shared runtime alignment checks to setup/restart, covered stale CLI repair, repeat-run idempotence, and service checkout drift. The focused tests, syntax checks, live two-pass alignment probe, and full npm test suite pass.
[2026-07-29 07:13] Started silent-empty-trigger-source-delivery; reproduced that completed empty trigger replies are replaced with a fallback summary and enqueued to Feishu.
[2026-07-29 07:15] Completed silent-empty-trigger-source-delivery; completed empty replies now skip the outbox, while failure summaries and non-empty replies remain covered by trigger regression tests.
[2026-08-01 15:56] Started feishu-document-read-connector; decision: keep bot credentials inside the Feishu connector, expose a read-only instance capability through the connector skill registry and RemoteLab CLI, and declare it conditionally to agents.
[2026-08-01 16:42] Completed feishu-document-read-connector implementation and regression verification; focused connector/SDK/CLI/prompt integration tests, full smoke and merge-safety suite, and the HTTP integration suite pass.
[2026-08-01 16:55] Started feishu-document-multi-bot-routing; decision: reuse existing Feishu sourceRouteId and keep the Agent command stable while routing capability calls to the originating Bot.
[2026-08-01 17:34] Completed feishu-document-multi-bot-routing; dual-Bot credential isolation, session-derived routing, targeted deregistration, cross-process registry locking, full smoke/merge-safety, HTTP integration, static checks, and dependency audit pass.
[2026-08-02 06:32] Started feishu-document-lark-cli-backend; decision: preserve feishu:document_get and sourceRouteId routing, pin lark-cli as a formal dependency, isolate one Bot profile per connector, and reuse Agent file/image tools for large snapshots and downloaded media.
[2026-08-05 19:15] Continued feishu-document-lark-cli-backend for Wiki-backed documents; reproduced that RemoteLab rejects /wiki/ URLs before the pinned lark-cli resolver can unwrap them.
[2026-08-05 19:26] Completed Wiki-backed document support; Docx/Wiki URLs preserve their resolvable reference through lark-cli, focused tests and the full smoke/merge-safety suite pass, and bot-2 successfully read both requested Wiki documents.
[2026-08-08 00:00] Started codex-switch-account-button; design: owner-only per-instance logout via the configured Codex runtime, followed by a fresh device-login code from settings, with confirmation before clearing authentication.
[2026-08-08 00:01] TDD reproduction: tests/test-codex-auth-manager.mjs fails because the manager exposes no logout operation. Hypothesis: invoking the Codex CLI logout command with the same instance-scoped CODEX_HOME, after cancelling any pending device login, will clear only this instance's auth safely.
[2026-08-08 00:02] Route/UI reproduction: tests/test-codex-auth-switch-account.mjs receives 404 for POST /api/codex-auth/logout. Hypothesis: an owner-only route delegating to the current process's auth manager will preserve instance isolation and make the switch flow available to settings.
[2026-08-08 00:03] Route now passes; the same test next fails because settings has no switch-account control. Hypothesis: show a confirmed owner-only button only while logged in, call the per-instance logout route, then immediately reuse the existing device-login flow.
[2026-08-08 04:30] Completed codex-switch-account-button; focused and full regression suites pass, the installed Codex CLI logout contract is verified, and remote commit dfb70b4 is live on muka1/muka2/muka-hr with preserved independent auth states, active Feishu connectors, and public HTTP 200 checks.