Repository navigation
Conversation
Contributor
Author
|
Closing as incorporated by merged #63/#68 (#68). Rechecked exact predecessor head |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The native agent owner page overflows a 375px viewport to 442px when its API boundary URL is long. Actual Chromium acceptance against the mounted host and disposable PostgreSQL showed the boundary paragraph has a 285px visible box but 397px scroll width. Grant creation/reload and revocation/reload passed; the strict mobile width check correctly failed.
Allow long boundary and retained grant text to wrap using
overflow-wrap:anywhere. Keep all text visible and preserve the native form, explicit permission/confirmation flow, current owner authorization, scopes and expiry. This is a one-line CSS change on the frozen owner-policy prerequisite; no credential, grant, schema, platform or deployment change.Validation:
gofmt -dandgit diff --checkpass. Multisite PR148 exact head2d6bf39a4ccadb9349a7d9ec933e88518f32d9b3consumed this exact Auth commit05097c9d8967dc81a975f8f2b3c0764c25fe5c34. Terminal successful CMS CI run38083999153passed all four mandatory Chromium scenarios without skips or failures. The owner scenario passed all six checks, including create/reload, revoke/reload, contrast, visible keyboard focus and session-loss denial. Actual mobile document width is 375px at a 375px viewport, and the full boundary and retained grant text remain visible. The enclosing PostgreSQL test also passed its post-browser audit binding, current runtime guard and two store reopenings. The consumer's general build and native PostgreSQL 17/18 lanes passed; CI's dependency checksums match the committed source. No local Go/Docker/build or hosted writes performed.This draft is stacked on Auth64 (
fix/agent-owner-ui-policy-20261009) and preserves Auth63/64 unchanged. Auth workflows target main, so normal retargeting and fresh upstream exact-head CI are required after prerequisites merge, before merge/release. Consumer source CI does not waive repository protections or authorize activation. Independent source review and final successful browser artifacts are retained in the parent task atverification/multisite-reusable-agent-editing-independent-review-2d6bf39-2026-10-10.mdandverification/agent-editing-2d6bf39-ci/browser/native-cms/. The final owner evidence JSON is 4255B, SHA256bf82cc139cc3af72d39f0f401d71017f7133c40844ebdca9651f26f6408b6571.