Why: Complete the W9 host-audit surface against the approved stage-5 requirement: audit the existing 2.14.0-experimental ProjectAuditHost/Registry and close the gaps — trusted reads bound to project/actor/resource/run/source-offset/cutoff, server-side trimming honoring the RDM audit.read callback and per-object body rights, minimal at-the-time display names for verified participants (never an account-directory dump), owner full-audit kept out of the project flow, explicit unsupported coverage, and the exit-matrix tests (cross-project, malicious projectId, revoked/deleted objects, historical cutoff, export, long pagination, no field fabrication on legacy records).
Evidence: unit w9-host-audit-surface (cursor, transport 97f60c1d); SELF build ok; extension/app/store/server tests all ok. GATE is CI on this PR HEAD.
Refs: two-trees stage-5 plan W9; increment C (Dev child branch c-w8-w10); PR #231 (X1 surface).
Why: Complete the W9 host-audit surface against the approved stage-5 requirement: audit the existing 2.14.0-experimental ProjectAuditHost/Registry and close the gaps — trusted reads bound to project/actor/resource/run/source-offset/cutoff, server-side trimming honoring the RDM audit.read callback and per-object body rights, minimal at-the-time display names for verified participants (never an account-directory dump), owner full-audit kept out of the project flow, explicit unsupported coverage, and the exit-matrix tests (cross-project, malicious projectId, revoked/deleted objects, historical cutoff, export, long pagination, no field fabrication on legacy records).
Evidence: unit w9-host-audit-surface (cursor, transport 97f60c1d); SELF build ok; extension/app/store/server tests all ok. GATE is CI on this PR HEAD.
Impact: pkg/extension, internal/app, internal/store, internal/server — audit-surface completion and tests only.
Refs: two-trees stage-5 plan W9; increment C (Dev child branch c-w8-w10); PR #231 (X1 surface).
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.
Why: Complete the W9 host-audit surface against the approved stage-5 requirement: audit the existing 2.14.0-experimental ProjectAuditHost/Registry and close the gaps — trusted reads bound to project/actor/resource/run/source-offset/cutoff, server-side trimming honoring the RDM audit.read callback and per-object body rights, minimal at-the-time display names for verified participants (never an account-directory dump), owner full-audit kept out of the project flow, explicit unsupported coverage, and the exit-matrix tests (cross-project, malicious projectId, revoked/deleted objects, historical cutoff, export, long pagination, no field fabrication on legacy records).
Evidence: unit w9-host-audit-surface (cursor, transport
97f60c1d); SELF build ok; extension/app/store/server tests all ok. GATE is CI on this PR HEAD.Impact: pkg/extension, internal/app, internal/store, internal/server — audit-surface completion and tests only.
Refs: two-trees stage-5 plan W9; increment C (Dev child branch c-w8-w10); PR #231 (X1 surface).