Add the Project board's seven metrics behind a five-minute cache by Birfy · Pull Request #1835 · ThinkFlowLab/FlyBot

Birfy · 2026-10-30T12:46:41Z

Written-by: Dev
Reworked-by: Rework

Fixes #1829
Owner: Dev
Reviewer: Reviewer
Tip SHA: b07e137
Base: f245520
Docs-not-needed: no — docs/subsystems/core-host.md and docs/subsystems/core-client.md carry the two sections.

What changed

host: new core/src/host/project-metrics.js — the seven numbers (PRs opened/merged today, issues opened/closed today, 7-day medians of PR merge, issue close and task completion), a five-minute in-process cache, and runningOf for the running table. The token comes from the host secret store (GITHUB_TOKEN) and the day boundary from the request's timeZone, so a reader in Shanghai gets its own day. A missing credential or a failed read answers ok: false with null values, and a failed read is never cached. project-board carries metrics beside the rows (the endpoint returns it), so header and rows come from one read. The cache holds the seven numbers only; the running rows are projected from the live tasks on every read.
client: core/src/client/project-board.js renders the seven cards (each with its one-line caption), draws — for every value the host could not read, and renders the running table — task, status, who, claim age, source (bot / group / workflow), last activity — with an overdue mark past RUNNING_OVERDUE_MS, a click through the existing onOpen, and one empty line when nothing is running. It asks the endpoint for the reader's zone. core/client.js is rebuilt from src/client (npm run build).
tests: core/test/project-metrics.test.js (natural-day boundary in two zones, per-field day counts, empty window → —, seven-day window, no-credential and failed-read degradation, cache hit spending the source once, a card claimed after a cached read still running, running-row projection, task median) and core/test/project-board.test.js (the board reads GITHUB_TOKEN from the host secret store and the zone from the call) plus three view cases in core/test/project-board-view.test.js.
generated: patches/ds-bot/ is regenerated with the repository's own tooling on a machine with git, so 0008 is hunks again instead of one whole-bundle replacement, and files/ mirrors the new sources.

Reworked from the INC at `caa61c3`

changelog.d/1829-project-metrics.added.md — renamed (done at bae6e49).
project-board.js — rt.secretValue('GITHUB_TOKEN') replaces the unassigned rt.githubToken; a test asserts the board carries the token.
project-board.js — the zone comes from the request body (client sends its own), UTC only as the fallback.
project-metrics.js — the cache keeps the seven numbers; running is derived from the live tasks every read.
patches/ds-bot/0008-client-bundle.patch — regenerated with git: one 14,040-line hunk is now 274 hunks.
## Checkpoint — trimmed under 1,500 characters with a summary under 600.
docs/subsystems/core-host.md — the numbers ride on the project-board endpoint, not a project-metrics endpoint in store.js.

Checkpoint

{
  "pr": 1835,
  "claim": "Dev",
  "issue": 1829,
  "summary": "Host: `project-metrics.js` counts today's opened/merged PRs and opened/closed issues in the reader's zone, with seven-day medians of PR merge, issue close and task completion; its token now comes from the host secret store, its zone from the request, and the cache holds the numbers while the running rows are read live. `store.js` returns the `metrics` section beside the rows. Client: seven captioned cards, a dash for an unreadable value, and the running table with the overdue mark and the row click. Tests cover the day boundary, degradation, the cache, the live rows and the token/zone wiring.",
  "files": [
    "core/src/host/project-metrics.js",
    "core/src/host/project-board.js",
    "core/src/host/store.js",
    "core/src/client/project-board.js",
    "core/client.js",
    "core/test/project-metrics.test.js",
    "core/test/project-board.test.js",
    "docs/subsystems/core-host.md"
  ],
  "checks": {
    "ran": "TZ=UTC node --test test/project-metrics.test.js test/project-board.test.js test/project-board-view.test.js (47/47); node scripts/ds-bot-patches.mjs check; node scripts/build-client.mjs --check",
    "result": "green",
    "at": "85ee213b6c643a2930c09c3304fd673da90bc092"
  },
  "next": "CI tests-ok at this tip is the gate, then a fresh PASS; full npm run verify (lint and the plugin suites) and smoke are unrun here."
}

The board had counts but no numbers: today's opened and merged PRs and issues, and the seven-day medians of PR merge, issue close and task completion durations, read from GitHub REST beside the local task store. The natural day is the reader's time zone, not the host clock, and a missing credential or a failed read answers `ok: false` with null values so the board paints `—` instead of inventing a zero. The read rides on `project-board`, so the header and the rows cannot disagree, and one five-minute in-process cache spends the source once per window; a failed read is not cached. `runningOf` projects a claimed card into the running table row: who, claim age, source and last activity. Fixes #1829 Docs: docs/subsystems/core-host.md

Birfy · 2026-10-30T12:51:32Z

Written-by: Chief

在这个 tip 073e6f11d0a27d9b18f5f6f026bc5356a7c31ae9 上有两处机械失败，改完重推就绿：

changelog 片段名不合法（package job 红在 .github/scripts/changelog.test.mjs）：changelog.d/1829-project-metrics.feature.md: name must be <slug>.<kind>.md with kind one of added, changed, deprecated, removed, fixed, security。把这一个文件改名为 changelog.d/1829-project-metrics.added.md（内容是新增能力，用 added）。
Checkpoint 块超长（enqueue-guard 拒收，非 PASS 问题）：checkpoint field "summary": 633 characters, over the 600、checkpoint field "next": 324 characters, over 300。把 summary 压到 ≤600、next 压到 ≤300，整个  块仍在 1500 字符内，其余字段不动。

改完 npm run verify（或至少 node --test .github/scripts/changelog.test.mjs）再推，并把 tip SHA 更新到 PR 正文与 Checkpoint 的 checks.at。

Birfy · 2026-10-30T12:54:15Z

Verdict: REQUEST_CHANGES at 073e6f1
Written-by: Reviewer
Attestation: 073e6f1 role=Reviewer

Ran at this tip:

$ cd core && TZ=UTC node --test test/project-metrics.test.js
# tests 9  # pass 9  # fail 0
$ cd core && TZ=UTC node --test test/project-board.test.js test/project-board-view.test.js
# tests 33  # pass 33  # fail 0
$ TZ=UTC node .github/scripts/changelog.mjs check
# changelog: 1829-project-metrics.feature.md: name must be <slug>.<kind>.md with kind one of added, changed, deprecated, removed, fixed, security
$ GH_REPO=ThinkFlowLab/FlyBot node .github/scripts/risk-gate.mjs --pr 1835
# risk-tier: T3; basis: core/src/host/project-board.js=T2, core/src/host/project-metrics.js=T2, ...

Red-first: with core/src/host/project-metrics.js removed and core/src/host/project-board.js reset to base 7d21690, the metrics command answers not ok 1 - test/project-metrics.test.js (# tests 1 # pass 0 # fail 1, ERR_MODULE_NOT_FOUND); restoring both tip blobs returns 9/9. The compare API is clean: 7 files, all in this change set, no unrelated core/ or patches/ds-bot/ edit.

What blocks this tip

changelog.d/1829-project-metrics.feature.md:1 — expected a kind in added|changed|deprecated|removed|fixed|security, actual feature; the CI package job fails and tests-ok is red at this tip. Rename to changelog.d/1829-project-metrics.added.md, content unchanged.
core/src/host/project-board.js:418 — expected the token from the host's secret store (rt.secretValue('GITHUB_TOKEN'), the path connectors.js uses), actual rt.githubToken, which no module assigns. readMetrics therefore always answers ok:false / no-credentials, so the seven numbers can never render. Wire the token from the host and add a test that the endpoint carries it.
core/src/host/project-board.js:420 — expected the reader's own time zone (the issue's natural-day rule), actual rt.timeZone, which is never assigned either, so the day counts always fall back to UTC. Pass the zone from the request/settings and test a non-UTC day boundary through the endpoint.
core/src/host/project-metrics.js:125 — the cache key excludes tasks, so the cached running list is returned unchanged for up to five minutes; a card claimed a minute ago is missing from the running table. Expected: cache the seven metrics only and derive running from the live tasks on every read (the issue's 5-minute cache is for the metrics).
core/src/client/project-board.js — the client half is absent (0 changed lines): no seven cards with their one-line captions, no running table (who / since claim / source / last activity, overdue mark, row opens via onOpen, one-line empty state), and Waiting/In flight/Blocked are not collapsed to one count line. This is 项目看板：7 个指标卡 + 在跑任务表 #1829 要做的 2–4 and this PR's own next; add it with the en/zh keys in core/src/client/i18n.js, the view/i18n cases, and docs/subsystems/core-client.md.
docs/subsystems/core-host.md:758 — the new section calls project-metrics “the endpoint in store.js”, but store.js has no such endpoint; the numbers ride on the existing project-board endpoint. Correct the sentence (or add the endpoint) so the doc matches the code.
## Checkpoint — enqueue-guard refuses it: summary is 633 characters (> 600) and next is 324 (> 300). Trim both to their limits.

The host module's own nine tests are good, but they inject token/timeZone directly, so they cannot catch items 2 and 3. Risk tier at this tip is T3; this is the only conclusion at this tip.

The client half of #1829: the seven cards with their captions, the dash for a value the host could not read, the running table (title, status, holder, claim age, source, last activity) with an overdue mark and a click through the existing onOpen, and one empty line when nothing is running. metricsView is pure so the view tests read it without a fetch. The Waiting/In flight/Blocked groups keep their reason lines beside the one-line count header. Fixes #1829 Docs: docs/subsystems/core-client.md

The seven card labels, their captions, the running table columns and the unavailable line read in zh as well as en; two keys that already existed are not duplicated, and client.js is rebuilt so the bundle carries the new dictionary. Fixes #1829

Birfy · 2026-10-30T13:07:18Z

Written-by: Chief

新 tip caa61c327b2f31db3a91445e203d6862983ce9e2 上 changelog.d/1829-project-metrics.feature.md 还是原来的名字（文件列表里仍是 1829-project-metrics.feature.md），所以 package 仍然红在同一处：name must be <slug>.<kind>.md with kind one of added, changed, deprecated, removed, fixed, security。

这一步是把文件改名（git mv changelog.d/1829-project-metrics.feature.md changelog.d/1829-project-metrics.added.md），不是改内容；改完 node --test .github/scripts/changelog.test.mjs 应绿。顺带把 Checkpoint 里 summary（≤600）与 next（≤300）压短，enqueue-guard 才不会被字段长度拒。

Birfy · 2026-10-30T13:12:58Z

Verdict: REQUEST_CHANGES at caa61c3
Written-by: Reviewer
Attestation: caa61c3 role=Reviewer

Ran at this tip:

$ cd core && TZ=UTC node --test test/project-metrics.test.js test/project-board-view.test.js test/project-board.test.js
# tests 45  # pass 45  # fail 0
$ TZ=UTC node .github/scripts/changelog.mjs check
# changelog: 1829-project-metrics.feature.md: name must be <slug>.<kind>.md with kind one of added, changed, deprecated, removed, fixed, security
$ node scripts/ds-bot-patches.mjs check
# ok   10 patches apply cleanly in order
# ok   core/ equals ds-bot/ + patches/ds-bot/
$ GH_REPO=ThinkFlowLab/FlyBot node .github/scripts/risk-gate.mjs --pr 1835
# risk-tier: T3; basis: core/src/host/project-board.js=T2, core/src/host/project-metrics.js=T2, ...

Red-first: with the four changed sources reset to base 7d21690 (both project-metrics.js and the three client files), the same suites answer not ok 2 - test/project-metrics.test.js plus not ok 17/18/19 (the three new view cases): # tests 20 # pass 16 # fail 4; restoring the tip blobs returns 45/45. CI at this tip is terminal: test, plugins, all four plugin suites and Node 24 pass; package/tests-ok fail on the changelog fragment, enqueue-guard refuses as expected without a PASS at this tip.

What blocks this tip

changelog.d/1829-project-metrics.feature.md:1 — still kind feature; expected one of added|changed|deprecated|removed|fixed|security. The package job fails and tests-ok is red at this tip (this is the second tip in a row that carries it). Rename to changelog.d/1829-project-metrics.added.md, content unchanged.
core/src/host/project-board.js:418 — expected rt.secretValue('GITHUB_TOKEN') (the host secret store connectors.js reads), actual rt.githubToken, which no module assigns. Every read still answers ok:false / no-credentials, so the cards can never show a number. Wire the token and add a test that the endpoint carries it.
core/src/host/project-board.js:420 — expected the reader's own time zone, actual rt.timeZone, also never assigned, so the natural day always falls back to UTC. Pass the zone from the request/settings and test a non-UTC boundary through the endpoint.
core/src/host/project-metrics.js:125 — the cache still stores running with the metrics, and its key has no tasks, so a card claimed after the previous read is missing from the running table for up to five minutes. Cache the seven metrics only and derive running from the live tasks on every read.
patches/ds-bot/0008-client-bundle.patch:8 — the patch is now one whole-bundle replacement: @@ -42,14040 +42,22073 @@ where base has @@ -42,6 +42,57 @@; the file grows 19,840 → 36,116 lines although core/client.js changed only +145/−5. patches/ds-bot/0001-core-fixes.patch shows the same shape (i18n.js one 2,386-line hunk). Regenerate the series with the repository's own tooling/git so only the changed hunks land — a whole-file rewrite loses the merge-friendly property and buries the real change.
## Checkpoint in the body — enqueue-guard refuses it: the block is 1,529 characters (> 1,500) and summary is 748 (> 600). Trim summary and move detail out so the block stays under 1,500.
docs/subsystems/core-host.md:758 — still says “the project-metrics endpoint in store.js”, but store.js has no such endpoint; the numbers ride on the existing project-board endpoint. Correct the sentence (or add the endpoint) so the doc matches the code.

The client half now lands: seven captioned cards, the dash on an unavailable read, the running row with its fields/overdue/click, the i18n keys, the rebuilt bundle and the three view cases are present and green. Risk tier at this tip is T3; this is the only conclusion at this tip.

Birfy · 2026-10-30T13:32:26Z

Written-by: Triage

Updated #1835 at 5027a6e82ae2cd3f9f50c97993301c95871414cf (task i1829-impl re-dispatch):

Renamed changelog.d/1829-project-metrics.feature.md → changelog.d/1829-project-metrics.added.md, content unchanged. This was the red one in the package job (name must be <slug>.<kind>.md).
Shortened the ## Checkpoint block: summary 748 → 597 characters, whole block 1529 → 1402, so enqueue-guard's 600/1500 limits pass.
Merged main (f245520cbbcb7de1931a91c07c675e20dbe9fc79) into dev/1829-project-metrics; the base is current.

This tip is past the Reviewer's INC at caa61c327b2f31db3a91445e203d6862983ce9e2, so it needs a fresh review. That INC also listed items 2/3/4/5/7 (token wiring, reader time zone, caching running with the metrics, the whole-bundle patch regeneration, the store.js doc sentence); this re-dispatch did not cover them and they remain open.

CI at the new tip is in flight.

Birfy · 2026-10-30T13:43:03Z

Written-by: Chief

5027a6e82ae2cd3f9f50c97993301c95871414cf 只覆盖了 caa61c32 那次 INC 的第 1 条（片段改名）和第 6 条（Checkpoint 压短），第 2/3/4/5/7 条仍然有效，已按条重派返工（token 接线、读请求者时区、running 不缓存、patch 只落改动 hunk、core-host.md:758 句子）。修完会推同一分支的新 tip 再请复审。

The seven numbers could never render: `project-board` read `rt.githubToken` and `rt.timeZone`, which no module assigns, so every read answered `no-credentials` and the day counts fell back to UTC. The token now comes from the host secret store (`rt.secretValue('GITHUB_TOKEN')`, the path `connectors.js` reads) and the zone from the request body, which the client fills with its own zone. The cache kept the running rows beside the numbers, so a card claimed a minute ago stayed out of the running table for up to five minutes; the cache now holds the seven numbers only and the rows are projected from the live tasks on every read. The endpoint returned no `metrics` section at all, so the cards had nothing to draw; `store.js` carries it beside the rows. The subsystem page names the endpoint the numbers actually ride on. The patch series is regenerated with the repository's own tooling (git present), so 0008 is hunks again instead of one whole-bundle replacement. Ran: TZ=UTC node --test test/project-metrics.test.js test/project-board.test.js test/project-board-view.test.js -> 47/47; red-first with the four sources reverted -> 2 failures (the two new cases). node scripts/ds-bot-patches.mjs generate + check ok; node scripts/build-client.mjs --check ok. Not run: full `npm run verify` (lint/plugin suites), smoke.

Birfy · 2026-10-30T14:08:05Z

Written-by: Rework

Reworked onto main at f245520 (base unchanged, mergeable) — new tip b07e137.

Ran at this tip's tree (local commit 85ee213b, same tree 7f987ecb):

$ cd core && TZ=UTC node --test test/project-metrics.test.js test/project-board.test.js test/project-board-view.test.js
# tests 47  # pass 47  # fail 0
$ node scripts/ds-bot-patches.mjs check
ok   ds-bot/ = Fei2411/DeepSeek-Bot@2b10c70 (tree 5834c00, v0.1.5)
ok   10 patches apply cleanly in order
ok   core/ equals ds-bot/ + patches/ds-bot/
$ node scripts/build-client.mjs --check   # exit 0

Red-first: with the four changed sources reverted (patch, store, metrics, client board) and the tests kept, # tests 28 # pass 26 # fail 2 — not ok 26 - a card claimed after a cached read still shows as running and not ok 2 - the board takes its token from the host secret store and its zone from the call. Restoring them answers 47/47.

Not run here: full npm run verify (lint, plugin suites, plugin lint) and the smoke test; CI tests-ok at b07e137 is the gate.

What the five INC items now look like:

project-board.js reads the token with rt.secretValue('GITHUB_TOKEN'), the store connectors.js reads; a test fails without it.
The natural day comes from body.timeZone (the client sends Intl.DateTimeFormat().resolvedOptions().timeZone), UTC only as the fallback; store.js hands it to the board and now returns the metrics section, which it silently dropped before — the cards had nothing to draw.
project-metrics.js caches the seven numbers only; running is projected from the live tasks on every read, so a card claimed a second ago appears on the next read.
patches/ds-bot/0008-client-bundle.patch is regenerated with the repository's own tooling on a machine with git: 274 hunks instead of one 14,040-line whole-bundle hunk; the whole series was regenerated so check passes.
docs/subsystems/core-host.md now says the numbers ride on the project-board endpoint. The checkpoint block is 1,456 characters with a 599-character summary.

A fresh PASS at b07e137 is still needed (T3): the INC at caa61c3 named caa61c3.

Birfy · 2026-10-30T14:21:47Z

Verdict: PASS at b07e137
Written-by: Reviewer
Attestation: b07e137 role=Reviewer

Ran at this tip:

$ cd core && TZ=UTC node --test test/project-metrics.test.js test/project-board.test.js test/project-board-view.test.js
# tests 47  # pass 47  # fail 0
$ TZ=UTC node .github/scripts/changelog.mjs check
# changelog: 8 fragment(s) in changelog.d/ are well formed
$ node scripts/ds-bot-patches.mjs check
# ok   10 patches apply cleanly in order
# ok   core/ equals ds-bot/ + patches/ds-bot/
$ cd core && node scripts/build-client.mjs --check
# exit 0

Red-first: with core/src/host/project-board.js and core/src/host/store.js reset to base f245520 and the tests kept at the tip, project-board.test.js answers # tests 18 # pass 17 # fail 1 — not ok 2 - the board takes its token from the host secret store and its zone from the call; restoring the tip blobs returns 47/47 across the three suites. I checked the working tree against the tip before running: all 23 changed-file blob shas match b07e137.

INC 剩余项 — 全部关闭

token (was rt.githubToken): project-board.js:418 now reads rt.secretValue?.('GITHUB_TOKEN'), the store connectors.js uses; project-board.test.js:112 asserts the board carries it, and that test is the red one above.
zone (was rt.timeZone): store.js:685 hands body.timeZone (sliced to 64) to the board, the client sends Intl.DateTimeFormat().resolvedOptions().timeZone (client/project-board.js:591), and UTC is only the fallback; the same test checks Asia/Shanghai against the fallback.
cache/running: readMetrics caches the seven numbers only (running is destructured off before cacheStore.set) and both the hit and the miss project the live tasks; the case "a card claimed after a cached read still shows as running" passes.
patch series: 0008-client-bundle.patch is now 274 hunks starting @@ -42,6 +42,57 @@ — no whole-bundle replacement as at caa61c3 — and the regenerated series applies in order with core/ equal to ds-bot/ + patches. Residual, not blocking: the largest hunk is still 6,696 lines (base max 1,919) because the bundle reflows; the documented handling for a client.js conflict is to take main's patch and regenerate.
doc: docs/subsystems/core-host.md:758 now says the numbers ride on the existing project-board endpoint, with the token and zone from the request — matches store.js:683-700.
checkpoint: block is 1,483 characters, summary 599, next 130, eight files including core/src/host/project-metrics.js from this diff; checks.at names the local 85ee213b, which the guard reads rather than compares.
changelog: changelog.d/1829-project-metrics.added.md is a valid <slug>.<kind>.md; package is green at this tip.

CI at this tip: tests-ok, package, Node 24 and the four plugin suites all pass. enqueue-guard is the only red check and it names only the two stale conclusions (073e6f1, caa61c3), so it should turn green on this PASS. Risk tier T3 (label plus the report-only job). Full npm run verify and the smoke test were not run here; CI covers them at this tip.

Fixes ThinkFlowLab#1813 Owner: Dev2 Written-by: Dev-2 Reviewer: Birfy Claim-Id: 4bb5d8a6714e4c62b36b4354f6e82051 Base: f7ce89c Tip SHA: 1a56091 Tree: 384ec38 Diff: 7 files, +58/−3 Replayed-by: Replay — merged main f7ce89c into this branch by hand (`update-branch` answered 422 "merge conflict between base and head"), regenerated from the merged core; the change set is the one above, nothing moved. ## What changed The Project board's queue rows beside the columns print a live claim's state through the host's own lowercase lease id — `core/src/client/project-board.js:178` puts `running` or `stalled` in the row and `:252` renders it with `t(row.state)` — but the zh dictionary had `Running` (capital, used elsewhere) and lowercase `done` only, and `t()` returns a missing key unchanged. A Chinese interface therefore read "Dev4 · running". Two entries next to `done` in `core/src/client/i18n.js` close that: ```js running: '运行中', stalled: '已停滞', ``` `运行中` reuses the wording of the existing capital `Running` entry instead of inventing a second translation; `已停滞` matches the stalled card's own copy. The ids the board emits are untouched — only the zh map gains keys, so an untranslated locale still reads `running`. `core/test/i18n.test.js` gains one case that binds a zh dictionary, asserts both lookups, unbinds, and asserts the English fallback. ThinkFlowLab#1768's three cases never bound a dictionary, so the missing-key path (raw id, English by construction) kept CI green over the gap. The branch is based on `b4e05acf` (`ThinkFlowLab#1835`, which re-cut `0001`/`0002`/`0003`/`0005`/`0008` and rewrote `core/client.js`), so this tip is the change re-applied and regenerated on that base, not an earlier tip rebased as text. The force-push to this branch is a lease on the previous tip `be9be42ab9298d223df6166252ded85160f67a17`. ## Red first The new case alone, on base `b4e05acf`, dictionary entries removed, everything else at this tip: ``` ok 1 - every literal the client translates has a Chinese entry ok 2 - copy follows the DSH language and stays English without a locale service not ok 3 - \ThinkFlowLab#1813: the Project board queue states read in Chinese ... 'running' !== '运行中' # tests 3 # pass 2 # fail 1 ``` ## Generated mirrors `core/src/client/` changed, so `node core/scripts/build-client.mjs` rebuilt `core/client.js` (+4) and `node scripts/ds-bot-patches.mjs generate` re-cut `patches/ds-bot/0001-core-fixes.patch` (27/1: the two dictionary lines plus the test, against `ThinkFlowLab#1835`'s new context) and `patches/ds-bot/0008-client-bundle.patch` (5/1) and registered `test/i18n.test.js` under `0001` in `patches/ds-bot/topics.json` — without that entry `generate` refuses with "edited upstream files with no topic". `changelog.d/1813-board-state-i18n.fixed.md` is the one-line fragment. A second `generate` produced byte-identical files for both patches (sha1 verified before and after), and the patch chain reports `core/ equals ds-bot/ + patches/ds-bot/`, so the applied bundle is byte-identical. Nothing in the generated files was edited by hand. The `generate` that ran here rewrote `0002`/`0003`/`0005` too, but byte-identically — the diff carries only `0001` and `0008`, so no face this change does not touch moves. Docs-not-needed: two zh entries and one test; `docs/subsystems/core-client.md` owns `core/src/client/` and still describes the dictionary and its fallback correctly. ## Verification at the tip `Ran:` at `f0f3744b3fea565960b9a9e44f9529a5e167c0a0` (tree `182e73c9`) on the committed tree, `git status --porcelain` empty before and after: ``` $ TZ=UTC ARCH_DOCS_BASE=b4e05acf9c2785eced88e94f1b70e4f15c860c9f npm run verify $ node scripts/ds-bot-patches.mjs check # twice, a generate between them $ node core/scripts/build-client.mjs --check ``` - core: **2218/2218**, including `test/i18n.test.js` 3/3 - plugins social 541/541, tree 127/127, timeline 135/135, workflow 294/294 - `.github/scripts` 549/549, interop 37/37, live-e2e 24/24 - oxlint: 0 errors (71 warnings) in core; plugin lints 0 errors (36/9/2/16 warnings) - `build-client.mjs --check`: clean - `arch-docs: OK (7 changed file(s))` with `ARCH_DOCS_BASE=b4e05acf9c2785eced88e94f1b70e4f15c860c9f`, read off the committed tree's run - patch chain: ``` ok ds-bot/ = Fei2411/DeepSeek-Bot@2b10c70 (tree 5834c00, v0.1.5) ok 10 patches apply cleanly in order ok core/ equals ds-bot/ + patches/ds-bot/ ``` `Not run:` the smoke bench (no change to `index.js` or `src/host/`), the CI `package` job (pack check, typecheck, actionlint) and the merge-queue rebuild — those run in CI and on the queue entry, not locally. ## Checkpoint  ```json { "pr": 1830, "claim": "Dev2", "issue": 1813, "summary": "The Project board's queue rows print the host's lowercase lease ids (running, stalled) through t(), which returned them unchanged because the zh map had no such keys. Two entries beside done now read 运行中 and 已停滞, reusing the capital Running wording; emitted ids and fallback stay untouched. A case binds a zh dictionary and asserts both lookups, which ThinkFlowLab#1768 never covered. This tip re-applies it on b4e05ac, where ThinkFlowLab#1835 re-cut the patches and rewrote client.js: bundle rebuilt, chain regenerated, second generate byte-identical, check proves core equals ds-bot plus patches.", "files": [ "core/src/client/i18n.js", "core/test/i18n.test.js", "core/client.js", "patches/ds-bot/0001-core-fixes.patch", "patches/ds-bot/0008-client-bundle.patch", "patches/ds-bot/topics.json", "changelog.d/1813-board-state-i18n.fixed.md" ], "checks": { "ran": "TZ=UTC ARCH_DOCS_BASE=b4e05acf npm run verify; node scripts/ds-bot-patches.mjs check (twice, generate between); build-client.mjs --check", "result": "green", "at": "f0f3744b3fea565960b9a9e44f9529a5e167c0a0" }, "next": "none — ready for review" } ```  Co-authored-by: Danyang Chen <birfychen@gmail.com>

Birfy added the agent-pr Pull request opened by an agent label Oct 30, 2026

Birfy self-assigned this Oct 30, 2026

Birfy mentioned this pull request Oct 30, 2026

项目看板：7 个指标卡 + 在跑任务表 #1829

Closed

Birfy added 2 commits October 30, 2026 21:02

github-actions Bot added the risk:T3 Risk tier T3 (needs a human approval), set by the controller from the diff label Oct 30, 2026

Birfy added 2 commits October 30, 2026 21:31

Rename the changelog fragment to the added kind

bae6e49

Merge main into dev/1829-project-metrics

5027a6e

github-actions Bot added the pass label Oct 30, 2026

Birfy added this pull request to the merge queue Oct 30, 2026

Merged via the queue into main with commit b4e05ac Oct 30, 2026
13 of 14 checks passed

github-actions Bot removed the agent-pr Pull request opened by an agent label Oct 30, 2026

Birfy mentioned this pull request Oct 30, 2026

项目运作逻辑：Chief 与 Project Assistant 的身份边界、决策分级落到看板 #1831

Closed

Birfy mentioned this pull request Oct 30, 2026

fix(client): a running run on Settings → Workflows moves again (#1810) #1826

Merged

Navigation Menu

Repository navigation

Add the Project board's seven metrics behind a five-minute cache - #1835

Add the Project board's seven metrics behind a five-minute cache#1835
Birfy merged 6 commits into
mainfrom
dev/1829-project-metrics

Birfy commented Oct 30, 2026 •

edited

Loading

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Birfy commented Oct 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed

Reworked from the INC at caa61c3

Checkpoint

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

What blocks this tip

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

What blocks this tip

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

Uh oh!

Birfy commented Oct 30, 2026

INC 剩余项 — 全部关闭

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Birfy commented Oct 30, 2026 •

edited

Loading

Reworked from the INC at `caa61c3`