Skip to content

fix: wrap long boundaries in native agent owner UI - #65

Closed
intel352 wants to merge 1 commit into
fix/agent-owner-ui-policy-20261009from
fix/agent-owner-ui-mobile-20261010
Closed

intel352 wants to merge 1 commit into
fix/agent-owner-ui-policy-20261009from
fix/agent-owner-ui-mobile-20261010

Conversation

@intel352

@intel352 intel352 commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

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 -d and git diff --check pass. Multisite PR148 exact head 2d6bf39a4ccadb9349a7d9ec933e88518f32d9b3 consumed this exact Auth commit 05097c9d8967dc81a975f8f2b3c0764c25fe5c34. Terminal successful CMS CI run 38083999153 passed 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 at verification/multisite-reusable-agent-editing-independent-review-2d6bf39-2026-10-10.md and verification/agent-editing-2d6bf39-ci/browser/native-cms/. The final owner evidence JSON is 4255B, SHA256 bf82cc139cc3af72d39f0f401d71017f7133c40844ebdca9651f26f6408b6571.

@intel352

Copy link
Copy Markdown
Contributor Author

Closing as incorporated by merged #63/#68 (#68). Rechecked exact predecessor head 05097c9d8967dc81a975f8f2b3c0764c25fe5c34. Accepted integration commit dfb9821c583653cd206eacc8e21f41f33fb10c50 has the identical complete tree 71e516665195d7e2d59abfc8a81b17677749475d. No unique source work remains in this predecessor. The branch, commits and historical receipts are retained; this closure grants no credential or hosted activation authority.

@intel352 intel352 closed this Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant