Only a documented procedure + per-account ZIP exist; no scripted DB+object dump. For a self-host product this is day-one data-loss exposure.
Non-negotiable:Pulled forward — Critical importance contradicted the old Phase-9 slot. Restore must re-apply privacy state faithfully (NN#3); safety net for NN#8.
Area: Performance & scale · P0 / must-have. From the product backlog gap analysis (docs/BACKLOG.md).
**Status:** partial · **Importance:** Critical · **Effort:** M · **Phase:** 1–2
Only a documented procedure + per-account ZIP exist; no scripted DB+object dump. For a self-host product this is day-one data-loss exposure.
**Non-negotiable:** **Pulled forward** — Critical importance contradicted the old Phase-9 slot. Restore must re-apply privacy state faithfully (NN#3); safety net for NN#8.
---
_Area: Performance & scale · P0 / must-have. From the product backlog gap analysis (docs/BACKLOG.md)._
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Status: partial · Importance: Critical · Effort: M · Phase: 1–2
Only a documented procedure + per-account ZIP exist; no scripted DB+object dump. For a self-host product this is day-one data-loss exposure.
Non-negotiable: Pulled forward — Critical importance contradicted the old Phase-9 slot. Restore must re-apply privacy state faithfully (NN#3); safety net for NN#8.
Area: Performance & scale · P0 / must-have. From the product backlog gap analysis (docs/BACKLOG.md).