Skip to content

Monitoring Tools v1.0.75

Latest

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.