From 70268154c06cf78c5d9e1f4eb900213ffd436d1b Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 13 Oct 2026 20:33:23 +0200 Subject: [PATCH] Refresh intent assessment and prepare remaining platform admission Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d --- SCOPE.md | 14 ++-- .../2026-10-13-2031-resumed-readback.json | 70 +++++++++++++++++++ ...6-10-13-platform-publication-followup.json | 17 +++++ ...2026-10-13-reuse-publication-followup.json | 17 +++++ docs/platform-admission.md | 56 +++++++++++++++ ...2026-10-13-2033-intent-scope-assessment.md | 67 ++++++++++++++++++ ...LAYWRIGHT-WP-0004-consumer-verification.md | 13 ++++ 7 files changed, 249 insertions(+), 5 deletions(-) create mode 100644 docs/evidence/2026-10-13-2031-resumed-readback.json create mode 100644 docs/evidence/2026-10-13-platform-publication-followup.json create mode 100644 docs/evidence/2026-10-13-reuse-publication-followup.json create mode 100644 docs/platform-admission.md create mode 100644 history/2026-10-13-2033-intent-scope-assessment.md diff --git a/SCOPE.md b/SCOPE.md index 4fcd1e4..4d18900 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -2,8 +2,8 @@ As of 2026-10-13, the service, standalone Python client, browser trial and Railiance package are implemented and verified locally. **Managed Railiance -availability is not established.** Release 0.1.0 is published and verified by a cluster pull; platform admission -has not been confirmed. The founder selected `railiance-platform` as lifecycle +availability is not established.** Release 0.1.0 is published and verified by a +cluster pull; platform admission has not been confirmed. The founder selected `railiance-platform` as lifecycle owner; service implementation remains here. ## Implemented and evidenced @@ -44,7 +44,7 @@ artifacts expire; sanitized evidence under `docs/evidence/` is retained. | WP-0003 | Finished: tested image published at its exact digest and pulled on railiance01; ingress upload deadline fixed. | | WP-0004 | T02 provider trial/pilot done. T01 waits on platform admission/access; T03 waits on reuse-surface's maintained/published discovery update. | -The `playwright` namespace is absent. No browser workload was created. Server +Fresh resumed readback confirmed the `playwright` namespace is absent. No browser workload was created. Server admission, private consumer binding, live target reachability, managed independent trial, restart/cancellation and cross-version rollback remain unverified. [Release 0.1.0](releases/0.1.0.json) is now published; see the @@ -54,7 +54,11 @@ and Kubernetes client dry-run passed; they do not imply server admission. Existing capability `capability.infotech.headless-browser` was still D3/A2/C2/R2 with source-reuse/planned-provider wording at readback. The owner received actual local evidence and the usable client path; registry publication is pending. -Open workplan tasks retain blocker messages and exact resume steps. +The [fresh readback](docs/evidence/2026-10-13-2031-resumed-readback.json) also +confirmed local preflight availability at the checked time. The +[admission review packet](docs/platform-admission.md) identifies the exact package +and remaining platform decisions. Publication updates were sent in both existing +owner threads. Open workplan tasks retain blocker messages and exact resume steps. ## Deliberate limits @@ -65,5 +69,5 @@ sandbox is disabled; hostile pages and mutually untrusted tenants are unsupporte Target failures identify the category but not detailed DNS/TLS/HTTP causes. The OnCo pilot covers the home page, not all consumer routes or accessibility. -See the [timestamped intent assessment](history/2026-10-13-1918-intent-scope-assessment.md) +See the [timestamped intent assessment](history/2026-10-13-2033-intent-scope-assessment.md) for the prioritized gaps and their acceptance evidence. diff --git a/docs/evidence/2026-10-13-2031-resumed-readback.json b/docs/evidence/2026-10-13-2031-resumed-readback.json new file mode 100644 index 0000000..411efbd --- /dev/null +++ b/docs/evidence/2026-10-13-2031-resumed-readback.json @@ -0,0 +1,70 @@ +{ + "observed_at": "2026-10-13T18:30:58.167855+00:00", + "namespace_check": { + "command": "ssh railiance01 kubectl get namespace playwright --ignore-not-found -o name", + "exit_code": 0, + "namespace_present": false + }, + "unread_provider_messages": 0, + "discovery": { + "url": "https://reuse.coulomb.social/v1/federated", + "matches": [ + { + "id": "capability.infotech.headless-browser", + "name": "Headless Browser Automation", + "summary": "Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations. A rapp-playwright-provided service will be available shortly (announced 2026-10-13; planned, not yet verified available).", + "vector": "D3 / A2 / C2 / R2", + "domain": "infotech", + "status": "reviewed", + "owner": "reuse-surface", + "path": "registry/capabilities/capability.infotech.headless-browser.md", + "tags": [ + "headless", + "browser", + "automation", + "playwright", + "chromium", + "testing", + "screenshots", + "extraction", + "firefox", + "webkit", + "selenium", + "puppeteer" + ], + "consumption_modes": [ + "informational", + "source adaptation", + "JavaScript library", + "Python library" + ], + "source_repo": "reuse-surface", + "source_url": "https://forgejo.coulomb.social/coulomb/reuse-surface/raw/branch/main/registry/indexes/capabilities.yaml", + "source_index": "/data/cache/reuse-surface.yaml" + } + ], + "composed_at": "2026-10-13T18:17:45+00:00" + }, + "local_preflight": { + "available": true, + "error": null, + "checked_at": "2026-10-13T18:30:45.443Z", + "browser_version": "156.0.8078.4", + "api_version": "1", + "service_version": "0.1.0", + "playwright_version": "1.64.0", + "execution_location": "workstation-release-check", + "release": "sha256:8d6fd5a8172cf906bb503642ed620761945c5138b86f6396c36f65cbe6def441", + "allowed_origins": [], + "fixture": true, + "active": 0, + "queued": 0, + "limits": { + "concurrency": 1, + "max_queue": 4, + "max_timeout_ms": 120000, + "retention_ms": 3600000, + "max_runs": 64 + } + } +} diff --git a/docs/evidence/2026-10-13-platform-publication-followup.json b/docs/evidence/2026-10-13-platform-publication-followup.json new file mode 100644 index 0000000..ed86bd5 --- /dev/null +++ b/docs/evidence/2026-10-13-platform-publication-followup.json @@ -0,0 +1,17 @@ +{ + "id": "a282c300-eaef-4cd6-99b0-f4fb255203b3", + "from_agent": "rapp-playwright", + "to_agent": "railiance-platform", + "subject": "Forgejo publication resolved; managed admission and consumer binding remain", + "body": "Publication blocker from e77247e5 is resolved. Release 0.1.0: forgejo.coulomb.social/coulomb/rapp-playwright@sha256:8d6fd5a8172cf906bb503642ed620761945c5138b86f6396c36f65cbe6def441. Registry bytes match the tested image and railiance01 pull passed. Evidence: https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/docs/evidence/2026-10-13-publication.md . Founder-approved shared ingress read timeout now 600s, owner source RCLUSTER-WP-0016; close-down row 23 records it. WP-0003 finished. WP-0004-T01 still needs admission of the existing package, existing consumer user/group for the scoped port-forward RoleBinding, and confirmation of bundled fixture plus public OnCo target (or an approved preview). No credentials requested. Namespace playwright remains absent at 18:31Z readback. Source: https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/declarations/rapp.yaml and https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/manifests/workload.yaml . Founder lifecycle-owner selection remains railiance-platform; no browser workload has been created.", + "thread_id": "c82d75f3-3191-410d-a8c8-fd647bf7f3ef", + "read_at": null, + "archived_at": null, + "created_at": "2026-10-13T18:31:58.256181Z", + "kind": "message", + "expires_at": null, + "supersedes_id": null, + "reader": null, + "delivered_at": null, + "acknowledged_at": null +} diff --git a/docs/evidence/2026-10-13-reuse-publication-followup.json b/docs/evidence/2026-10-13-reuse-publication-followup.json new file mode 100644 index 0000000..1b3b6fa --- /dev/null +++ b/docs/evidence/2026-10-13-reuse-publication-followup.json @@ -0,0 +1,17 @@ +{ + "id": "fbab576e-7737-4b44-ab45-d7215b7ecca4", + "from_agent": "rapp-playwright", + "to_agent": "reuse-surface", + "subject": "Published browser release; discovery still needs verified local provider path", + "body": "WP-0004-T03 follow-up with changed delivery evidence: release 0.1.0 is now published at tested immutable digest sha256:8d6fd5a8172cf906bb503642ed620761945c5138b86f6396c36f65cbe6def441 and railiance01 pulled it. Contract: https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/docs/consumer-contract.md ; independent trial: https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/docs/evidence/2026-10-13-independent-local-consumer.md ; release: https://forgejo.coulomb.social/coulomb/rapp-playwright/src/commit/8831a05aeba5ce588f3b395ade676dde2a151c5d/releases/0.1.0.json . Local provider preflight passed again at 18:31Z. Managed platform admission remains pending; do not claim Railiance availability. Live /v1/federated still describes the provider only as planned at D3/A2/C2/R2. Please maintain the existing capability.infotech.headless-browser and publish the verified client/local evidence path with conditional managed instructions, then return the published readback. Source-only fallbacks and ephemeral workstation availability must remain explicit; no new capability requested.", + "thread_id": "30503ee1-77f9-4e9e-a63a-2f70ac097823", + "read_at": null, + "archived_at": null, + "created_at": "2026-10-13T18:32:00.688534Z", + "kind": "message", + "expires_at": null, + "supersedes_id": null, + "reader": null, + "delivered_at": null, + "acknowledged_at": null +} diff --git a/docs/platform-admission.md b/docs/platform-admission.md new file mode 100644 index 0000000..5086922 --- /dev/null +++ b/docs/platform-admission.md @@ -0,0 +1,56 @@ +# Managed admission review — release 0.1.0 + +Publication is complete. The remaining WP-0004-T01 decision is platform +admission and a scoped consumer binding, owned by railiance-platform. This +review packet does not claim approval or create a cluster workload. + +## Package to review + +- [Published immutable release](../releases/0.1.0.json), independently pulled on + railiance01: `sha256:8d6fd5a8172cf906bb503642ed620761945c5138b86f6396c36f65cbe6def441`. +- [Declaration](../declarations/rapp.yaml) and [workload](../manifests/workload.yaml): + namespace `playwright`, one Recreate replica, 100m CPU / 256Mi memory requests, + 1 CPU / 1Gi limits, 2Gi local-path RWO artifact volume, one-hour retention. +- Pod loopback listener with Kubernetes port-forward; no public ingress. + Deny-all incoming NetworkPolicy, DNS and public HTTPS outgoing rules, exact + application origin grant `https://onco.cc`. The fixture is internal to the + browser service. A workstation development server requires a separately + reviewed preview or dedicated reverse-tunnel origin. +- Non-root, read-only filesystem, dropped capabilities, no service-account token. + Chromium's OS sandbox is disabled for trusted-target jobs; hostile pages and + mutually untrusted tenants are outside this release's boundary. +- Role `playwright-consumer` permits pod lookup, deployment lookup and creation + of pod port-forwards. The package deliberately contains no RoleBinding. + +## Outstanding owner decisions + +1. Confirm admission of this package on railiance01 and any required changes to + its resource, storage, target or browser trust boundary. +2. Name the existing user/group eligible for the consumer RoleBinding and the + supported Kubernetes access route. Do not send credentials in the reply. +3. Confirm whether the initial managed pilot uses the bundled fixture and public + OnCo home page, or supply an approved reachable preview for another baseline. + +The founder selected railiance-platform as lifecycle owner. That selection and +the successful registry pull do not establish these decisions. Capacity must be +read again immediately before activation; earlier capacity observations expire. + +## Execution after admission + +Use the immutable reference in the release record with the commands in +[operations](operations.md). First review current node identity and capacity, +bootstrap the namespace with server dry-run/diff, then server-validate and diff +the full package. Apply the reviewed manifest and owner-approved consumer binding. + +Retain the admitted revision, Ready rollout, PVC binding, actual image digest, +and consumer identity's successful port-forward. Run the documented trial from +that consumer path, retrieve and hash screenshots, and exercise wrong-token, +failed UI assertion and unreachable-target cases. Verify bounded cancellation, +restart interruption and retrieval of completed artifacts after restart. + +For this first release, reapplying the same digest establishes recovery only. +An actual cross-version rollback requires a second reviewed compatible release; +retain that distinction in the receipt. WP-0004-T01 stays open until its managed +execution and recovery evidence is complete. Independent trial delegation was +previously authorized by the founder; no new trial has been started while +managed admission is pending. diff --git a/history/2026-10-13-2033-intent-scope-assessment.md b/history/2026-10-13-2033-intent-scope-assessment.md new file mode 100644 index 0000000..3e025bc --- /dev/null +++ b/history/2026-10-13-2033-intent-scope-assessment.md @@ -0,0 +1,67 @@ +# INTENT against SCOPE — 2026-10-13 20:33 Europe/Berlin + +The service, standalone consumer client and release package are implemented. +The tested release is now published and pullable on railiance01. **The full +intent remains unmet:** managed operation and evidence-backed discovery still +lack their owner actions. WP-0001 through WP-0003 are finished; WP-0004 has two +open tasks. This assessment supersedes the earlier gap ordering without erasing +its dated observations. + +## Current evidence + +| Requirement | Authoritative evidence | Result | +| --- | --- | --- | +| Fresh agent, no local browser, responsive screenshots and keyboard assertions | [Independent trial](../docs/evidence/2026-10-13-independent-local-consumer.md), retained final-image receipt and four hashed PNGs | Demonstrated locally; managed path missing | +| Reproducible release and immutable identity | [Release 0.1.0](../releases/0.1.0.json), fetched index SHA-256, [node pull](../docs/evidence/2026-10-13-published-image-pull.json) | Completed; previous registry gap resolved | +| Isolation, bounded lifecycle, failure diagnosis and evidence retrieval | [Implementation evidence](../docs/evidence/2026-10-13-implementation.md), integration and independent negative receipts | Demonstrated under local Docker; managed execution missing | +| Current availability and execution location | [Fresh readback](../docs/evidence/2026-10-13-2031-resumed-readback.json): local preflight available, workstation location, matching release; cluster namespace absent | Local provider available at check time; no managed endpoint | +| Railiance admission, consumer access, readiness, live recovery and rollback | [Package](../manifests/workload.yaml), [operations](../docs/operations.md), [admission review](../docs/platform-admission.md) | Prepared; admission and consumer binding unconfirmed; no managed receipts | +| Published discovery describes supported consumption accurately | Fresh `/v1/federated` readback in the same evidence file | Still D3/A2/C2/R2 with planned-provider wording; owner update missing | +| Content-explorer demand and acceptance | [Pinned OnCo pilot](../docs/content-explorer-pilot.md), provider handoff | Home-page smoke delivered; consumer owns broader acceptance | + +## Most important gaps + +1. **Managed Railiance operation is not established.** WP-0004-T01 needs + platform admission, an existing consumer identity/group binding and target + confirmation. The namespace is absent, so an installed runtime, private + consumer path, managed independent trial, cancellation, restart/retrieval + and rollback evidence cannot be claimed. The [admission review packet](../docs/platform-admission.md) + identifies the exact release, resources, trust boundary and execution gates. + Platform follow-up `a282c300-eaef-4cd6-99b0-f4fb255203b3` corrects the old + publication blocker and asks for the remaining decisions. Earlier requests + had no reply at this audit. A message is not approval or a running process. +2. **Discovery does not yet expose the verified provider path.** WP-0004-T03 + still needs reuse-surface's maintained capability and published response to + reflect the actual contract, release and local evidence. Follow-up + `fbab576e-7737-4b44-ab45-d7215b7ecca4` supplies immutable source references. + Managed availability must remain conditional until gap 1 closes. Inspect + the published response after the owner update; notification alone is insufficient. +3. **Consumer acceptance remains narrower than the full demand.** The pinned + OnCo home page and skip-link journey passed. Additional routes, search/graph + behavior and visual acceptance remain content-explorer's decisions. Provider + evidence does not close CONTENT-WP-0000-T04. The existing WP-0004 handoff + retains this boundary; no consumer task was marked complete here. +4. **Cross-version rollback has no executed evidence.** The current release + is the first. Same-image recovery can be exercised after deployment, but a + genuine version rollback needs a second reviewed compatible image. Keep + this distinction in WP-0004-T01 and future release verification. + +Detailed DNS/TLS/HTTP diagnoses remain a limitation: `target_unreachable` +correctly distinguishes target setup from failed UI assertions but can require +an operator reachability check. Native sessions, authenticated browser state, +multiple browsers, hostile targets and visual-baseline approval remain deliberate +non-goals, rather than unfinished commitments of this increment. + +## Disposition + +The previous goal turn made concrete progress by fixing publication and completing +WP-0003. This resumed turn revalidated external state, prepared the admission +review and updated both existing owner threads. No new workload or access binding +was created. Historical local test results remain linked to the unchanged image; +this documentation-only pass did not repeat browser tests. + +[SCOPE.md](../SCOPE.md) now reflects publication and the fresh readback. The +requested timestamped assessment is saved, but implementation of all workplans +is not complete. WP-0004-T01 and T03 remain explicit external waits; no completion +claim is made for the overall goal. Remaining owner actions are authoritative +work records, not merely prose in this report. diff --git a/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md b/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md index 4d3b349..3eea606 100644 --- a/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md +++ b/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md @@ -109,3 +109,16 @@ published discovery response; preserve the local/managed distinction. [Implementation evidence](../docs/evidence/2026-10-13-implementation.md) and [scope](../SCOPE.md) preserve these live waits. This workplan is not finished. + +## Resumed audit after publication + +Fresh readback confirmed local provider preflight, absent managed namespace and +unchanged planned-provider discovery. See [readback](../docs/evidence/2026-10-13-2031-resumed-readback.json). +Platform follow-up `a282c300-eaef-4cd6-99b0-f4fb255203b3` resolves the earlier +registry blocker and requests the remaining admission, consumer binding and +initial target decisions. The [admission review](../docs/platform-admission.md) +prepares that decision without inferring approval. Reuse follow-up +`fbab576e-7737-4b44-ab45-d7215b7ecca4` supplies published release/source evidence. +T01 and T03 remain wait until their owner outcomes can be verified. Actual +cross-version rollback remains unproven with only one release; same-image +recovery must be labeled accurately.