Skip to content

feat(browser): track ordered browser parity backlog #35

Closed

Description

@trmosala

Current checkpoint: 7f18709

Implementation and macOS validation are pushed to sqlite-lock-probe at 7f18709634b14be85ce36471626e39a8dadb60c1. macOS is the sole release target; Windows/Linux evidence is historical, not a remaining target requirement. Validation record. No release was deployed. The local unsigned package was installed and CookieMonster was restarted for validation. Live WPP token-accounting acceptance for #3 passed and is recorded on that issue.

Objective

Track the browser feature backlog and its separate release-assurance gates. Checked items reflect closed issue status and bounded implementation acceptance, not physical/platform/security equivalence.

Release assurance

Ordered implementation backlog

Remaining work and scope limits

Latest validation

#22 imports: 43 native cases passed. #24 custom device sizes, rotation and disable/restoration passed in the final full native run. Diagnostics, site tools, site data, tab organisation, presentation preferences, accounts, persistence and encrypted backup native fixtures passed. Physical macOS Touch ID approval returned VERIFIED; native cancellation returned CANCELLED. #32 now supports macOS secure passphrase entry; the actual helper compiles and the subprocess boundary is exercised with a synthetic child.

WPP bridge: 210 passed; live normal, continued, truncated, replacement and streaming usage checks passed. Desktop: 569 passed, 4 skipped; the final #23 browser scope passed 257/257. Browser plugin: 91 passed. Mounted app browser tests: 43 passed. App/desktop typechecks and the push-time 31-package typecheck passed. Native i18n: 14 passed, one pre-existing pa-PK detection failure remains. Scoped lint: zero errors, 55 warnings on the final 13-file scope. The branded unsigned macOS package built, installed and launched locally; packaged and installed app hashes matched, the installer-owned CLI ran, and the restarted bridge reported healthy. Earlier failed/timed-out native runs and their corrections are retained in the evidence record.

All tracked implementation items and the owner-approved internal-test assurance gate are complete. Preserve Chromium identity, isolation, explicit consent and vault locking in future work; broader distribution retains its separate written sign-off and external-review requirements.

Activity

  1. trmosala commented on Sep 15, 2026

    @trmosala
    OwnerAuthor

    Published checkpoint on browser-tabs: bc4040b saved-account Windows implementation, ce8f23c contact autofill, e0a9a4c native smoke stabilization. Full isolated native browser smoke now passes, focused offers/accounts/contacts have passing fixture evidence, browser unit tests 30/30, pre-push typechecks 31/31. The offer timeout was test-window Windows occlusion; cancelled-download cleanup required a bounded wait. Production safeguards unchanged. #5/#6 remain open for outstanding native/macOS/packaged evidence; #34 external review and release gates remain open. Next: #7 registration/password-change forms, then #8 generation. No installed app/server/bridge restarted.

  2. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Checkpoint: #7 implementation 996ac25 and #8 password generation c148c22 are pushed to browser-tabs; remote c148c22 verified. #8 final focused fixtures, full isolated native smoke, browser/i18n tests and typechecks passed; final source re-review found no actionable findings. Native/platform/localization/external assurance remains open, not satisfied by stubbed fixture ceremonies.

    Windows Update interrupted publishing after the local commit. Reconciled worktree/process/remote state and pushed the existing commit once. User-reported stale running indication after reboot is recorded under #20: #20 (comment). Do not automatically replay interrupted side-effect tools.

    #9 selected automatic-save compatibility is implemented locally with passing focused checks and is under review; #10 follows. No releases, installed-process restarts, or changes to unrelated user files.

  3. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    #9 published and remote-confirmed on browser-tabs at e366d28. Evidence: #9 (comment)

    Scope: persistent visible cleared-password native login and selected formless trusted Enter / same-turn association / requestSubmit; no general fetch/XHR detection. All four focused smoke suites, 31 browser unit tests and desktop typecheck PASS; parent full native smoke PASS after the final rejection-ack race fix. Complete scoped source review against c148c22 found no actionable findings (source-only, not external assurance). Scoped lint: 46 warnings / 0 errors. Normal push hook: 31/31 typecheck tasks successful.

    #9 stays OPEN for native usability/authentication, macOS/packaged evidence and #34 assurance. #8 remains confirmed at c148c22. Next ordered implementation is #10 contextual saved-account selection; stopped before starting it. Five owned files are committed and clean; excluded files preserved. No release or installed-process restart.

  4. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    #10 published on browser-tabs at ef7cb7f; remote matches HEAD. Exactly ten owned files committed, one commit/push with hooks enabled, owned worktree clean. Publication evidence: #10 (comment)

    Final source-only review found no actionable findings. App 15 unit / 41 browser, desktop 31 unit, both typechecks, focused --account-fill and full native smoke PASS; lint 74 warnings / 0 errors. Pre-push typecheck 31/31 PASS. Full app unit has 737 pass / 4 unchanged i18n parity failures; isolated parity 1 pass / 4 fail, i18n baseline diff empty. Translation repair is separate follow-up. #10 remains OPEN for packaged/native timing, usability, platform and external #34 evidence; synthetic native ceremonies are not assurance.

    Next checkout slice is parallel-priority #34 strict fail-closed storage writes across the whole cm-browser store, preventing non-atomic EXDEV/SNAP fallback and adding filesystem fault/interruption/reopen evidence: #34 (comment). Then pending #11 effective-permission explanation. No #34 or #11 code started in this publication step; sole editor and no installed-process restart. Stopped after publication.

  5. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Checkpoint: #34 strict-storage slice published at 80d7a6b, remote browser-tabs confirmed equal to HEAD. Exactly seven intended files, one commit and one normal push with hooks; 31/31 pre-push typecheck tasks passed. Evidence and remaining limits: #34 (comment)

    EXDEV/SNAP/WRITE/FSYNC/malformed-store checks, close/collision, real interruption/reopen/migration, --accounts, 31 browser unit tests, desktop typecheck and full native smoke passed. Scoped source review ses_f5905c6a3ffeYlhAvgmZBvPSmg found no production issues; parent fixed the low fixture checkpoint JSON visibility race and reports all eleven reopen phases passing afterward. #34 remains OPEN for initialized-key/first-key, power-loss/parent-directory durability, multiprocess, orphan-temp, native/packaged/macOS, threat-model and external-assurance gaps.

    Next is #11; no #11 code in this publication. Read-only audit ses_f57010568ffegBWydpk1KP70Nm: old snapshot survives global off/on/reconsent; press_key pending approval is not bound to the page. These are source gaps awaiting reproduction, not verified fixes. Audit: #11 (comment)

    Initial 900000ms worker timeout made no edits and ran no tests; bounded follow-ups succeeded. Only excluded local files remain dirty and untouched. Existing #20 no-replay incident instructions and unrelated i18n parity failures remain unchanged. No installed app/server/bridge restart, release or deployment. Stopping after publication.

  6. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Published #11 on browser-tabs at e55b0a1, based on 80d7a6b. Remote refs/heads/browser-tabs equals HEAD. Commit: e55b0a1. Full evidence: #11 (comment)

    Exactly 22 owned files: unified Agent access settings, main-owned eligibility and revocation, prepared source/access bindings, loading/native-consent lifecycle, final synchronous destination-policy recheck and complete 65,536-byte UTF-8 Response budget without URL truncation. Missing/incompatible bindings fail closed; main/plugin must ship together. Independent final complete source review ses_f5905c6a3ffeYlhAvgmZBvPSmg found NO actionable findings across 21 tracked changes plus the new mounted test. Source review is not external assurance.

    Applicable checks: driver/router 27 PASS; desktop browser 48 PASS; cm-browser 16 PASS; both latest typechecks PASS; focused/full native PASS serially after the final code edit. Prior app panel 15 PASS, browser 42 PASS and app typecheck PASS. Full app remains 737 PASS / 4 known unrelated i18n failures. Latest eight-file follow-up includes six linted TypeScript files: 77 warnings / 0 errors; earlier whole 20-file TS/TSX lint: 104 warnings / 0 errors. Different scopes, neither warning-free. Documentation formatting and scoped/staged diff checks PASS. Normal push hook passed 31/31 typecheck tasks (28 cached); completed feature tests were not unnecessarily rerun.

    #11 remains OPEN: deterministic cancellation seam with real policy/Electron/network observations is not naturally timed Chromium cancellation. The oversized URL is real Chromium history mutation (65,568 bytes, page/list failures 84 bytes each, short recovery succeeds). Windows consent is a real unparented native dialog with Electron-injected fixture-renderer Cancel, not physical input, packaged layout/timing, keyboard/screen-reader or macOS/Linux validation. Verified localization and #34 native/platform/security assurance remain open. Whole-inventory failure requires a known tab ID or manual recovery; the Response budget excludes internal storage, renderer state and outer IPC/plugin formatting. Dispatched actions cannot be recalled.

    Next is #12; audit-only ses_f564221dcffeYyRwMBH70xh4TP records that context.abort stops at cm-browser run and port timeout only abandons the reply. Main server.ts IPC needs per-sidecar request/session-owned cancellation and cleanup on child exit; router checks need membership/deadline enforcement and no overlapping in-flight native command. Scroll should reuse the #11 binding; only navigation wait tolerates its expected transition. No #12 code during publication.

    #20 reboot recovery stays settlement-only with no automatic replay of interrupted side-effect tools. #34 remaining gates and i18n failures are preserved. One resulting commit and one normal push with hooks enabled; an index.lock error was reconciled against status/log/process/remote, with no repeat commit or lock deletion. All 22 owned files are clean; excluded files remain untouched and uninspected. No installed app/server/bridge restart, release or deployment. Stopping after publication.

  7. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Checkpoint: #12 published once with normal hooks and remote-confirmed at 2fefd54. Bounded scroll/waits and cancellation, 24 owned files, both source review tracks clear after concrete regression fixes; pre-push typechecks 31/31. Platform/localization and #34 assurance gates remain open, so this is not issue closure or a release.

    Continuing the saved dependency-oriented sequence with #14 snapshot naming/state/shadow-DOM identity before #13 richer interactions, then #15 screenshots and #16 tab lifecycle. No repeated completed feature tests merely for continuation. Preserve the two excluded files, CM_GPT6_Astra_High and the installed app/bridge.

    #20 retains the worker-timeout/stale-running/auth-reclassification evidence and explicit continuation/no-auto-replay constraint: #20 (comment).

  8. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Backlog checkpoint: #12, then #14, then #13 are published in dependency order on browser-tabs.

    #14: 40f4d95, isolated node-identity snapshots with bounded naming/states and editable-content exclusion. Publication evidence: #14 (comment).

    #13: af5842e, hover, double/right-click, identity-bound native single-select and bounded same-tab pointer drag. Publication evidence: #13 (comment). One normal commit/push for the 18 reviewed files; remote SHA equals HEAD. Pre-push 31/31 typechecks passed (28 cached); only the two excluded unrelated files remain dirty and uninspected.

    Both cumulative #13 review axes cleared. Final verification: 125 browser tests, separate focused interactions and post-correction full native smoke passed; 60 cm-browser tests, 9 native-i18n tests and three package typechecks passed. Scoped lint retains warnings; known unrelated root lint/localization failures remain. Publication did not replay completed feature tests.

    Right-click uses the explicitly approved same-tab native-menu suppression until actual settlement. Single-select emits changed-only untrusted events. Drag is restricted to existing snapshot controls, with no universal HTML5/file/native drag guarantee. Native dispatch is not atomic; interrupted held input is quarantined without cleanup release or automatic replay. Selection-specific queued execution/tampering/synchronous-handler coverage and physical/native accessibility, packaged/macOS/Linux, verified translations and separate #34 assurance remain open. #20 recovery evidence remains recorded, not fixed.

    Next ordered implementation: #15 screenshots, then #16 tab lifecycle. Neither has been started in this slice. No installed app/server/bridge restart, model change, release or deployment.

  9. trmosala commented on Sep 16, 2026

    @trmosala
    OwnerAuthor

    Publication checkpoint: #13 was already published at af5842e; no duplicate commit. #15 is now published and remote-confirmed at 564ccd1 (18 task files, normal hooks, 31/31 typechecks). Evidence and remaining gates: #15 (comment) . Independent reviews clear; final 147 browser tests, 63 cm-browser tests, focused screenshot 22 rejection cases and default native smoke passed. Detached-background timeout, postdecode allocation, platform/accessibility/packaged/localization and external assurance remain explicit limits. Excluded files and CM_GPT6_Astra_High preserved; no installed-process restart or release.

    Next ordered slice #16 was audited and implementation started. Its worker hit o1_code_extension_timeout after 900000ms; recovering saved work/status without automatic replay before further edits. #16 is not verified or published yet.

  10. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    #16 implementation is published at 147ab6d, with the revocation-limit summary correction at c8ce338. Remote branch confirmed at c8ce338; normal hooks passed 31/31 typechecks. Full evidence: #16 (comment) . Both excluded files and CM_GPT6_Astra_High are preserved; no installed-process restart, release or deployment. #16 remains open for recorded platform/accessibility/localization/assurance gates.

    Continuing the ordered backlog with #17. The read-only audit identified that top-only snapshots did not prevent keyboard input reaching a focused iframe or wheel events reaching embedded frames. A bounded top-only input-boundary prerequisite is now saved and under review, with eight native unsafe cases witnessed RED before guards, then focused --frames/typecheck and 133 affected tests passing. This is not yet published and does not claim iframe snapshots, frame writes, chooser or password support. Those remain subsequent #17 work; #18 and later items have not been started.

  11. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    Backlog item 13 (#17) bounded implementation published and remote-confirmed at 0e89d57, exactly 24 task files. Evidence: #17 (comment) . Direct HTTP(S) frame reads/single-select and consent-aware native iframe file selection now work with exact top/receiver-origin and document/session authority. Child passwords remain explicitly blocked. Cumulative correctness/standards reviews clear; serial focused frames and final default native suite passed; normal push hooks 31/31 passed. Excluded files and CM_GPT6_Astra_High preserved; no installed-process/model/config changes.

    #17 remains open for documented platform/accessibility/localization and external assurance gates. Continuing item 14 (#18): source audit shows fresh exact-origin selection already supports top-level/popup login origins, so the next slice adds integrated actual redirect/popup and consent-invalidation evidence, without affiliation inference or cross-origin credential sharing.

  12. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    #18 published; #19 manual validation gates recorded

    Published b69d5e0 on browser-tabs; local and remote SHAs confirmed equal. Exactly three test/documentation files, no production routing changes. Existing exact-origin account selection is now covered through real loopback redirects, private popup/opener/callback/close, cancellation/retry, wrong-origin IDs and stale-consent origin/tab changes. Review corrections prevent fixture setup failures masquerading as safe rejection and directly inspect callback fields before close.

    Final uninstrumented serial desktop typecheck, --account-fill and browser unit suite passed (154 tests / 2252 expectations). Scoped lint: 49 warnings / 0 errors; formatting and staged whitespace passed. Normal push hook: 31/31 typechecks, 29 cached. Standards and corrected correctness reviews clear. Earlier unexplained account-menu timeout remains documented; later passes do not establish its cause. No production RED/GREEN or real-provider assurance claim.

    #18 evidence: #18 (comment)
    #19 reproducible Windows/macOS matrix: #19 (comment)

    #19 remains blocked for actual validation pending a designated user-controlled test account/tenant and disposable meeting, a candidate supported packaged build, and Windows/macOS interactive validation environments. All real-account/physical-picker/platform matrix entries are Not run. No speculative regression or credential sharing was added. #18, #19 and external #34 assurance remain open.

    Only the two excluded files remain dirty, untouched and uninspected. CM_GPT6_Astra_High, configuration, dependencies and installed processes preserved; no deployment or release. Editors and reviewers have ended. This checkpoint stops at the #19 external validation gate; #20 has not been implemented in this slice.

  13. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    #20 browser recovery published; task recovery remains open

    Published 913eb4f on browser-tabs; local and remote SHAs confirmed equal. Exactly 12 reviewed files, 532 insertions / 60 deletions. URL/title-only native navigation history restoration preserves private-by-default tabs and a locked vault on relaunch, without Chromium form/page state or POST-body replay. Failed restoration retains recoverable history and provides existing Reload/address/close actions.

    Evidence and remaining scope: #20 (comment)

    Checks passed: desktop 155 tests / 2276 expectations; app scoped browser/i18n 24 / 506; desktop/app typechecks; separate serial default native, --recovery, --tab-lifecycle, --frames and --account-fill. Normal push hook: 31/31 typecheck tasks, 28 cached. Formatting/whitespace passed; scoped lint 84 warnings / zero errors. Correctness and standards reviews clear for the browser slice. Earlier failures and fixture corrections remain documented, not erased by later passes.

    The reboot stale-running transcript and timeout/auth-reclassification incidents are NOT fixed. Legacy/V2 execution owners are process-local without an exclusive cross-process database execution boundary. Automatic settlement could falsely interrupt another live host; no transcript mutation or provider/tool/publication replay was added. Remaining #20 work needs an agreed ownership/fencing design and isolated idempotent settlement tests preserving partial output, child links, completed effects and pending admissions.

    #19 still needs designated test accounts/meeting, supported packaged builds and Windows/macOS interactive validation; #34 assurance remains open. URL/title metadata is plaintext and restored pages may execute authenticated site-side effects. No packaged release, deployment, installed app/bridge restart, model/configuration/dependency change or excluded-file edits. Only the two excluded files remain dirty. This checkpoint stops at the remaining #20 design gate; #21 has not been started.

  14. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    Download-only checkpoint: a3b77ee was committed, fast-forward merged into browser-tabs and pushed; local/remote SHAs match. Integrated desktop typecheck, 161 browser tests (2,360 assertions), and one serial disposable default native smoke passed. Normal push hooks passed 31/31 typecheck tasks (29 cached); scoped lint reported 62 warnings and zero errors. Seven task files only, with unrelated changes preserved. Full evidence and limits: #21 (comment) . #21 remains open: restart-resume is not implemented. #24 remains isolated and unmerged pending its unexplained native login-offer timeout. #20 task recovery remains design-gated; #19/#34 external validation gates remain. No release, deployment or installed-process restart.

  15. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    Preview checkpoint published and remote-verified: ff96a0e on browser-tabs, preserving download a3b77ee. Custom native dimensions/orientation/restoration plus stale capture A-B-A protection; delayed-arming fixture regression corrected without changing production login-offer guards. Historical offer timeout causation remains unproven. Combined checks: desktop/app typechecks; 167 desktop tests / 2440 expectations; 26 app tests / 597; serial --capture-selection, --offer-arming and default native PASS. Prettier PASS with no tracked change after local CRLF normalization; scoped lint 93 warnings/0 errors; push hooks 31/31 PASS (28 cached). Details: #24 (comment) . #24 platform/physical/translation acceptance and screenshot detached-background LIMIT remain. Next actionable ordered issue is #22 guided export import, then #23 before #25. #20 task recovery remains design-gated; #21 restart-resume remains unimplemented and product-gated; #19/#34 external validation inputs remain missing. Unrelated files and installed processes untouched; no deployment or release.

  16. trmosala commented on Sep 17, 2026

    @trmosala
    OwnerAuthor

    Current publication checkpoint: 98dd3c0, feat(browser): add guided export imports (#22). Local/remote verified, 14 reviewed files, normal push hook 31/31 PASS (28 cached). Both IPv4-cookie identity and append-only native i18n review findings resolved with RED/GREEN coverage and final source-only clearances. Saved evidence reused, not rerun: final typechecks, parser/bookmark9/43, native-i18n10/459, serial imports43/default/persistence11 PASS; initial full browser units169/2449. Native review before writes, stable identities/dedup/no-op and partial-cookie/flush results implemented without profile scraping or OS bypass. Physical/platform/translation/external assurance still open; cookies non-atomic/process-local. #24 published ff96a0e and #21 safety a3b77ee preserved. #24 historical timeout cause remains unproven and detached-background screenshot LIMIT remains. Now continuing #23: supported origin-specific foreground notification consent/revocation first, no placeholder location/screen controls. Active screen shutdown, clipboard boundaries and location configuration require explicit supported evidence, not inferred permissions. #20 task-recovery design, #21 resume product and #19/#34 external gates unchanged. Excluded files/installed processes untouched; no release or deployment.

  17. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Checkpoint: #23 supported notification controls are published in ced347782; local and remote browser-tabs match.

    Verified: desktop/app typechecks; native i18n 10/459; desktop browser 171/2,492; one serial default native smoke; scoped formatting/whitespace; oxlint 102 warnings/0 errors; final Standards and Spec source reviews CLEAR; push hook 31/31.

    #23 remains open for real OS delivery/consent, packaged and macOS/Linux evidence, native accessibility/localization review, screen-capture shutdown and external assurance. Screen sharing, clipboard permission controls and geolocation remain deliberately unsupported with no placeholder controls.

    Next actionable implementation item: #25, using the already-recorded native-only, explicitly consented, bounded console-severity design. Network-health counters and broader CDP access remain out of scope.

  18. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Checkpoint: browser-tabs is published and remote-verified at 52b4bd463f4fdeab662a84a9f7d8b78b011c0eda for the bounded console-only portion of #25.

    The new tool returns severity counts only with named Ask approval plus native per-use consent; it adds no console text, source URL, network capture, CDP access, or vault interaction. Task/tab/source/owner binding and cleanup have unit, router, and real Chromium fixture coverage.

    #25 stays open for its network-diagnostics acceptance and platform/external assurance. The next ordered implementation candidate is #26; #20/#21, #19, and #34 retain their existing design/product/external gates. No release, deployment, installed-app restart, or excluded-file change occurred.

  19. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    #26 is complete and pushed at 2d10f66b4 after the Electron 44.3.0 runtime upgrade 945c2f120. WebMCP discovery/execution is top-document-only, bounded, origin/source/task-bound, labelled untrusted, and requires named approval plus fresh native default-cancel consent. Real Chromium 152 and full isolated browser smoke passed; package tests/typechecks/build and the 31-package push hook passed. Experimental/platform/external-assurance limits are documented and remain separate. Proceeding to ordered item #27.

  20. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Backlog progress: #27 is complete in e959b0c and has been closed.

    CookieMonster now uses Chromium's own per-origin quota inspection for site controls, reports matching-cookie counts without values, discloses all-time and parent-domain cookie scope, and verifies exact-origin reload plus sibling/unrelated/app/WPP preservation in an isolated native fixture. Full native browser smoke and 31/31 pre-push typechecks passed.

  21. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Issue #28 bookmark folders and ordering is complete and published at 62e3f4ca9. Nested HTML structure/order/pin state, flat-record migration, limits, malformed input, normalized duplicate preservation, and native round-trip behavior are verified. Evidence is recorded on #28. Next ordered actionable item: #29 tab organisation.

  22. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Issue #29 tab organisation is complete and published at 34a9c33d1, with the current-runtime recovery prerequisite test correction at 4a1fc8347. Pin/order recovery, fresh private duplication, pinned-tab bulk-close protection, beforeunload Stay/Leave behavior, and keyboard tab-strip navigation are verified. Evidence is recorded on #29. Next ordered actionable item: #30 browser presentation preferences.

  23. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Issue #30 is complete and closed at 82eabea31.

    CookieMonster now persists exact-origin zoom (including ports) across navigation, new tabs, and URL/title recovery, while unconfigured origins explicitly return to 100%. Named device-size presets persist, but device emulation remains per-tab and is deliberately off on fresh/reopened/recovered tabs. Preview exit restores the native viewport.

    Evidence: focused real-Chromium presentation fixture PASS; full isolated native smoke PASS; desktop browser 187/187; mounted app browser tests 2/2; app/desktop typechecks; scoped lint 0 errors; push hook 31/31.

    Next ordered actionable item: #31.

  24. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Issue #31 is complete and closed at 25f3e0cf9.

    DuckDuckGo remains the default, with explicit Google and Bing selection. A closed validated HTTPS template registry encodes queries; direct URLs and local development addresses remain engine-independent. Missing/legacy/invalid stored values migrate to DuckDuckGo, and suggestions remain local with no remote autocomplete.

    Evidence: 17 resolver/template/migration/privacy tests; 2 mounted settings/preview tests; app/desktop typechecks; scoped lint 0 errors; push hook 31/31.

    Next ordered actionable item: #32.

  25. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    #32 is published and closed at 65b6a839a: versioned scrypt + AES-256-GCM password backups, fresh OS authentication in both directions, non-persistent native passphrase entry with confirmation, authenticated parameters/ciphertext, reviewed merge counts/collision handling, encrypted-destination race checks, exclusive atomic publication, and explicit OS-key-loss/offline-guessing/platform limits. Complete desktop browser suite, focused failure tests, package typechecks, native translations, full Windows native smoke, and 31/31 push-hook typechecks passed. #33 remains proposal-only discovery; no payment, passkey, or sync controls will be added without an accepted proposal.

  26. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    #33 discovery is published and closed at 4536d8daf. Three separate proposals now cover payment autofill, passkey management, and cross-device sync with current Electron/native APIs, user value, security/compliance requirements, platform gates, explicit non-goals, and earliest acceptable next steps. The product remains honest: no card vault, CookieMonster passkey manager, sync path, or placeholder controls were added. Normal push hook passed 31/31 typechecks.

  27. trmosala commented on Sep 22, 2026

    @trmosala
    OwnerAuthor

    All ordered implementation items are complete, #3 and #34 are closed, and the final owner-approved internal macOS test-build assurance decision is recorded in 7f18709634.

    The final state preserves the documented boundaries: no Chromium-equivalence or malware-resistance claim, and broader distribution still requires written WPP Open owner sign-off plus external security review. Closing this tracker as completed for its internal macOS test scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions