Repository navigation
Conversation
…nowledgment baselines
…probes and completion gates
…when Copy markup is absent
Maintainer review checkpoint — 2026-11-20HEAD: Requirement trace:
Validation provenance: prior candidate Residual gates: (a) complete latest-head CI, (b) authorized ONE REST live certification proving response text and status 200 against current DOM, (c) independent second review (Codex code-review quota observed previously), (d) PR #56's separate F2 rebind-on-failure correction and PR #52 no-replay integration. No changes to |
Frozen first-pass review: TXT-01…TXT-06 — live REST text-integrity failure (before remediation)Pinned: PR #57 Attached live-result JSON (provided externally): HTTP 200 in 14.25 s from a new conversation TXT-01 P0 role chrome: current-only fallback in TXT-02 P0 non-prefix slicing: Phase-2 emits TXT-03 P0 authority skip: backend TXT-04 P1 evidence scope: one live JSON report supports an HTTP status + returned content + URL; single-send identity, DOM text and downstream API provenance are in the separate user report, not the JSON. This is neither a replay finding nor a current CDP ownership proof. TXT-05 P1 fixture gap: the current Node-vm fake sets TXT-06 P1 invariants: retain legacy markup, anchored end_turn tri-state priority, Stop precondition, fail-closed stale-turn identity. #57 stays Draft, master unchanged. Review gate/patch scope: do not stream raw article wrapper text absent a clean semantic content node; read anchored backend text on positive end_turn; require an exact prefix before any final suffix (otherwise typed error, not silent 200); add behavioral fixtures for role chrome, nonprefix delta, legacy and backend-not-ready. Then head-specific CI and ONE separate authorized live REST confirmation. Independent Codex review remains outstanding. |
…anchored sentinel
…ion after live canary
… reset emitted baseline
Response-text remediation delta (after frozen first pass) — 2026-11-20The attached REST result has a particularly diagnostic property: Patch on this branch (starting at
Provenance and limits: Original live canary |
TXT-07 first-pass follow-up — 2026-11-20: two separately fetched anchored text versionsPinned head before changes: A second one-send live REST run has been reported against this exact commit: new conversation, no duplicate send, HTTP 500 Verified in source: Chosen narrow fix: remove the detector's intermediate backend text fetch and emission. Keep anchored Diagnostic addition: structured WARN on nonprefix comparison with response lengths, first mismatch offset, content hashes, and whitespace-only indicator; avoid logging raw assistant content or prompts. Tests: change former detector-anchored-fetch fixtures to assert deferral, plus a driver+detector regression feeding different v1/v2 results and requiring exactly one fetch, HTTP-safe matching content, and no resubmit. No merge and no renewed live send from this review. CI on a new SHA, then one explicitly authorized confirming REST run, and independent review are still gates. |
…ences without logging content
…ore one backend read
TXT-07 resolution candidate — single authoritative text emission (20 Nov 2026)PR #57 current head: Implementation (option 2 + privacy-preserving option 4):
Still open: Await full 9-job CI on this new SHA, then an authorized third one-send live REST confirmation with 200 + exact expected token + one send + no stale reply. The second live run's HTTP 500 is evidence that fail-closed behavior worked, not live text-integrity certification. Independent code review remains. Do not merge, mark Ready, or modify |
TXT-08 first-pass follow-up — transient
|
|
/gitwire run review |
|
ℹ️ GitWire: AI Review is disabled by repository policy. |
PR #57 — frozen maintainer-first review, pinned to
|
Independent second review — pinned head
|
…d backend fallback
…ompletion evidence
… anchored midloop ID
Follow-up to independent second review #7050086779 — R1/R2 remediation + R3 regression (2026-11-20)Source head of review:
Status: Implementation and new regression tests committed. GitHub Actions for this new exact head: |
Companion revision of PR #55 — ACT-aria current-UI compatibility
Branch ancestry: created from the exact PR #55 fork head
4dcebbe492c5caeea5e712534d51ccaf7df9fc86. The original forklekthailtd-bit/ChatGPT-Web2APIreturns 403 Resource not accessible by integration for direct edits, despitemaintainer_can_modify=true. This upstream-owned branch therefore preserves #55's changes and proposes its revision as a separate draft PR; #55 remains open, unchanged. Do not merge both independently.Authoritative input: user-provided
pr55-act-aria-patch-spec.md(live-verified 2026-11-20): completed assistantbutton[aria-label="Copy"]per turn; userbutton[aria-label="Edit message"]per turn; legacy roles/action-testids absent on current DOM. Earlier PR #55 review requested runtime JS tests, meaningful current/legacy fallbacks, and avoiding source grep-only confidence.Implementation in progress
end_turnremains authoritative when reachable and incomplete; a Copy DOM fallback requires stable text plus Stop absence; if current markup contains no usable assistant node, use exact-turn backend text.vmfixture executes emitted JavaScript on aria-only + legacy DOM, stale prior Copy, hidden menus, script text traps, and a textless-but-anchored final response.Critical review gates before ready/merge
finallyrebinding as a separate issue; do not conflate completion with route ownership or no-replay.Draft — not ready for merge or live certification until CI is green and review findings reconciled.