Repository navigation
Keep edited profile feedback when a replacement request fails - #15
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://fix-capture-feedback-recovery-professional-toolkit.abihurairahansari.workers.dev (commit f9e2e9c)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retrying profile feedback used to remove the current review before a replacement arrived, losing unsaved rewrite edits when the request failed. The website now keeps that artifact during processing and after 429/502/504/network/invalid-response failures, distinguishes old feedback from a failed new attempt, and replaces it only after validation. Competing edits/imports/handoffs are guarded; source redaction still clears the old review and renews consent.
Two independently published milestones preserve the owner’s history:392e617 adds the complete UI recovery and actual-browser regression; f9e2e9c enforces it in CI using the built Worker, fresh local D1 and Chrome. No production/Preview resources or AI are bound in the CI fixture, outbound Worker calls are blocked, and synthetic records/runtime are cleaned up.
Validation:161 application tests,10 Python tests, TypeScript, production audit0findings, backend/client builds, package/checksum/runtime checks, desktop/mobile recovery and existing project/extension journeys passed. Final head f9e2e9c passed all six GitHub/Cloudflare checks, including the new Linux backend/browser CI step in run39195936868. Independent app/harness/runner reviews found no actionable findings; Codex completed the first UI milestone without findings. Twelve controlled review responses per full recovery run tested persistence and state recovery without inference.
Actual full Cloudflare Preview acceptance passed loaded-extension capture/account/redaction/private-save/title-sync plus desktop/mobile downloads. The configured October12 platform runtime and separate Preview D1 were verified; all four synthetic fixture-table counts were0 after cleanup. Final Cloudflare build0ce2a8ab-3f48-49bc-aa9f-3a0a3d0197e2 passed. The pinned local runtime’s September25 test-date cap is explicit and documented; generated Cloudflare configuration is unchanged.
Evidence: reports/2026-10-19/FEEDBACK_RECOVERY_RESEARCH.md and FEEDBACK_RECOVERY_VALIDATION.md. Extension package remains0.1.4; no dependency, permission or data migration. Production remains the separately approved0.1.3 and requires owner approval for a future release. Recovery is in-memory through a failed attempt, not automatic persistence across navigation.
Merged as a146f7c, preserving both GitHub-linked AbuHurairh authored commits. Default-branch Contributor run39196149893, including the new isolated backend/browser acceptance step, all three security analyses and Cloudflare build4379e9b1-8459-4ba7-8980-3eb8a7a97f95 passed. Active production remains f5b88a6f at100%; the upload-only build did not publish new code to live traffic. The five-hour automation was updated and read back ACTIVE with the same cadence, marking recovery complete and retaining the production approval boundary.