Skip to content

v0.23.1 — Inspectable application diagnostics

Latest

Choose a tag to compare

@ShanilKoshitha ShanilKoshitha released this 21 Oct 19:40
f2e8b5a

v0.23.1 — Inspectable application diagnosis and route inventory

Normal fresh applications now use format 17 and the immutable, publicly verified
v0.23.0 runtime. The scaffold includes ordinary application-owned Go under
cmd/diagnostics and internal/diagnostics; no runtime discovery or reflection.

  • forge doctor aggregates independent HTTP, worker/mail, scheduler, and database
    configuration checks, actual application construction, PostgreSQL availability,
    read-only migration verification, ORM/view freshness, and embedded asset
    validity. Failed/skipped checks exit nonzero with safe repair guidance, not raw
    driver/compiler errors, credentials, SQL, or panic stacks. It never repairs.
  • forge routes:list prints actual production-router registrations, including
    generated resources and handwritten routes, without requiring reachable
    PostgreSQL or starting services. It is not an inferred authorization report.
  • Diagnostic subprocesses use readonly modules, disabled workspaces, external
    shared caches/temporary builds, bounded output and deadlines, and the existing
    complete process-tree cancellation boundary. No implicit migrations, generated
    source publication, background service startup, SMTP connection, or job claims.
  • Application checks, constructors and route wiring remain explicit ordinary Go.
    Replace them directly. Custom application code is trusted code, not sandboxed;
    it must remain side-effect-free when used for inspection. Direct Go commands
    remain available with documented caller-owned build/cache and output boundaries.
  • Existing applications are not rewritten or injected with diagnostics. Older
    formats receive an unsupported-command explanation. Historical generation
    contracts and the authentic public format-16 compatibility workflow remain.

The runtime was published and verified before this scaffold adopted its exact
public module sums. Runtime v0.23.0 remains fixed at
8f92f31557d05920bcdef25376dcbd3b181c5b96.

See the diagnostic guide,
acceptance contract,
and scorecard.

Published from qualified merge f2e8b5a42d84250d2ee22a6bd303b340897d5fcf,
tree e10a3306b2f5f76f4b51d89d0df6a17f5f743ad8, identical to reviewed
head 56a1bf86b360af23a6236200e03dffcd26166542.

Both complete Windows/Linux workflows passed and were independently audited:
push qualification
and PR qualification.
Each Linux job executed all sixteen product stages, historical public formats
7–16, the normal no-replace format-17 scaffold, and all eleven PostgreSQL journeys
twice, including all eleven diagnostic states and all six scale cases twice.
Those final PostgreSQL stages had no failures, skips, panics, or timeouts
(640.751s / 545.593s). Framework CLI race tests actually executed
(1160.965s / 962.324s); twenty unchanged runtime-package results reused Go's
test cache. Windows installer, CLI tests, vet, and build passed in both jobs.

The independent native fresh -race -count=1 full-framework run also passed,
followed by whole-framework vet and diff checks: 26 packages, 648 top-level
tests, CLI 1505.539s. Two Windows-specific file-mode tests were skipped and are
disclosed in the scorecard history; this is not a zero-skip Windows claim.

Public v0.23.1 installation and no-replace application qualification passed
after publication. The downloaded installer produced the exact public CLI
module checksum h1:QT1h4MJZrWp4+nDyLCUtFlq10C9XqjiBbO8YhhEKsdo=.
A normal format-17 Category/Ticket/LegacyIssue app passed tests, fresh race tests,
vet, artifact/module checks, and all five process builds on public v0.23.0.
Offline/private-input diagnosis, actual route inventory, healthy ten-check CLI
and seven-check direct Go diagnosis, complete application/database nonmutation,
exact owned-schema cleanup, and process-environment restoration all passed.
Independent artifact/log/schema-absence review was clean.

Two earlier public-proof failures remain recorded, not counted as passes: an
overstrict assertion about optional older shared-cache provenance fields, and
a Windows scaffold-rename Access denied before application publication. A
byte/mode-identical complete ordinary-Go control reproduced the latter errno 5
without GoForge code; the specific host cause remains unidentified. No product
or ACL changes or automatic success-until-green retry were used. One
predeclared fresh full proof completed all unchanged workflow assertions.