48 lines
2.8 KiB
Markdown
48 lines
2.8 KiB
Markdown
# WP-80 development entrypoint evidence
|
|
|
|
This packet supports T33/T37 and completed browser-discovery checkpoint T45.
|
|
The short runbook is [Working development entrypoints](../../../netkingdom-development.md).
|
|
|
|
## Completed discovery correction
|
|
|
|
Reuse-surface commit `ed3c900efbe96b931747dee336bf30e92744764f` updates only
|
|
`registry/capabilities/capability.infotech.headless-browser.md` and its existing
|
|
index summary. The record now points to the actual supervised managed trial.
|
|
No capability ID or maturity level changed (D3/A5/C2/R2); no new catalog, browser
|
|
client or deployment was introduced.
|
|
|
|
The owner validator passed all three capability entries with
|
|
`--fail-on-warnings`. The local browser query returned the updated card, and
|
|
`hosted-browser-discovery.json` records HTTP 200 and exactly one matching card
|
|
with the corrected summary. The owner publication receipt records exact primary
|
|
projection and normal remote publication. Its unrelated brief/work-record
|
|
changes were preserved. The two postimage files retain exact published sources.
|
|
|
|
## Partial flow evidence
|
|
|
|
- `playwright-current-preflight.json`: available service, exact versions,
|
|
release and limits. Actual human/agent runs remain in
|
|
[the delivery packet](../wp80-build-mode-r1/README.md).
|
|
- `git-baseline.json`: existing SSH read, 0.629 seconds, and previous ordinary
|
|
write/publication sample. This alone does not close T44.
|
|
- `forgejo-cli-result.json`: current owner transport refused retrieval with
|
|
OpenBao 403 before the Tea/API probe ran. Raw output was discarded. This is a
|
|
retained failure, not authenticated API acceptance.
|
|
- `forgejo-route-plan.json` and `forgejo-login-plan.json`: routing metadata
|
|
identifies Platform custody and the founder-required interactive KeyCape
|
|
login prerequisite. No credential values are included.
|
|
- `check_forgejo_cli.py`: isolated verification using installed Tea, not a new
|
|
Forgejo client. Isolation-only mode passed without an API request. The
|
|
credentialed path remains unverified because the owner transport refused.
|
|
- `measurements.json`: bounded samples, command counts and explicit unknowns.
|
|
No cold-onboarding or comparative performance claim is made.
|
|
- `attended-api-preparation.json`: exact existing-owner login/role and silent
|
|
invocation of the existing Tea probe. Installed Warden source pins and shell
|
|
syntax are checked; no new runner or credential-policy change is introduced.
|
|
This prepares the founder-run attempt and does not prove interactive login,
|
|
session revocation or authenticated API success.
|
|
|
|
T33/T37 remain in progress until the actual Forgejo paths are accepted.
|
|
T42 still waits on decision `ad88edeb-7c7c-486f-a695-1a7abae5b20c`; no source
|
|
changes here activate its native proposal. Human sign-in T43 and complete agent
|
|
Git/API T44 remain open. Repository privatization stays with ORGREF-WP-0002.
|