gea-program 0.89.0__tar.gz → 0.91.0__tar.gz

{gea_program-0.89.0 → gea_program-0.91.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gea-program
-Version: 0.89.0
+Version: 0.91.0
 Summary: GEA-Program: downhole gauge monitoring - canonical measurement records, quality rules, drift evaluation with a re-fit change log, well-test validation, alarm management, model cards, store-and-forward, monthly SLA measurement, FAT/SAT protocols and a dashboard, generated from live objects in the client's reporting outline.
 Author: Daniel T. Murphy
 License: MPL-2.0
@@ -847,7 +847,7 @@ unsigned, the key hand-overs - and shows the reports as they were signed. A
 reader made from the workspace knows the site's key fingerprints, so it
 says whether a dossier is the site's; it allows no network request, and it
 leaves the trusted time-stamp to `verify_dossier.py`. For a client who wants
-it installed, every release also carries `GEA-Reader-Setup-0.89.0.exe`: GEA
+it installed, every release also carries `GEA-Reader-Setup-0.91.0.exe`: GEA
 Reader as a Windows program of its own - its own icon and taskbar button,
 Check with GEA Reader on a dossier's right-click menu, fingerprints the client
 saves kept on that computer, nothing of GEA-Program. `gea help reader`.
@@ -934,6 +934,26 @@ the window. The Dutch offshore well L07-01 (NLOG open data) is the worked
 example. The **Pore pressure** tab, `gea pore-pressure`,
 `gea help pore-pressure`.
 
+### Frac treatment
+
+Each fracturing stage from its own pumping record - the treating pressure,
+the slurry rate and the proppant concentration, second by second, as the
+frac service company gave them (a spreadsheet with its stacked header, a
+frac van's data-acquisition export, or a plain CSV). With nothing fitted to
+a model of the fracture, the page reads what was pumped beside the record's
+own totalisers; the ISIP - a straight line fitted to the pressure after the
+ringing has died down and read back to the moment the rate reached zero,
+over three windows, with the spread between them as its range; the friction
+at the last rate held, and where the rate was stepped down its two parts,
+one with the square of the rate (the pipe and the perforations) and one
+with its root (the path just outside the wellbore); the pressure at 5, 10
+and 15 minutes and against Nolte's G, with a closure candidate offered only
+where the record supports one; and a step-rate test where there was one.
+With the depth of the perforations declared, the bottomhole ISIP and its
+gradient. It hands the Frac hits tab each stage's times. The **Frac
+treatment** tab, `gea frac-treatment`, `gea help frac-treatment`; an
+assistant reads it as the `frac_treatment` tool.
+
 ### Frac hits
 
 What each fracturing stage did to the pressure in the wells around it. A
@@ -1073,6 +1093,83 @@ eras of the protocol are spoken: the stateless revision 2026-07-28 and the
 `initialize` handshake of 2025-11-25 and earlier. The **Assistant access**
 tab (one button adds it to Claude Desktop), `gea mcp`, `gea help mcp`.
 
+### Benchmark
+
+The wells of a pad against one another, and each against the best the pad
+has done. Every well with a drilling record is measured the same way from
+its own record - the footage, the days from its first stand to its last,
+feet per day, the rate on bottom, rotary and sliding, the median connection
+weight to weight, the trip speeds - and ranked on each count. Then each
+well is set against the pad's best: the well it would have been had every
+stretch of hole been drilled at the rate of whichever well was fastest
+through that stretch (300 ft or more of it), and every connection made in
+the pad's best quarter. The gap is hours the pad has already shown can be
+saved, on some well in that stretch - not a forecast, and not a cause: the
+bit, the motor, the mud and the hole size are not in the record. The
+**Benchmark** tab, `gea benchmark`, `gea help benchmark`; an assistant
+reads it as the `benchmark` tool.
+
+### Public data: a real pad
+
+A pad anyone may check. The Utah FORGE project - the U.S. Department of
+Energy's geothermal field laboratory near Milford, Utah - publishes the
+rig recorders of five wells drilled through the same basin fill and
+granite between 2017 and 2023, under Creative Commons Attribution 4.0.
+`gea public-pad` turns those files into a site of its own, so the rig
+time, the roadmap, the drilling alerts and the benchmark run on real
+records before any client's. The program does not contain the files and
+does not fetch them: the site downloads them in a browser from the
+Geothermal Data Repository, names the folder, and the program checks each
+file against the size and the SHA-256 it had when this release was checked
+with it, converts the three layouts that are not the recorder's own
+export, attaches each well, and keeps on the record what was done to
+each - 16A(78)-32's bit depth is RECONSTRUCTED from the block and the
+slips and is marked so on every page. Every page and report of that site
+ends with the credit the licence asks for.
+
+What this release made of them, on the five files as published:
+
+| Well | Drilled, ft | Days | ft/day | On bottom, ft/h | Median connection, min |
+|---|---|---|---|---|---|
+| 58-32 (2017) | 6,288 | 43.5 | 145 | 15.9 | 14.4 |
+| 16A(78)-32 (2020) | 11,035 | 67.8 | 163 | 34.4 | 11.3 |
+| 56-32 (2021) | 9,232 | 19.0 | 487 | 46.6 | 7.5 |
+| 78B-32 (2021) | 9,372 | 29.1 | 322 | 84.7 | 7.7 |
+| 16B(78)-32 (2023) | 10,490 | 52.4 | 200 | 45.7 | 10.2 |
+
+Against the pad's best the five wells spent 812 of their 1,256 on-bottom
+hours beyond it. The roadmap's own check on them is split - running nearer
+the window was the faster half on two wells and the slower on two - which
+is the page saying, of wells drilled six years apart in three hole sizes,
+that one well's parameters are not the next well's roadmap. The drilling
+alerts, replayed, find 27 motor stalls on the three wells whose records
+can show one, three falls in off-bottom pressure on 78B-32 that no trip followed
+and one on 58-32 that a trip out of the hole followed within twelve hours.
+
+The same site takes the published pumping records of the two deviated
+wells' stimulation - three stages on 16A(78)-32 in April 2022, nine more
+and four on 16B(78)-32 in April 2024 - when those files are in the folder
+too, and the Frac treatment tab reads all sixteen: 132,132 bbl of slurry
+and 2,969,800 lbm of proppant by the records' own rates, fifteen of the
+sixteen volumes within 0.6 % of the record's own totaliser (the sixteenth
+3.6 % under it: that totaliser also counted the lines being primed); an
+ISIP at every stage, 3,289 to 5,664 psi at the surface; thirteen stages
+stepped down to the shut-in. The service company's reports are published with the
+2022 stages, so the page can be checked against them: for stage 1 the
+company gives a final ISIP of 4,019 psi and 3,715, 3,582 and 3,501 psi
+after 5, 10 and 15 minutes, and this page reads 3,985 psi (3,975 to 3,997)
+and 3,720, 3,585 and 3,486; for stage 2, 3,918 psi and 3,664, 3,565 and
+3,506 against 3,859 (3,852 to 3,862) and 3,665, 3,572 and 3,508. The page's
+ISIP is the lower because it is read back along the decline, not taken at
+the top of the ringing. No
+stage's fall-off shows a closure: the records stop a quarter of an hour
+after the pumps, and the page says so and offers none.
+
+Data: Utah FORGE, Energy & Geoscience Institute at the University of Utah,
+funded by the U.S. Department of Energy; Geothermal Data Repository,
+gdr.openei.org; CC BY 4.0. The **Public data** tab, `gea public-pad`,
+`gea help public-data`.
+
 ### Plan vs actual and the survey tools
 
 Each well against its directional plan: at every survey station, how far
@@ -1737,7 +1834,7 @@ attaches the zips to the GitHub release of that tag.
 
 ### The Windows installer
 
-Every release also carries `GEA-Program-Setup-0.89.0.exe` (for 0.89.0): the
+Every release also carries `GEA-Program-Setup-0.91.0.exe` (for 0.91.0): the
 same Windows kit installed like any Windows program, for the signed-in user
 alone and with no administrator rights (`%LOCALAPPDATA%\Programs\GEA-Program`).
 It asks for the site workspace (an existing one such as `C:\site` is used as
@@ -1756,7 +1853,7 @@ it, removes the program and leaves the workspace. Silent, for a site's
 software deployment:
 
 ```
-GEA-Program-Setup-0.89.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
+GEA-Program-Setup-0.91.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
 ```
 
 The setup is built by Inno Setup 6 from `tools/installer.iss` in the same

{gea_program-0.89.0 → gea_program-0.91.0}/README.md

@@ -808,7 +808,7 @@ unsigned, the key hand-overs - and shows the reports as they were signed. A
 reader made from the workspace knows the site's key fingerprints, so it
 says whether a dossier is the site's; it allows no network request, and it
 leaves the trusted time-stamp to `verify_dossier.py`. For a client who wants
-it installed, every release also carries `GEA-Reader-Setup-0.89.0.exe`: GEA
+it installed, every release also carries `GEA-Reader-Setup-0.91.0.exe`: GEA
 Reader as a Windows program of its own - its own icon and taskbar button,
 Check with GEA Reader on a dossier's right-click menu, fingerprints the client
 saves kept on that computer, nothing of GEA-Program. `gea help reader`.
@@ -895,6 +895,26 @@ the window. The Dutch offshore well L07-01 (NLOG open data) is the worked
 example. The **Pore pressure** tab, `gea pore-pressure`,
 `gea help pore-pressure`.
 
+### Frac treatment
+
+Each fracturing stage from its own pumping record - the treating pressure,
+the slurry rate and the proppant concentration, second by second, as the
+frac service company gave them (a spreadsheet with its stacked header, a
+frac van's data-acquisition export, or a plain CSV). With nothing fitted to
+a model of the fracture, the page reads what was pumped beside the record's
+own totalisers; the ISIP - a straight line fitted to the pressure after the
+ringing has died down and read back to the moment the rate reached zero,
+over three windows, with the spread between them as its range; the friction
+at the last rate held, and where the rate was stepped down its two parts,
+one with the square of the rate (the pipe and the perforations) and one
+with its root (the path just outside the wellbore); the pressure at 5, 10
+and 15 minutes and against Nolte's G, with a closure candidate offered only
+where the record supports one; and a step-rate test where there was one.
+With the depth of the perforations declared, the bottomhole ISIP and its
+gradient. It hands the Frac hits tab each stage's times. The **Frac
+treatment** tab, `gea frac-treatment`, `gea help frac-treatment`; an
+assistant reads it as the `frac_treatment` tool.
+
 ### Frac hits
 
 What each fracturing stage did to the pressure in the wells around it. A
@@ -1034,6 +1054,83 @@ eras of the protocol are spoken: the stateless revision 2026-07-28 and the
 `initialize` handshake of 2025-11-25 and earlier. The **Assistant access**
 tab (one button adds it to Claude Desktop), `gea mcp`, `gea help mcp`.
 
+### Benchmark
+
+The wells of a pad against one another, and each against the best the pad
+has done. Every well with a drilling record is measured the same way from
+its own record - the footage, the days from its first stand to its last,
+feet per day, the rate on bottom, rotary and sliding, the median connection
+weight to weight, the trip speeds - and ranked on each count. Then each
+well is set against the pad's best: the well it would have been had every
+stretch of hole been drilled at the rate of whichever well was fastest
+through that stretch (300 ft or more of it), and every connection made in
+the pad's best quarter. The gap is hours the pad has already shown can be
+saved, on some well in that stretch - not a forecast, and not a cause: the
+bit, the motor, the mud and the hole size are not in the record. The
+**Benchmark** tab, `gea benchmark`, `gea help benchmark`; an assistant
+reads it as the `benchmark` tool.
+
+### Public data: a real pad
+
+A pad anyone may check. The Utah FORGE project - the U.S. Department of
+Energy's geothermal field laboratory near Milford, Utah - publishes the
+rig recorders of five wells drilled through the same basin fill and
+granite between 2017 and 2023, under Creative Commons Attribution 4.0.
+`gea public-pad` turns those files into a site of its own, so the rig
+time, the roadmap, the drilling alerts and the benchmark run on real
+records before any client's. The program does not contain the files and
+does not fetch them: the site downloads them in a browser from the
+Geothermal Data Repository, names the folder, and the program checks each
+file against the size and the SHA-256 it had when this release was checked
+with it, converts the three layouts that are not the recorder's own
+export, attaches each well, and keeps on the record what was done to
+each - 16A(78)-32's bit depth is RECONSTRUCTED from the block and the
+slips and is marked so on every page. Every page and report of that site
+ends with the credit the licence asks for.
+
+What this release made of them, on the five files as published:
+
+| Well | Drilled, ft | Days | ft/day | On bottom, ft/h | Median connection, min |
+|---|---|---|---|---|---|
+| 58-32 (2017) | 6,288 | 43.5 | 145 | 15.9 | 14.4 |
+| 16A(78)-32 (2020) | 11,035 | 67.8 | 163 | 34.4 | 11.3 |
+| 56-32 (2021) | 9,232 | 19.0 | 487 | 46.6 | 7.5 |
+| 78B-32 (2021) | 9,372 | 29.1 | 322 | 84.7 | 7.7 |
+| 16B(78)-32 (2023) | 10,490 | 52.4 | 200 | 45.7 | 10.2 |
+
+Against the pad's best the five wells spent 812 of their 1,256 on-bottom
+hours beyond it. The roadmap's own check on them is split - running nearer
+the window was the faster half on two wells and the slower on two - which
+is the page saying, of wells drilled six years apart in three hole sizes,
+that one well's parameters are not the next well's roadmap. The drilling
+alerts, replayed, find 27 motor stalls on the three wells whose records
+can show one, three falls in off-bottom pressure on 78B-32 that no trip followed
+and one on 58-32 that a trip out of the hole followed within twelve hours.
+
+The same site takes the published pumping records of the two deviated
+wells' stimulation - three stages on 16A(78)-32 in April 2022, nine more
+and four on 16B(78)-32 in April 2024 - when those files are in the folder
+too, and the Frac treatment tab reads all sixteen: 132,132 bbl of slurry
+and 2,969,800 lbm of proppant by the records' own rates, fifteen of the
+sixteen volumes within 0.6 % of the record's own totaliser (the sixteenth
+3.6 % under it: that totaliser also counted the lines being primed); an
+ISIP at every stage, 3,289 to 5,664 psi at the surface; thirteen stages
+stepped down to the shut-in. The service company's reports are published with the
+2022 stages, so the page can be checked against them: for stage 1 the
+company gives a final ISIP of 4,019 psi and 3,715, 3,582 and 3,501 psi
+after 5, 10 and 15 minutes, and this page reads 3,985 psi (3,975 to 3,997)
+and 3,720, 3,585 and 3,486; for stage 2, 3,918 psi and 3,664, 3,565 and
+3,506 against 3,859 (3,852 to 3,862) and 3,665, 3,572 and 3,508. The page's
+ISIP is the lower because it is read back along the decline, not taken at
+the top of the ringing. No
+stage's fall-off shows a closure: the records stop a quarter of an hour
+after the pumps, and the page says so and offers none.
+
+Data: Utah FORGE, Energy & Geoscience Institute at the University of Utah,
+funded by the U.S. Department of Energy; Geothermal Data Repository,
+gdr.openei.org; CC BY 4.0. The **Public data** tab, `gea public-pad`,
+`gea help public-data`.
+
 ### Plan vs actual and the survey tools
 
 Each well against its directional plan: at every survey station, how far
@@ -1698,7 +1795,7 @@ attaches the zips to the GitHub release of that tag.
 
 ### The Windows installer
 
-Every release also carries `GEA-Program-Setup-0.89.0.exe` (for 0.89.0): the
+Every release also carries `GEA-Program-Setup-0.91.0.exe` (for 0.91.0): the
 same Windows kit installed like any Windows program, for the signed-in user
 alone and with no administrator rights (`%LOCALAPPDATA%\Programs\GEA-Program`).
 It asks for the site workspace (an existing one such as `C:\site` is used as
@@ -1717,7 +1814,7 @@ it, removes the program and leaves the workspace. Silent, for a site's
 software deployment:
 
 ```
-GEA-Program-Setup-0.89.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
+GEA-Program-Setup-0.91.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
 ```
 
 The setup is built by Inno Setup 6 from `tools/installer.iss` in the same

{gea_program-0.89.0 → gea_program-0.91.0}/gea/__init__.py

@@ -123,7 +123,7 @@ from .profile_catalog import (
     read_pangaea_txt,
 )
 
-__version__ = "0.89.0"
+__version__ = "0.91.0"
 __all__ = [
     "aging_rate", "rate_psi_yr", "accuracy_psi",
     "Sensor", "SimulatorConfig", "DownholeEngine",

{gea_program-0.89.0 → gea_program-0.91.0}/gea/__main__.py

@@ -677,6 +677,32 @@ def main(argv=None) -> int:
     p_os.add_argument("--actor", type=str, default="cli")
     p_os.add_argument("--json", action="store_true")
 
+    p_bm = sub.add_parser("benchmark", help="the wells of a pad against one another: feet per day, on-bottom rate, connections and trips ranked, and each well against the pad's best - every stretch at the rate of the fastest well through it")
+    p_bm.add_argument("--workspace", type=str, default=None, help="the workspace folder; without one the self-test runs")
+    p_bm.add_argument("--write", action="store_true", help="write reports/benchmark/benchmark.json, .md, .csv and stretches.csv")
+    p_bm.add_argument("--actor", type=str, default="cli")
+    p_bm.add_argument("--json", action="store_true")
+    p_ft = sub.add_parser("frac-treatment", help="each fracturing stage from its own pumping record: what was pumped, the ISIP read back through the ringing with its range, the friction and its two parts from a step-down, the fall-off against G, a step-rate test - nothing fitted to a model of the fracture")
+    p_ft.add_argument("--workspace", type=str, default=None, help="the workspace folder; without one the self-test runs (stages built with every answer known)")
+    p_ft.add_argument("--well", type=str, default=None, help="a well, by its name or id: with --stage, that stage in full")
+    p_ft.add_argument("--stage", type=str, default=None, help="the stage (1, 3R, 6A)")
+    p_ft.add_argument("--attach", type=str, default=None, help="a stage's treatment record to keep (CSV or Excel: the pressure, the rate and the proppant, second by second); needs --well, --stage and --source")
+    p_ft.add_argument("--start", type=str, default=None, help="--attach: the record's first moment, for a file that only has elapsed time (2026-08-03T06:00:00)")
+    p_ft.add_argument("--tvd", type=float, default=None, help="declare the true vertical depth of the perforations, ft: for --stage, or every stage of --well; needs --source")
+    p_ft.add_argument("--fluid", type=float, default=None, help="with --tvd: the gradient of the fluid in the well at the shut-in, psi/ft (fresh water, 0.433, when not given)")
+    p_ft.add_argument("--source", type=str, default="", help="where the record, or the depth, came from")
+    p_ft.add_argument("--to-frac-hits", action="store_true", help="give the Frac hits page --well's stage times, read from these records")
+    p_ft.add_argument("--write", action="store_true", help="write reports/frac_treatment/frac_treatment.json, .md, stages.csv and a stage table a well")
+    p_ft.add_argument("--actor", type=str, default="cli")
+    p_ft.add_argument("--json", action="store_true")
+    p_pp = sub.add_parser("public-pad", help="a real pad from public data: the Utah FORGE wells' published rig recorders (CC BY 4.0) made into a site of their own - the files to get and where, checked against their sizes and hashes, converted and attached; the program fetches nothing")
+    p_pp.add_argument("--folder", type=str, default=None, help="the folder the downloaded files are in; with nothing else, lists each file and whether it is there. Without a folder the self-test runs (stand-ins in each published layout)")
+    p_pp.add_argument("--verify", action="store_true", help="hash each file that is there against the SHA-256 this release was checked with")
+    p_pp.add_argument("--build", action="store_true", help="make the site at --site from the files in --folder, or add to it the wells it does not have yet")
+    p_pp.add_argument("--site", type=str, default=None, help="--build: the folder the site's workspace is made in")
+    p_pp.add_argument("--list", action="store_true", help="list the dataset's files, sizes, hashes and where each is published, and exit")
+    p_pp.add_argument("--actor", type=str, default="cli")
+    p_pp.add_argument("--json", action="store_true")
     p_mc = sub.add_parser("mcp", help="the site, readable by an assistant: a Model Context Protocol server on standard input and output - local (no port), read-only (every tool reads one of the program's pages, none changes anything), logged; with --workspace alone it serves until its input closes")
     p_mc.add_argument("--workspace", type=str, default=None, help="the workspace folder; without one the self-test runs (both eras of the protocol against a labelled site)")
     p_mc.add_argument("--allow", type=str, default=None, help="serve only these tools this run, comma-separated (never more than the site offers)")
@@ -3575,6 +3601,102 @@ def main(argv=None) -> int:
             for v in f_["versions"][: (50 if a.family else 3)]:
                 print(f"      {v['utc']}  {v.get('report_id') or ''}  reports/{v['dir']}")
         return 0
+    elif a.cmd == "benchmark":
+        import json as _json
+        from . import benchmark as _BM
+        from .cli import _safe_stdout
+        from .workspace import Workspace, WorkspaceError
+        _safe_stdout()
+        if not a.workspace:
+            r = _BM.selftest()
+            print("\n".join(f"{'PASS' if c['pass'] else 'FAIL'}  {c['check']}: {c['value']}" for c in r["checks"]) + f"\n{'OK' if r['ok'] else 'FAILED'} - {r['label']}")
+            return 0 if r["ok"] else 1
+        try:
+            ws = Workspace(a.workspace)
+            if a.write:
+                from . import __version__ as _ver90b
+                r = _BM.write_report(ws, _ver90b, a.actor)
+                print(f"written: {', '.join(r['files'])} under {r['folder']}")
+            p = _BM.page(ws)
+        except (_BM.BenchmarkError, WorkspaceError, ValueError, OSError) as e:
+            raise SystemExit(f"benchmark: {e.args[0] if e.args else e}")
+        print(_json.dumps(p, default=str) if a.json else _BM.text(p))
+        return 0
+    elif a.cmd == "frac-treatment":
+        import json as _json
+        from . import frac_treatment as _FT
+        from .cli import _safe_stdout
+        from .workspace import Workspace, WorkspaceError
+        _safe_stdout()
+        if not a.workspace:
+            r = _FT.selftest()
+            print("\n".join(f"{'PASS' if c['pass'] else 'FAIL'}  {c['check']}: {c['value']}" for c in r["checks"]) + f"\n{'OK' if r['ok'] else 'FAILED'} - {r['label']}")
+            return 0 if r["ok"] else 1
+        try:
+            ws = Workspace(a.workspace)
+            wid = None
+            if a.well:
+                wid = next((w["id"] for w in ws.wells() if a.well in (w["id"], w.get("display"))), None)
+                if wid is None:
+                    raise SystemExit(f"frac-treatment: no well {a.well!r} in this workspace")
+            if a.attach:
+                if not (wid and a.stage):
+                    raise SystemExit("frac-treatment: --attach needs --well and --stage")
+                with open(a.attach, "rb") as f_:
+                    m_ = _FT.attach(ws, wid, a.stage, a.attach, f_.read(), a.actor, a.source, a.start)
+                print(f"kept: stage {m_['stage']}, {m_['samples']:,} samples from {m_['start'] or 'its first sample'} ({m_['layout']}); read as " + ", ".join(f"{k}: {v}" for k, v in m_["read_as"].items()))
+            if a.tvd is not None:
+                if not wid:
+                    raise SystemExit("frac-treatment: --tvd needs --well")
+                d_ = _FT.declare(ws, wid, a.actor, a.source, a.tvd, a.fluid, a.stage)
+                print(f"declared for stage {', '.join(d_['stages'])}: perforations at {d_['tvd_ft']:,.0f} ft TVD, fluid {d_['fluid_psi_ft']:g} psi/ft")
+            if a.to_frac_hits:
+                if not wid:
+                    raise SystemExit("frac-treatment: --to-frac-hits needs --well")
+                h_ = _FT.to_frac_hits(ws, wid, a.actor)
+                print(f"the Frac hits page has {h_['stages']} stage(s) for this well, {h_['first'][:16]} to {h_['last'][:16]}")
+            if a.write:
+                from . import __version__ as _ver91
+                r = _FT.write_report(ws, _ver91, a.actor)
+                print(f"written: {', '.join(r['files'])} under {r['folder']}")
+            p = _FT.page(ws, wid, a.stage)
+        except (_FT.TreatmentError, WorkspaceError, KeyError, ValueError, OSError) as e:
+            raise SystemExit(f"frac-treatment: {e.args[0] if e.args else e}")
+        print(_json.dumps(p, default=str) if a.json else _FT.text(p))
+        return 0
+    elif a.cmd == "public-pad":
+        import json as _json
+        from . import public_pad as _PP
+        from .cli import _safe_stdout
+        _safe_stdout()
+        if not a.folder and not a.list:
+            r = _PP.selftest()
+            print("\n".join(f"{'PASS' if c['pass'] else 'FAIL'}  {c['check']}: {c['value']}" for c in r["checks"]) + f"\n{'OK' if r['ok'] else 'FAILED'} - {r['label']}")
+            return 0 if r["ok"] else 1
+        try:
+            if a.build:
+                if not a.site:
+                    raise SystemExit("public-pad: --build needs --site, the folder the site is made in")
+                last_ = {"t": ""}
+
+                def say_(d_):
+                    t_ = f"{d_.get('well', '')} {d_.get('step', '')}".strip()
+                    if t_ != last_["t"] and d_.get("step") != "done":
+                        last_["t"] = t_
+                        print(f"  {d_.get('n', '')}/{d_.get('of', '')} {t_}", flush=True)
+                r = _PP.build(a.folder, a.site, a.actor, verify=True, progress=say_)
+                print(f"{r['name']} at {r['path']}: " + (f"added {', '.join(r['added'])}" if r["added"] else "nothing to add") + f"; it has {', '.join(r['wells'])}")
+                if r.get("stages"):
+                    print(f"  and the pumping record of {len(r['stages'])} stimulation stage(s): {', '.join(r['stages'])}")
+                for e_ in r["record"]["wells"]:
+                    for n_ in e_["notes"]:
+                        print(f"  {e_['well']}: {n_}")
+                return 0
+            s_ = _PP.status(a.folder or "", verify=a.verify)
+        except (_PP.PublicPadError, OSError) as e:
+            raise SystemExit(f"public-pad: {e.args[0] if e.args else e}")
+        print(_json.dumps(s_, default=str) if a.json else _PP.text(s_))
+        return 0
     elif a.cmd == "mcp":
         import json as _json
         from . import mcp_server as _MC