Skip to content

Releases

Monitoring Tools v1.0.75

Choose a tag to compare

@DingDingChae DingDingChae released this 15 Nov 06:01

One-click packing and detailed Compose operations

Copy files, folders or path text and choose Pack to ZIP or Pack to VHDX. Packing starts directly with progress. Verified success dismisses immediately; incomplete results remain visible and Activity reopens completed packing results.

Copy a selection and then the exact word vhd for a new pack, or vhd add to add to the latest successful pack in this application session. Choose VHDX selects another target. Additions use a verified staged disk, preserve existing user content, number name collisions and retain a rollback backup.

Compose startup now streams preflight, build, pull, start and health observation. It distinguishes command completion from readiness and offers previewed engine checks, retries, selected-service logs and restart. Both workflows use icon buttons with text labels.

Verification

  • Application source: 1d6541f.
  • Application SHA-256: 7a0d558610b75dea94865b64e1d773c894f3b22edfd939b84296df4e8c49413a.
  • Packing/native creation/native append: 23 passed, 0 failed, including staging cancellation, old/new content verification, collision numbering and retained backup equality.
  • Compose built-dialog checks: 5 passed, 0 failed. Focused controller checks passed separately; real startup observed an isolated healthy service.
  • Genuine source-bound images and detailed limitations are under docs/evidence/2026-11-15-packing-compose/ on main.
  • Application and companions were built locally through build-installer.bat. Documentation companions use the current reviewed documentation snapshot, whose revision is recorded in the attached manifest.

Full display-scale/minimum-layout coverage, assistive-technology interaction, native consent cancellation, actual low-space growth, crash recovery and every live Compose repair scenario remain unverified. The setup executable uses the existing self-installing distribution, not Squirrel.Windows. Executables are unsigned and may trigger unknown-publisher or SmartScreen warnings. Local build timing was not recorded as a precise duration.

廣東話

複製檔案或資料夾後,可以一按打包 ZIP 或 VHDX;驗證成功即收起視窗,有未完成嘅結果會留低。複製 vhd 建立新磁碟,複製 vhd add 加入本次程式執行期間最近成功嘅磁碟,亦可以用 Choose VHDX 指定目標。加入前會先做暫存複本,驗證舊檔同新檔,撞名就加編號,並保留回復備份。

Compose 有即時階段、記錄、服務狀態同有預覽嘅修復操作。打包檢查 23/23、Compose 視窗檢查 5/5 通過;未驗證項目如上,唔會當已完成。

Delivery manifest and documentation companion

The attached MonitoringTools-release-manifest.json records every expected asset's source revision, size and SHA-256. The current MonitoringTools-Site.exe includes explicit --data-dir support and was launched with a verified isolated profile. Packaged home, both updated articles, search, internal navigation and embedded current images were exercised; owned processes were closed. Its source is 8ba59c7, SHA-256 9c326dd537cc5e1a226b4b8dad85aa2826c0fc179942e4374a9863677c4ac42e. The initial documentation package is retained as MonitoringTools-Site-initial-v1.0.75.exe for provenance; use MonitoringTools-Site.exe for the current companion. The application tag and its verified binary remain unchanged.

Published-source statistics

Report-only run 43688274154 succeeded against immutable tag v1.0.75. This run measures source and does not replace native verification.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 1d6541f0016b with node scripts/line-counts.mjs --ref v1.0.75.

Category Files Lines Non-blank
Source 439 107,198 99,141
Tests 60 14,565 13,922
Styles and markup 16 2,003 1,948
Documentation 135 9,408 7,511
Configuration and data 32 2,403 2,340

Project total: 135,577 lines (124,862 non-blank).

Language Files Lines Non-blank
Batch 4 117 110
C# 466 118,270 109,751
CSS 3 756 735
HTML 1 55 50
JSON 22 1,739 1,739
JavaScript 13 2,794 2,645
MSBuild 3 89 83
Markdown 135 9,408 7,511
Other 4 38 36
PowerShell 15 485 465
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 2 515 460

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,910 1,910
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 160,437 lines (149,265 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 106,573 agent
Claude 26,197 agent
Claude Opus 5.5 2,807 agent

Agent-written lines: 135,577 of 135,577 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 135,577 lines and the counter found 135,577; they agree. Binary files skipped: 424.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 115,011 non-blank hand-written code lines (source, tests, styles and markup) and 7,511 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 115,011/50 + 7,511/150 = 2,350 days; 115,011/20 + 7,511/75 = 5,851 days.
  • Estimate: about 2,350 to 5,851 working days for one person, roughly 118 to 293 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.74

Choose a tag to compare

@github-actions github-actions released this 11 Nov 05:13
5102804

Monitoring Tools v1.0.74, Lamb and Scallion Bao · 蔥香羊肉包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.73

  • Read a copied file:/// address as a wording file path (5102804)
  • Apply copied wording paths and larger files; create servers off the UI thread (7a56748)
  • Record v1.0.73 figures and changelog (893e663)
  • Refresh screenshots for v1.0.73 (e832e6e)

Dim sum code name

Lamb and Scallion Bao · 蔥香羊肉包

Lamb and Scallion Bao, a dim sum dish

Photo: Lamb and Scallion Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 75 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-11T04:45:38Z
  • Workflow completed: 2026-11-11T05:13:55Z
  • Workflow duration: 00:28:17

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 5102804903ee with node scripts/line-counts.mjs --ref 5102804903ee39dd436a3efc7bd2c3da161ad7fd.

Category Files Lines Non-blank
Source 426 105,865 97,833
Tests 57 13,945 13,306
Styles and markup 16 2,003 1,948
Documentation 129 9,004 7,208
Configuration and data 27 2,234 2,175

Project total: 133,051 lines (122,470 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 452 116,383 107,893
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 9,004 7,208
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 479 428

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,904 1,904
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 157,905 lines (146,867 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,950 agent
Claude 26,294 agent
Claude Opus 5.5 2,807 agent

Agent-written lines: 133,051 of 133,051 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 133,051 lines and the counter found 133,051; they agree. Binary files skipped: 420.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 113,087 non-blank hand-written code lines (source, tests, styles and markup) and 7,208 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 113,087/50 + 7,208/150 = 2,310 days; 113,087/20 + 7,208/75 = 5,750 days.
  • Estimate: about 2,310 to 5,750 working days for one person, roughly 115 to 288 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.73

Choose a tag to compare

@github-actions github-actions released this 10 Nov 02:03
7543e2c

Monitoring Tools v1.0.73, Steamed Curry Beef Bao · 咖喱牛肉包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.72

  • Set the routed event before anything else on bridged drop arguments (7543e2c)
  • Keep the elevated drop hook alive and trace the bridge (ca3f64c)
  • Accept dropped files while running as administrator (491d7e8)
  • Record v1.0.72 figures and changelog (79c5532)
  • Refresh screenshots for v1.0.72 (92cdab9)

Dim sum code name

Steamed Curry Beef Bao · 咖喱牛肉包

Steamed Curry Beef Bao, a dim sum dish

Photo: Steamed Curry Beef Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 74 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-10T01:32:22Z
  • Workflow completed: 2026-11-10T02:03:26Z
  • Workflow duration: 00:31:04

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 7543e2cdb11f with node scripts/line-counts.mjs --ref 7543e2cdb11ffff14e24b1666ba2d1f3ef856b79.

Category Files Lines Non-blank
Source 426 105,736 97,714
Tests 55 13,787 13,151
Styles and markup 16 2,003 1,948
Documentation 129 8,985 7,195
Configuration and data 27 2,194 2,139

Project total: 132,705 lines (122,147 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 450 116,096 107,619
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 8,985 7,195
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 439 392

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,904 1,904
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 157,559 lines (146,544 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,985 agent
Claude 26,294 agent
Claude Opus 5.5 2,426 agent

Agent-written lines: 132,705 of 132,705 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 132,705 lines and the counter found 132,705; they agree. Binary files skipped: 420.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 112,813 non-blank hand-written code lines (source, tests, styles and markup) and 7,195 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 112,813/50 + 7,195/150 = 2,304 days; 112,813/20 + 7,195/75 = 5,737 days.
  • Estimate: about 2,304 to 5,737 working days for one person, roughly 115 to 287 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.72

Choose a tag to compare

@github-actions github-actions released this 10 Nov 00:11
a9b4e12

Monitoring Tools v1.0.72, Steamed Beef Bao · 牛肉包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.71

  • Keep every copy in a local Git repository with a history manager (a9b4e12)
  • Record v1.0.71 figures and changelog (5f3f241)
  • Refresh screenshots for v1.0.71 (a424559)

Dim sum code name

Steamed Beef Bao · 牛肉包

Steamed Beef Bao, a dim sum dish

Photo: Steamed Beef Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 73 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-09T23:40:52Z
  • Workflow completed: 2026-11-10T00:11:06Z
  • Workflow duration: 00:30:14

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit a9b4e12f020d with node scripts/line-counts.mjs --ref a9b4e12f020d2a27a019a186f5653bd66100a03f.

Category Files Lines Non-blank
Source 425 105,532 97,528
Tests 54 13,677 13,049
Styles and markup 16 2,003 1,948
Documentation 129 8,966 7,182
Configuration and data 27 2,174 2,121

Project total: 132,352 lines (121,828 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 448 115,782 107,331
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 8,966 7,182
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 419 374

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,898 1,898
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 157,200 lines (146,219 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,978 agent
Claude 26,294 agent
Claude Opus 5.5 2,080 agent

Agent-written lines: 132,352 of 132,352 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 132,352 lines and the counter found 132,352; they agree. Binary files skipped: 419.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 112,525 non-blank hand-written code lines (source, tests, styles and markup) and 7,182 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 112,525/50 + 7,182/150 = 2,298 days; 112,525/20 + 7,182/75 = 5,722 days.
  • Estimate: about 2,298 to 5,722 working days for one person, roughly 115 to 286 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.71

Choose a tag to compare

@github-actions github-actions released this 09 Nov 20:51
efe8f1c

Monitoring Tools v1.0.71, Pork and Cabbage Bao · 津白豬肉包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.70

  • Show a colour preview for colours in copied text and code (efe8f1c)
  • Record v1.0.70 figures and changelog (22bdd50)
  • Refresh screenshots for v1.0.70 (ee72d8c)

Dim sum code name

Pork and Cabbage Bao · 津白豬肉包

Pork and Cabbage Bao, a dim sum dish

Photo: Pork and Cabbage Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 72 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-09T20:21:26Z
  • Workflow completed: 2026-11-09T20:51:22Z
  • Workflow duration: 00:29:56

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit efe8f1c0cc9f with node scripts/line-counts.mjs --ref efe8f1c0cc9feca434988c0da4afe6b1c7f739cb.

Category Files Lines Non-blank
Source 423 104,584 96,659
Tests 53 13,541 12,919
Styles and markup 16 2,003 1,948
Documentation 129 8,926 7,148
Configuration and data 27 2,154 2,103

Project total: 131,208 lines (120,777 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 445 114,698 106,332
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 8,926 7,148
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 399 356

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,886 1,886
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 156,044 lines (145,156 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,986 agent
Claude 26,296 agent
Claude Opus 5.5 926 agent

Agent-written lines: 131,208 of 131,208 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 131,208 lines and the counter found 131,208; they agree. Binary files skipped: 418.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 111,526 non-blank hand-written code lines (source, tests, styles and markup) and 7,148 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 111,526/50 + 7,148/150 = 2,278 days; 111,526/20 + 7,148/75 = 5,672 days.
  • Estimate: about 2,278 to 5,672 working days for one person, roughly 114 to 284 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.70

Choose a tag to compare

@github-actions github-actions released this 09 Nov 19:55
cbec4d5

Monitoring Tools v1.0.70, Mushroom Vegetable Bao · 冬菇菜包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.69

  • Refresh the closeout prompt for the 2026-11-09 session (cbec4d5)
  • Record v1.0.69 figures and changelog (0f08dc2)
  • Refresh screenshots for v1.0.69 (9b1eed2)

Dim sum code name

Mushroom Vegetable Bao · 冬菇菜包

Mushroom Vegetable Bao, a dim sum dish

Photo: Mushroom Vegetable Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 71 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-09T19:24:04Z
  • Workflow completed: 2026-11-09T19:55:34Z
  • Workflow duration: 00:31:31

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit cbec4d5c2835 with node scripts/line-counts.mjs --ref cbec4d5c28358633afeff56a2a6fbbdecbcc969e.

Category Files Lines Non-blank
Source 421 104,232 96,329
Tests 52 13,437 12,819
Styles and markup 16 2,003 1,948
Documentation 129 8,891 7,123
Configuration and data 27 2,134 2,085

Project total: 130,697 lines (120,304 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 442 114,242 105,902
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 8,891 7,123
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 379 338

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,886 1,886
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 155,533 lines (144,683 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,979 agent
Claude 26,321 agent
Claude Opus 5.5 397 agent

Agent-written lines: 130,697 of 130,697 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 130,697 lines and the counter found 130,697; they agree. Binary files skipped: 418.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 111,096 non-blank hand-written code lines (source, tests, styles and markup) and 7,123 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 111,096/50 + 7,123/150 = 2,269 days; 111,096/20 + 7,123/75 = 5,650 days.
  • Estimate: about 2,269 to 5,650 working days for one person, roughly 113 to 282 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.69

Choose a tag to compare

@github-actions github-actions released this 09 Nov 08:53
1cdb21f

Monitoring Tools v1.0.69, Piglet Custard Bao · 豬仔奶黃包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.68

  • Make the plain-folder check use a folder outside any repository (1cdb21f)
  • Check copied folders and their toasts on every build (cfe86f4)
  • Translate choice lists and accept figures that read the same in both (b7ebea8)
  • Record repository folder remote pages and the sweep fixes (975ac9e)
  • List attached virtual disks with a real buffer and plain paths (1b287a4)
  • Keep page searches and narrow cards uncut at large text (38ad4cf)
  • Open a copied repository's remote pages, with a dropdown of every remote (4b1d3bb)
  • Offer Quick pack and the Virtual disks page from a copied file (b4e7d8f)
  • Keep the feature design boards in the repository (8ad85a3)
  • Bring the switch, menu builder, Base64 and folds to the project site (5371aae)
  • Refresh screenshots for v1.0.68 (dfebe1a)
  • Document the Virtual disks page and the features beside it (61fab7b)
  • Add the Virtual disks page, with Quick pack and real disk checks (b33c730)
  • Add the virtual disk engine: the disk service, checked jobs and Quick pack parts (67d0931)
  • Wrap the labels and button rows the stricter sweep found cut (9393047)
  • Make the regex builder and explanations resizable, with a reset (4940f7a)
  • Add the live response-time chart and folding search, filters and stats (7e08e80)
  • Put live controls in context menus and a filter in every dropdown (0b90ebc)
  • Split bilingual rail labels in the tab and teach the sweep about scrolling (46710b3)
  • Give the Markdown renderer emoji, relative links and an empty state (c28cf7b)
  • Record discarded changes so they can be copied back (facdf57)
  • Add the dim sum switch, Base64 beside the file and a local history (e0af234)

Dim sum code name

Piglet Custard Bao · 豬仔奶黃包

Piglet Custard Bao, a dim sum dish

Photo: Piglet Custard Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 70 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-09T08:22:20Z
  • Workflow completed: 2026-11-09T08:53:19Z
  • Workflow duration: 00:30:59

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 1cdb21f37d65 with node scripts/line-counts.mjs --ref 1cdb21f37d6505b11c0aeb430c2cfd5001c3452e.

Category Files Lines Non-blank
Source 421 104,232 96,329
Tests 52 13,437 12,819
Styles and markup 16 2,003 1,948
Documentation 129 8,851 7,089
Configuration and data 27 2,134 2,085

Project total: 130,657 lines (120,270 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 442 114,242 105,902
CSS 3 756 735
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,794 2,645
MSBuild 2 85 79
Markdown 129 8,851 7,089
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 379 338

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 105 15,760 15,303
Generated (generated screenshots and their index) 1 1,838 1,838
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 155,445 lines (144,601 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 103,956 agent
Claude 26,304 agent
Claude Opus 5.5 397 agent

Agent-written lines: 130,657 of 130,657 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 130,657 lines and the counter found 130,657; they agree. Binary files skipped: 410.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 111,096 non-blank hand-written code lines (source, tests, styles and markup) and 7,089 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 111,096/50 + 7,089/150 = 2,269 days; 111,096/20 + 7,089/75 = 5,649 days.
  • Estimate: about 2,269 to 5,649 working days for one person, roughly 113 to 282 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.68

Choose a tag to compare

@github-actions github-actions released this 07 Nov 19:46
0585e5c

Monitoring Tools v1.0.68, Hedgehog Red Bean Bao · 刺蝟豆沙包

Setup and portable exe are 205 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.67

  • Give the screenshot run thirty minutes (0585e5c)
  • Step past the look step in the guided look capture (317fcf3)
  • Record the green every-surface sweep for the four looks (9dcd113)
  • Wrap the labels and button rows the stricter sweep found cut (bd92da5)
  • Split bilingual rail labels in the tab and teach the sweep about scrolling (3af678d)
  • Stack bilingual rail labels and let the look figure shrink (0e269e7)
  • Keep the look previews out of the language layer from the start (6964461)
  • Widen the side rail and record the layout building blocks (c58b66f)
  • Fix what the second sweep found and make the sweep trust the layout (1d06a46)
  • Fix the corner mapping, fit every window to the screen and text size (0d99b57)
  • Add four looks and an every-surface sweep (9a04c73)
  • Record v1.0.67 figures and changelog (beea9e0)
  • Refresh screenshots for v1.0.67 (2247f94)

Dim sum code name

Hedgehog Red Bean Bao · 刺蝟豆沙包

Hedgehog Red Bean Bao, a dim sum dish

Photo: Hedgehog Red Bean Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 69 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-07T19:21:15Z
  • Workflow completed: 2026-11-07T19:46:51Z
  • Workflow duration: 00:25:36

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 0585e5c8a321 with node scripts/line-counts.mjs --ref 0585e5c8a321662bc0df87494be9b19714d5ecfb.

Category Files Lines Non-blank
Source 402 98,226 90,654
Tests 46 12,760 12,181
Styles and markup 16 1,934 1,885
Documentation 123 8,410 6,747
Configuration and data 27 2,091 2,046

Project total: 123,421 lines (113,513 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 417 107,867 99,891
CSS 3 687 672
HTML 1 55 50
JSON 19 1,610 1,610
JavaScript 13 2,486 2,343
MSBuild 2 85 79
Markdown 123 8,410 6,747
Other 4 38 36
PowerShell 14 459 439
SVG 1 1 1
Shell 1 97 92
XAML 11 1,191 1,162
XML 1 22 22
YAML 1 336 299

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 98 14,215 13,769
Generated (generated screenshots and their index) 1 1,712 1,712
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 146,538 lines (136,184 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 104,051 agent
Claude 18,972 agent
Claude Opus 5.5 398 agent

Agent-written lines: 123,421 of 123,421 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 123,421 lines and the counter found 123,421; they agree. Binary files skipped: 389.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 104,720 non-blank hand-written code lines (source, tests, styles and markup) and 6,747 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 104,720/50 + 6,747/150 = 2,139 days; 104,720/20 + 6,747/75 = 5,326 days.
  • Estimate: about 2,139 to 5,326 working days for one person, roughly 107 to 266 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.67

Choose a tag to compare

@github-actions github-actions released this 07 Nov 09:59
4ec291b

Monitoring Tools v1.0.67, Mushroom-Shaped Custard Bao · 蘑菇奶黃包

Setup and portable exe are 203 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.66

  • Open every page by default, say cut or copied, keep updates quiet (4ec291b)
  • Record v1.0.66 figures and changelog (c987416)
  • Refresh screenshots for v1.0.66 (8472d69)

Dim sum code name

Mushroom-Shaped Custard Bao · 蘑菇奶黃包

Mushroom-Shaped Custard Bao, a dim sum dish

Photo: Mushroom-Shaped Custard Bao, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 68 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-07T09:40:52Z
  • Workflow completed: 2026-11-07T09:59:06Z
  • Workflow duration: 00:18:14

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit 4ec291b9d009 with node scripts/line-counts.mjs --ref 4ec291b9d0093ee6e9605e3ab5197766725666b7.

Category Files Lines Non-blank
Source 393 96,613 89,142
Tests 46 12,760 12,181
Styles and markup 16 1,896 1,847
Documentation 122 8,297 6,657
Configuration and data 27 1,939 1,896

Project total: 121,505 lines (111,723 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 408 106,265 98,390
CSS 3 687 672
HTML 1 55 50
JSON 19 1,487 1,487
JavaScript 13 2,486 2,343
MSBuild 2 81 75
Markdown 122 8,297 6,657
Other 4 38 36
PowerShell 14 448 428
SVG 1 1 1
Shell 1 97 92
XAML 11 1,153 1,124
XML 1 22 22
YAML 1 311 276

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 85 12,587 12,148
Generated (generated screenshots and their index) 1 1,700 1,700
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 142,982 lines (132,761 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 104,253 agent
Claude 16,835 agent
Claude Opus 5.5 417 agent

Agent-written lines: 121,505 of 121,505 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 121,505 lines and the counter found 121,505; they agree. Binary files skipped: 379.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 103,170 non-blank hand-written code lines (source, tests, styles and markup) and 6,657 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 103,170/50 + 6,657/150 = 2,108 days; 103,170/20 + 6,657/75 = 5,247 days.
  • Estimate: about 2,108 to 5,247 working days for one person, roughly 105 to 262 working months. This is information about scale, not a claim of merit.

Monitoring Tools v1.0.66

Choose a tag to compare

@github-actions github-actions released this 07 Nov 02:54
e96ced0

Monitoring Tools v1.0.66, Scallion Flower Roll · 蔥花卷

Setup and portable exe are 203 MB each: FFmpeg, FFprobe and portable Git are bundled inside, so conversion and pushing work offline with nothing else to install. MonitoringTools-BuildTool.exe is a portable desktop front end for build.bat and build-installer.bat; MonitoringTools-Site.exe is the project site and documentation as a portable offline app.

Changes since v1.0.65

  • Keep built-in extension scripts plain ASCII (e96ced0)
  • Ship eleven built-in extensions (054d7b2)
  • Record v1.0.64 figures and changelog (21477c7)
  • Refresh screenshots for v1.0.64 (753d3f0)

Dim sum code name

Scallion Flower Roll · 蔥花卷

Scallion Flower Roll, a dim sum dish

Photo: Scallion Flower Roll, published in the public dim sum photo catalogue. The photo is linked, not copied. Code names are picked by release order from scripts/dim-sum-code-names.json (entry 67 of 118), so each release takes a different dish.

Workflow timing

  • Workflow started: 2026-11-07T02:37:07Z
  • Workflow completed: 2026-11-07T02:54:04Z
  • Workflow duration: 00:16:58

Measured by the workflow itself, from the start of the build job to the end of the publication step.

Checks

By project policy this workflow runs no tests, lint or other gating checks, so this release is not described as tested. What it did do: ran build-installer.bat (the build), rendered the app's screenshots (outcome: success), built the desktop tools, and verified below that this is a normal release with every asset attached.

Line counts

Counted by this release workflow, not by hand, with node scripts/line-counts.mjs (runnable locally on any commit).

Counted at commit e96ced04b626 with node scripts/line-counts.mjs --ref e96ced04b626b229b02aa0dd6030530b6e9e2e74.

Category Files Lines Non-blank
Source 390 96,337 88,892
Tests 45 12,695 12,119
Styles and markup 16 1,872 1,823
Documentation 122 8,273 6,643
Configuration and data 27 1,938 1,895

Project total: 121,115 lines (111,372 non-blank).

Language Files Lines Non-blank
Batch 3 77 70
C# 404 105,924 98,078
CSS 3 687 672
HTML 1 55 50
JSON 19 1,487 1,487
JavaScript 13 2,486 2,343
MSBuild 2 80 74
Markdown 122 8,273 6,643
Other 4 38 36
PowerShell 14 448 428
SVG 1 1 1
Shell 1 97 92
XAML 11 1,129 1,100
XML 1 22 22
YAML 1 311 276

Excluded from the project total, still counted in the grand total:

Excluded group Files Lines Non-blank
Design prototypes (historical design prototypes, not shipped code) 85 12,587 12,148
Generated (generated screenshots and their index) 1 1,700 1,700
Generated (lockfile) 2 7,190 7,190

Grand total of everything counted: 142,592 lines (132,410 non-blank).

Surviving lines by author (git blame, project total only):

Author Lines Kind
Claude Fable 5.1 104,256 agent
Claude 16,442 agent
Claude Opus 5.5 417 agent

Agent-written lines: 121,115 of 121,115 (100.0%). Rule: a line is agent-written when its commit author name looks like an automation identity or the commit has a Co-Authored-By trailer naming an agent. This is a statement of fact, neither a boast nor an apology.

Consistency check: blame attributes 121,115 lines and the counter found 121,115; they agree. Binary files skipped: 379.

How long a human would have taken

This is an estimate, not a measurement: nobody wrote this project by hand, and the true figure could be well outside this range.

  • Inputs: 102,834 non-blank hand-written code lines (source, tests, styles and markup) and 6,643 non-blank documentation lines, taken from the line counts above. Generated files, lockfiles, design prototypes and vendored or build-output trees are excluded, exactly as in the counts.
  • Assumed rates: code 50 lines per working day (fast) to 20 (slow); documentation 150 to 75 lines per working day; 8-hour days; 20 working days per month; no complexity multiplier.
  • Arithmetic: 102,834/50 + 6,643/150 = 2,101 days; 102,834/20 + 6,643/75 = 5,230 days.
  • Estimate: about 2,101 to 5,230 working days for one person, roughly 105 to 262 working months. This is information about scale, not a claim of merit.