Skip to content

Reconcile reviewed production fixes on current main - #147

Merged
hamzamerzic merged 14 commits into
mainfrom
reconcile/reviewed-prod-round2
Jul 22, 2026
Merged

Reconcile reviewed production fixes on current main#147
hamzamerzic merged 14 commits into
mainfrom
reconcile/reviewed-prod-round2

Conversation

@hamzamerzic

@hamzamerzic hamzamerzic commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Outcome

Integrates thirteen independently reviewed production fixes onto current protected main after #129 containment and #144 restart-safety revert. Each source PR remains one commit in this branch so scope and provenance stay auditable.

Included reviewed changes:

Deliberately excluded:

Integration evidence

  • current base: f7548ce859a90debdd725f15085791b7656c07ca
  • exact head: 33951d666893fd14e9f5449d6cf3d69a7dd504ff
  • git diff --check: clean
  • combined frontend library tests: 1,797 passed
  • combined hook tests: 47 passed
  • production Vite/PWA build: passed
  • prior 12-fix head d8d29ce653b6a82d960dcc113567b6a968fa725f: hosted backend and E2E passed

Hosted backend and E2E must also pass on the exact 13-fix head. Do not merge if the exact head changes without renewed review.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Source-head ledger for exact integration d8d29ce653b6a82d960dcc113567b6a968fa725f:

Each integration commit was produced from that PR’s complete three-dot patch, in the listed order, followed by a clean merge of current protected main f7548ce8 (#129). git diff --check, 1,790 library tests, 47 hook tests, and the production/PWA build pass locally.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Thorough integration review — round 1/2 (exact d8d29ce6)

I verified provenance and replay integrity rather than trusting the aggregate description:

I also checked the four overlapping integration surfaces (composer shortcuts/sizing, ChatView quiet state, attachment styling, and Shell focus/activity attention). Their source tests all survive together on the aggregate head. No integration defect found in round 1.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Thorough integration review — round 2/2 (independent boundaries pass)

Second pass focused on failure domains and cross-feature state rather than patch provenance:

  • durability: app-attention acknowledgements remain version-bounded; provider/background saves preserve the authoritative first failure; platform hook refresh remains lock-bound to one immutable upstream object
  • authority/privacy: the app-module broker still owns executable loading, telemetry redaction remains fail-closed across the changed reporting paths, and the reviewed-label flow cannot create or publish a PR as a side effect
  • UI state composition: explicit focus does not consume the durable app-update signal; empty-composer reconciliation does not change shortcut semantics; quiet empty-chat rendering does not remove attachment or activity ownership
  • base interaction: current main changed browser profiles and the Codex runner only; the merge touched no reviewed feature file and needed no manual resolution
  • repository hygiene: no generated bundles, private workspace paths, conflict markers, or direct chat-JSON write path entered the aggregate

No code change requested from round 2. This aggregate is review-clear at d8d29ce6; merge should still wait for the exact-head hosted backend and E2E jobs to finish successfully.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Independent UI integration review on exact head d8d29ce653b6a82d960dcc113567b6a968fa725f: no code blocker found; hosted backend/E2E remain the final gate.

The integrated patches for #118/#119/#131/#132/#140/#141 are patch-id identical to their reviewed PR tips. Relative to current base f7548ce8, the PR has no useScrollMode delta, no #139 automatic-continuation paths/markers, no held #143 scroll patch, and no private .agents/.codex/AGENTS.md/CLAUDE.md leakage. The only skill-named path is the intended product seed backend/scripts/seed-skills/reflection.md from #142.

Cross-feature seams checked: modified-Enter's durable queue→per-row steer path and the semantic composer sizing/reset path coexist cleanly; voice, restore, send clear, hidden pane, visibility, and pageshow sizing still route through the shared helper. Builder immersive visibility feeds the app-activity acknowledgement/dot filter consistently, and the empty-chat prompt removal is orthogonal.

Exact local evidence: 173 focused composer/attachment/activity/Builder tests + 2 voice tests passed; full frontend passed 1790/1790 library tests and 47/47 hook tests; production Vite/PWA build and git diff --check passed. Awaiting the current hosted run before a final merge-ready verdict.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

APPROVED on exact head d8d29ce653b6a82d960dcc113567b6a968fa725f.

I independently audited the reconciliation graph, exact source patches, final merge construction, and the combined backend/process state machines.

Transition / owner Integration result
Codex start, cancellation, SDK exit, process-group TERM/KILL, browser-session close (#129 in protected base) Preserved exactly. None of the 12 integration patches touches Dockerfile, chat.py, codex_sdk_runner.py, browser_profiles.py, or their #129 tests. The final #129 merge is Git's conflict-free computed tree, with no manual resolution.
Modified-Enter steer (#118) Adds only a UI trigger into the existing live-turn route; it creates no runner/process path. Stop-vs-steer, force-steer, split, and active-turn registry tests remain green.
App broker/error containment (#134) Redaction and module-broker enforcement only; no browser daemon/process ownership bypass.
Platform hook refresh (#135) Separate reconciler authority: bounded fixed Git plumbing, pinned reviewed OID, cross-process reconcile lock plus hook lock, atomic replacement/rollback. It does not mutate chat generations, active turns, PGIDs, or browser targets.
Contribution review/create/recovery (#138) Separate durable review-record authority with explicit reviewed base and bounded GitHub commands; no chat-runner state mutation.
App activity acknowledge (#140) Version-gated DB transition; a stale seen request cannot clear newer activity. No runner/process path.
Background defaults/save (#136) Settings affect future provider selection only; live Codex chats still enter the same #129 lifecycle. Failed companion saves are authoritative before req-id staleness and cannot be hidden by a later edit.
Reflection adaptation (#142) Static seeded instruction/template change only. The repaired source aligns answer evidence by report date and explicitly removes the deleted verbosity/focus/avoid controls.

Composition evidence:

Validation:

  • local containment + steer group: 97 passed
  • local affected backend integration group: 311 passed
  • exact-head hosted CI: backend, E2E, frontend unit, core-app unit/sync, packager, and privacy all green

No blockers found. I did not merge.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Final exact-head verdict for d8d29ce653b6a82d960dcc113567b6a968fa725f: approve / no blocker. The full hosted run 29948789601 is green across privacy, backend, frontend unit, packager, core-apps, sync, and E2E. Combined with the patch-identity, leakage, composer/Builder/activity seam review and exact local tests/build above, this integration head is cleared as it stands. #143 is intentionally not present and remains separately gated.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Integrated reviewed #143 exact source 230332e028fe9a3bbca9a0915626f1ece412fc94 as integration commit 33951d666893fd14e9f5449d6cf3d69a7dd504ff. The source patch restores canonical physical-tail attention nudges while separating live off-content anchors from persisted/restore state. Local exact head: 1,797 library + 47 hook tests passed, production Vite/PWA build passed, git diff --check clean. Fresh hosted backend/E2E and exact-head re-review are required.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

APPROVED — narrow #143 delta on exact head 33951d666893fd14e9f5449d6cf3d69a7dd504ff.

Delta from the fully approved d8d29ce653b6a82d960dcc113567b6a968fa725f is exactly the repaired #143 source head 230332e028fe9a3bbca9a0915626f1ece412fc94:

  • stable patch ID matches: a4e45700fd3fb63c97160eff5d526253266b7d74
  • the full binary diff SHA-256 matches byte-for-byte: 10007caff434877983e5eda58ac6a4b25fbdbf01243e3d7a876a8e000b0f0c70
  • both pre-delta file blobs equal Prevent chat restore into reserved blank space #143's source base, and both post-delta blobs equal the repaired source head
  • scope is exactly two frontend files: useScrollMode.js and useScrollMode.test.js

There is no backend, Docker, recovery, settings, runner, process, database, or durable state-machine delta. The approved #129 containment and all other d8d29ce backend transitions are byte-identical. Because the delta is only the exact two-file #143 patch, #139 remains reverted and #146 remains absent.

The repaired behavior retains live physical-tail attention nudges while normalizing off-content anchors at the single persistence/restore gate. Targeted exact-integrated-head test: 71/71 useScrollMode tests passed. git diff --check d8d29ce..33951d6 is clean.

Hosted status at review time: privacy, frontend unit, packager, core-app unit, and core-app sync are green; backend and E2E are still in progress on this exact head. Code delta approved; required hosted checks still gate merge.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Re-review of current exact head 33951d666893fd14e9f5449d6cf3d69a7dd504ff: approve / no code blocker; the current hosted backend and E2E jobs remain the final gate.

The new integration commit is patch-id identical (a4e45700…) to the full reviewed #143 source diff at exact 230332e028fe9a3bbca9a0915626f1ece412fc94; no conflict resolution or semantic rewrite occurred. The final state preserves the owner-authoritative scroll split:

  • explicit question/paused attention nudges use physicalBottomAnchorModeFromScroll, stay live ANCHOR_AT, and reach the true physical tail;
  • live off-content anchors may retain reserved-room geometry;
  • every stored ANCHOR_AT passes the content-intersection gate, while mount restore also validates old state, so off-content/blank locations normalize to the real-content tail;
  • live FOLLOW_BOTTOM/pin state remains observable during the mount but restores only as settled hold state.

The #143 delta touches only useScrollMode.js and its unit test. It composes cleanly with the already-reviewed composer sizing/pageshow listeners, modified-Enter queue→steer path, durable app activity, and Builder immersive focus: retained-chat hide/return still crosses freezeChatExit, while composer foreground sizing owns only textarea/footer geometry. The diff contains no #139 automatic-continuation paths/markers and no #146 skill-platform files or hunks; #146 is not an ancestor (its only overlapping filenames, ARCHITECTURE.md and models.py, contain unrelated existing integration changes).

Exact local evidence on 33951d66: 224 focused scroll/composer/activity/Builder tests + 2 voice tests passed; full frontend passed 1797/1797 library tests and 47/47 hook tests; production Vite/PWA build and git diff --check passed. Current hosted run 29949662882 has privacy/frontend/packager/core-apps/sync green; backend and E2E are still running.

@hamzamerzic
hamzamerzic merged commit 226106c into main Jul 22, 2026
7 checks passed
@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Final exact-head CI update: 33951d666893fd14e9f5449d6cf3d69a7dd504ff is unchanged and all hosted checks are now green, including backend and E2E. The narrow #143 delta approval above is therefore fully merge-ready; no caveat remains. I did not merge.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Final integrated verdict: exact head 33951d666893fd14e9f5449d6cf3d69a7dd504ff passed hosted run 29949662882 across all seven jobs, including backend and the full E2E suite. Source #143 exact 230332e0 independently passed the same complete gate in run 29949521522. No remaining review finding. #147 merged as main 226106c46e83b776cc89c6d84daec820eee932a7; the new main push run 29950348376 is now the sole post-merge verification gate.

@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Post-merge landing verification is complete: main 226106c46e83b776cc89c6d84daec820eee932a7 passed run 29950348376 across all seven jobs, including backend and E2E. Source #143, integrated #147, and merged main have each independently passed the complete hosted gate.

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