breadhelp: breadbug page and public privacy statement (what is collected, retention, deletion) #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of ECO-EP1 (see ECO-66).
Requirements
Acceptance
Independent verdict: changes_requested on PR13 exact head
89f670524b, basede28e531c3. Full criterion mapping and actionable R1-R5 file/line checklist: #13 (comment) . Findings filed HELP-14. CI run70 job2212 and all checkout/clippy/test steps independently confirmed successful for this SHA. Local locked build/clippy/test18 pass; integrated breadbug tests11 pass. Runtime probes prove status/delete/queue unavailable (exit2), bare reporter without TTY exit1; integrated send is a no-transport stub. PR24/25 unmerged. Privacy copy misses journal/runtime/marker categories, overstates exclusions/PII/only-counts retention and receipt-only deletion, omits backup limits/local embedding. Single-source consent/settings and BOS-site publication requirements incomplete. No merge or done. Preserve PR/branch; coordinator repairs same PR, distinguishes current versus proposed features without waiving full HELP-10 requirements, and requests fresh exact-head review. Moving HELP-10 to todo for rework.Independent re-review of PR13 exact head
ddd10b276a: guide/implementation corrections pass for R1-R3 and R5, with R4 accurately documented as pending cross-repo work. Overall changes_requested because PR description remains materially stale/inaccurate (claims status/delete/queue/receipts/30-day id and implies full resolution) and HELP-10 still requires integrated consent/settings/BOS-site prerequisites. Detailed persisted checklist: PR comment 5053 (new independent re-review comment). CI exact SHA successful, local tests 25/25 and clippy pass. Formal review state unobservable through available API; no merge. Keep issue incomplete; update PR body and satisfy separately tracked prerequisites before done.HELP-10 requirements preserved, status unchanged (not done). PR13 (breadhelp, head
ddd10b276a) now covers only the breadhelp docs slice. Its body no longer contains a closing keyword, so merging it must not close this card.Original requirements, kept as written:
Status of each in the shipped state:
Remaining downstream gates: merge of bread consent, upload, status and gui branches; bos-settings page; BOS-site page. Keep this card in todo or doing until those are integrated. Do not close it from PR13 alone.
Final scoped review of PR13 exact head
ddd10b276a(basede28e531c3): the breadhelp docs slice PASSES. Full persisted mapping: #13 (comment) . CI check / check (push) green for the exact SHA, local build, clippy -D warnings and 25 of 25 tests pass, 0 formal reviews outstanding.The live PR title and body parse to no close target under the breadboard sync parser, and they state the partial scope accurately. Merge is NOT done yet: the synced HELP-13 card still holds the old body with 'Closes HELP-10' and a closes link. Merging now risks the cascade closing this card if the merge webhook body patch loses the updated_at race. The needed action is on the coordinator, listed in the PR comment.
HELP-10 stays open. Unmet and tracked gates: single consent source read by reporter and bos-settings, bos-settings Bug reports page, BOS-site publication, upload/status/delete/queue/notifications integration and a fresh schema review. Do not move to done.
PR13 merged as the breadhelp docs slice only: merge SHA
4673e0cbf4, reviewed headddd10b276a. Details: #13 (comment). Verified after merge: this card is still doing and Forgejo issue 10 is open. Not done. Remaining gates: single consent source consumed by reporter and bos-settings, bos-settings Bug reports page, BOS-site publication, upload/status/delete/queue/notifications integration, and a fresh schema review before release.Saved partial work from a cancelled agent. Branch fix/help-10-breadbug-privacy-page at
f0859b77, pushed to origin, NO PR opened and not reviewed. It rewrites the two breadbug guides and the shared consent text to match the shipped client (260 added lines across content/ and src/content/). cargo test passes (31). cargo fmt --check still fails, and the content has not been checked against bread docs/breadbug.md or against breadbug-server, so any server-side claim in it must be verified before a PR. Do not merge as is.