PastureStack Web Console 1.6.164

PastureStack Web Console 1.6.164

Narrow Receiver validation-label release. Required and numeric errors reuse
existing labels for Receiver and its three supported driver configurations.
Model-specific translation precedence and unknown-field fallback are retained.
The scale-service and scale-host minimum-greater-than-maximum conditions are
unchanged; their message uses the existing localized numeric validation copy.
No API, schema, authorization, driver action, dependency graph or security
threshold changes are included. The published 1.6.163 display-locale fixes remain
unchanged.

• Signed numeric tag source: c3c0779d930d4d0367ec0517166ca21f6b3dc6d4.
• Validated source and merged runtime tree: 62ed2f12a29899fb55c5ccc6de3dc144f8310834.
• Normal PR147 merge: ae17bbc955522d5c78be588315115c89dbf839d8.
• Official validation 36831735186
  passed 763/763 actual Chrome tests, with zero failures, skips or todos. This
  includes eight new Receiver cases, four adjacent existing validation cases
  and the twelve retained Web163 locale cases. Existing source/dependency/
  security gates and both required PR CodeQL checks passed unchanged; this is
  not an all-findings-zero claim.
• Earlier focused native Chrome153 source validation passed 12/12 cases and
  61/61 assertions. The initial fixture-precedence failure remains preserved
  separately; runtime precedence was not weakened to satisfy the fixture.
• Two production archives were byte-identical. The existing reviewed candidate
  is published without rebuilding.
• Artifact: web-console-1.6.164.tar.gz, 2,976,044 bytes.
• SHA-256: 734898ac6ed2fe8774e5bb947988da9720a3a65aa0bb7ec09a89420adc0acc20.
• The accompanying .sha256 file uses the portable asset basename.

Component publication does not establish Server packaging, QA or production
deployment, native packaged-browser acceptance, full-language acceptance,
backend-write acceptance or complete resource/role matrix PASS. Historical
HOLD evidence remains HOLD, and the previous immutable 1.6.163 release is not
overwritten.

Web Console 1.6.163

Web Console 1.6.163

Numeric component release. Signed tag 1.6.163 pins validated source 5db737a5e04c4cc15672f97296d5bf521ab9a8da.

• Relative dates recompute on selected-locale changes and use the existing Moment language mapping per instance without changing the global locale during formatting.
• State badges translate seven recognized display labels through existing keys. Unknown text and health/connection overrides such as active + Disconnected retain their original semantics; icons, colors and API behavior are unchanged.

Official validation 36827428183 passed 755/755 actual tests, including the 12 locale source cases (seven rendering, three helper, two user-language). Failures, skips and todos are zero. The two production candidate archives are byte-identical.

The existing reviewed candidate is published without rebuilding:

web-console-1.6.163.tar.gz SHA-256: 54ef4e0726c6564abfb0b16727e991ef8a2258d9655cd1e603f43d6a557f8d27.

The accompanying .sha256 file uses the portable asset basename. PR CodeQL source checks completed successfully; this does not declare all findings zero.

This component publication does not declare a complete resource/role matrix PASS, full-language/responsive/mobile acceptance, backend-write acceptance, Server packaging or deployment readiness. Earlier HOLD evidence remains HOLD. No Server, authentication, runtime-host, VM or production deployment change is included.

1.6.162

Narrow desktop fixes: Host Add Container follows the current environment container POST capability, including schema readiness and generation changes. Secrets desktop headers use existing translation keys without changing sorting, search fields or widths. Source commit: 46501e3. CI 36810596087 passed 746/746 browser tests and two byte-identical production builds. Archive SHA256: 9c5b34d2cdf7ad354e1dab199795b12e5de119e47dc342547d5cdc84c7911581. PR #143 is merged. No API, authentication, OIDC, MFA or VM changes. Mobile and all-language acceptance are not claimed. Packaged Server browser acceptance remains pending; this release does not claim the broader resource/role matrix is complete.

Web Console 1.6.161

Web Console 1.6.161

Fix the native existing-Certificate editor that required an API-masked private key before a name/description update. Only a persisted, matching Certificate with unchanged certificate/chain and a masked key may omit the key. Its metadata PUT contains only name and description. Create and material replacement validation remains strict; encrypted keys remain rejected. No API, authorization, authentication, session, MFA or firewall contract changes.

The existing hint explains preservation versus replacement in all 13 locales. Rendered English, Traditional Chinese and Japanese forms retain the create required marker without incorrectly requiring the masked edit key.

• Immutable source: 2ad068d62b5afd3cd213cde8addc5ebbef738130
• Official CI: https://github.com/PastureStack/web-console/actions/runs/36738408143
• Full Chromium test suite: 738/738 PASS; focused native tests: 25/25 PASS.
• Locale gates: zero missing, orphan or invalid ICU keys.
• Two official builds produced byte-identical archives.
• Archive SHA-256: fa3ec0bf5173fa75a53dd621b87e1f587b20d9ecc6e5cb42a703ac4f5f7e97e7

Packaged Server and owner/member browser acceptance remain separate and pending. Historical failed browser receipts are not promoted to PASS. This component release does not complete the broader resource/role matrix.

1.6.160

Web Console 1.6.160

The shared error formatter and growl service now explain the known 405 / InvalidAction certificate-in-use response: remove the load-balancer service's certificate references before deletion. English, Traditional Chinese and Japanese are covered. Server-returned service names/IDs are not displayed; 403/404 and unrelated 405 errors retain the neutral message. API status, authorization, session, OIDC and MFA behavior are unchanged.

Source: 63964fa3a6da5cbd452cdc1061c1e18340055362. PR #138 is normally merged with an identical source tree. Official native Chrome CI run 36702030007 passed all 725 tests. Two production builds produced byte-identical release archives. Locale checks passed with zero missing/orphan/invalid keys. The focused local formatter/growl tests also passed 32/32.

Archive SHA256: 705946b96e693c55a8ab5de3bc96b14020a52a050bf3992c302b9fb3c1408a51. The standalone checksum is attached. This tag is immutable and does not overwrite prior versions. Native Server/browser acceptance of the certificate workflow is a separate gate; full resource/role matrix completion is not implied.

Web Console 1.6.159

Preserves existing Registry passwords on username-only edits: blank, null and missing password inputs are omitted; explicitly entered nonempty replacements retain literal whitespace. Adds English, Traditional Chinese and Japanese guidance. Existing exact-ID, parent Registry, project and capability guards remain intact.

Source: aab95cf (PR #135 and #136).
Official validation: https://github.com/PastureStack/web-console/actions/runs/36686121660 — PASS, 723/723 browser unit/integration tests, 0 failures; two deterministic production archives matched. Focused Registry tests: 7/7.
Archive SHA-256: f014083480e10430701e3a08588cf617242188938d9f935fbaac42a3b5feeb90. VERSION.txt=1.6.159; 13 locales; no source maps.

Build/test-only compatible security patches pin brace-expansion 1.1.21 / 2.1.7 / 5.0.12 and Engine.IO 6.6.10. The unchanged High/Critical audit gate and compatibility probes passed; remaining Moderate findings are not declared fixed.

This source/archive release does not establish Server image publication or full role/resource/browser acceptance. Those are separately verified on isolated QA 8080; no formal company-site deployment is included.

Web Console 1.6.158

Web Console 1.6.158

Service direct-ID and Secrets collection load failures now use the existing localized resource-load error handling. HTTP 403 and 404 show the same safe unavailable explanation; HTTP 5xx shows a server-failure explanation. HTTP 401 and network errors retain their existing session and network handling. Save and action failures with HTTP 405 now use the established localized unavailable explanation rather than raw API text.

English, Traditional Chinese, and Japanese translations were updated. Focused Chrome 153 QUnit tests passed 7/7, and the official validation workflow passed on commit 4c99e4803d594a6bc7c340aefc686d34e4ea0f87 after two reproducible production builds. The official archive SHA-256 is 286833d3313c5bc04469a8fafd41bab7de1c4b60527f91aae9eef8a4016b17f6.

This release is the Web Console artifact only. It has not yet been assembled into a Server image or accepted through the packaged QA browser workflow; no production deployment is implied.

Web Console 1.6.157

Web Console 1.6.157

Server v1.6.490 packaged Web Console 1.6.156. In isolated 8080 browser QA, a
readonly user opening /apps/stacks/add directly on a fresh page received
the intended permission denial, but the notice remained fixed under BODY.
The authenticated template contained an empty #growl-mount, and the notice
overlapped the right-side header actions at 1440px (notice y55–136; actions
y65–97). A client-side transition on the same page moved the notice into the
mount and cleared the actions.
Thus 1.6.156 did not pass packaged browser acceptance for this path.

The route's deferred render callback could miss the mount on a fresh load.
The authenticated template now renders a growl-mount component that moves
the existing jGrowl container when its element enters the DOM. On teardown it
returns the container to BODY only if that component still owns it. This
preserves the running plugin instance and keeps login/MFA notices on their
existing body host. The change does not alter route permission checks, API
authorization, notice copy, or request payloads.

npm test -- --filter='growl' passed 7/7 Chrome 153 QUnit tests, covering
notice placement, component insertion and teardown, delete notices, and layout.
The layout test covers light and dark themes, LTR and RTL, English, Traditional
Chinese, and Japanese, at 1440px, 375px, and 280px. These checks use the source
build.

The official Web Console 1.6.157 release
publishes web-console-1.6.157.tar.gz with
SHA-256 ba1724c8a2e3d204c6f1527c7880cd361f3e307863133a1d1ba45120fce53a3f.
Server v1.6.491
packages this version in the published image
ghcr.io/pasturestack/server:v1.6.491@sha256:c484d298e5bde93b51b44acd476a725bbaa471959d1079d19331c01bc55f8705.

Post-release isolated 8080 QA passed 14 scoped cases: 12 readonly Stack and
Service direct-create denials across Traditional Chinese, English, and Japanese
at 1440x900 and 375x812, plus two owner checks that the create forms open at
1440x900. Two additional fresh
direct-URL checks for the readonly role passed at 1440x900. The record reports
zero resource writes; the owner checks did not submit a resource. This QA does
not establish 280px packaged layout, both themes and directions, login/MFA
notice behavior, the broader six-role resource matrix, or formal company-site
deployment.

Web Console 1.6.156

Web Console 1.6.156

Server v1.6.489 packaged Web Console 1.6.155. Its isolated QA 8080 browser
run confirmed that the permission notice was visible and no longer covered
the 45px navigation bar, but screenshots revealed a remaining defect: at
375px the fixed notice covered the page title; at 1440px it covered the
right-side sort controls. The earlier viewport-only test had incorrectly
reported those cases as passing. This release addresses that shared layout
cause, not the Stack or Service authorization rules.

On authenticated pages the existing jGrowl container is moved into a mount
between the navigation and <main>. It stays in the normal document flow and
is right-aligned, so visible notices push page titles and header actions down
at desktop and mobile widths. The same container and plugin instance move
back to the body when leaving the authenticated route; login and MFA notices
retain their existing behavior. A deferred mount operation checks that the
destination still belongs to the document before moving the container.

Focused Chrome QUnit tests cover the shared notification service and layout
at 1440px, 375px, and 280px, including both themes and text directions.
Local Playwright screenshots with compiled CSS verify that the notice clears
the navigation, title, and header actions at those widths. These are source
and local-browser checks; official CI, the immutable Server image, and a new
QA 8080 packaged-browser receipt must be verified separately. No API,
Engine, permission, or request-payload contract changes in this release.

Web Console 1.6.155

Global notification layout now respects the shared 45px navigation height and stays inside narrow viewports in light/dark and LTR/RTL layouts. This is a frontend layout patch; permission semantics and APIs are unchanged. Official main CI run 36605681674 passed 713/713 Chrome tests and twice-built the identical production archive. Packaged Server and 8080 browser acceptance are separate gates.