docs: clarify breadbug privacy contract #43

Merged

Breadway merged 1 commit from fix/eco-66-design-privacy-contract into main

2026-10-14 18:12:37 +08:00

Breadway commented

2026-10-14 12:43:54 +08:00

Owner

Closes ECO-66

Follow-up to merged PR #23, addressing reviewer comment #4754. Updates only docs/breadbug.md with field-level schema allowlists and bounds, consent/live-stack clarification, sensitive-app exclusion status, and explicit endpoint/security design requirements versus implemented controls.

Validation: cargo run -p xtask -- check-docs; git diff --check.

Closes ECO-66 Follow-up to merged PR #23, addressing reviewer comment #4754. Updates only `docs/breadbug.md` with field-level schema allowlists and bounds, consent/live-stack clarification, sensitive-app exclusion status, and explicit endpoint/security design requirements versus implemented controls. Validation: `cargo run -p xtask -- check-docs`; `git diff --check`.

Breadway added 1 commit

2026-10-14 12:43:54 +08:00

docs: clarify breadbug privacy contract

check / check (push) Successful in 34m5s

Details

c006f2a340

Breadway commented

2026-10-14 12:46:17 +08:00

Author

Owner

Independent ECO-66 follow-up review

Reviewed exact head c006f2a34054815d2fa869abcfcf7c24e094c72a against base main at 46a3feb16e9a112a2e8c8ecf8c7dce254efc9249. The sole changed file is docs/breadbug.md. Code assessment: accepted for design deliverable, with requirements explicitly distinguished from current implementation guarantees. It resolves prior comment #4754: v1 schema bounds and frame-only future live_stack consent contract; app-sensitive default exclusion policy clearly marked not implemented; detailed limits/allowlists and their current enforcement gaps; user-facing consent explains upload disabled/unavailable, destination and proposed retention/deletion; threat model articulates Aegis/intake boundaries, hostile payload handling, identifier limitations/rate controls, and isolated symbol store access. This is design specification, not evidence those server controls or ECO-66 release pipeline exist.

Merge gate is BLOCKED: exact-head check / check (push) is pending (Waiting to run), so do not merge yet. Individual workflow jobs are not exposed through the available Forgejo tools; no claim they were observed. Local check-docs/diff-check are reported by PR body but are not verified here. After exact-head CI is green and required jobs observable, re-read head/base/reviews/mergeability before authorized normal merge.

## Independent ECO-66 follow-up review Reviewed exact head `c006f2a34054815d2fa869abcfcf7c24e094c72a` against base `main` at `46a3feb16e9a112a2e8c8ecf8c7dce254efc9249`. The sole changed file is `docs/breadbug.md`. Code assessment: **accepted for design deliverable**, with requirements explicitly distinguished from current implementation guarantees. It resolves prior comment #4754: v1 schema bounds and frame-only future `live_stack` consent contract; app-sensitive default exclusion policy clearly marked not implemented; detailed limits/allowlists and their current enforcement gaps; user-facing consent explains upload disabled/unavailable, destination and proposed retention/deletion; threat model articulates Aegis/intake boundaries, hostile payload handling, identifier limitations/rate controls, and isolated symbol store access. This is design specification, not evidence those server controls or ECO-66 release pipeline exist. Merge gate is BLOCKED: exact-head `check / check (push)` is pending (Waiting to run), so do not merge yet. Individual workflow jobs are not exposed through the available Forgejo tools; no claim they were observed. Local check-docs/diff-check are reported by PR body but are not verified here. After exact-head CI is green and required jobs observable, re-read head/base/reviews/mergeability before authorized normal merge.

Breadway merged commit e4ddf6c5d3 into main

2026-10-14 18:12:37 +08:00

Breadway referenced this pull request from a commit

2026-10-14 18:12:37 +08:00

Merge pull request #43: breadbug design doc privacy contract