No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
No description available
This feature delivers the deeper round participation experience once a user opens a review: understanding assigned versus contextual scope, navigating recipe-based structure, opening content in the right reviewer-safe context, comparing what changed, signing off, and for round managers, overseeing reviewer-by-reviewer progress including terminal rounds. It solves the core execution problem of helping participants understand exactly what is in scope now, what changed from baselines or prior rounds, what is complete, and where attention is still needed. The implementation spans API aliases for round detail, scope, content, and sign-off actions; Azure service projections for assignment summaries, scope summaries, recipe navigation nodes, compare references, sign-off history, context labels, and profile-preserving content views; and DTO and mapper updates that expose only participant-safe metadata. It also adds manager-only projections for reviewer progress rows, unassigned coverage, warnings, and terminal-round access, while preserving capability metadata and integrating with existing scope-status and workflow behavior from specs 049 and 051. Important constraints include rejecting context-only sign-off, resolving completion and invalidation against the current in-scope revision identity rather than historical buckets, preserving read-only participation rules, supporting latest-subversion review without content editing, and keeping manager-only breakdowns hidden from ordinary reviewers. Acceptance comes from broad unit and integration coverage across scope aliases, navigation, content access, comparisons, sign-off invalidation, manager oversight, and final regression journeys.
This feature establishes the dedicated review surface that reviewers and round managers use to enter review work without exposing authoring or management-only complexity. It solves the baseline discovery and contract problem by creating the participant-specific routes, DTOs, mappings, service contracts, and shared infrastructure needed for every later review participation flow. The implementation spans shared test fixtures, API request and response scaffolding, endpoint anchors, projection models, mapper and service contract extensions, repository interfaces, DI wiring, ProblemDetails behavior, OpenAPI coverage, and core access/progress helper utilities. It introduces the participant inbox route, enforces read-only response shaping, removes management-only fields from participant DTOs, supports participant-safe delegation aliases, and adds the canonical foundations for reminder-aware due-date context, audit constants, and repository lookups that later features rely on. The main constraints are the guardrails around participant safety: reviewer-facing payloads must avoid raw Work Package metadata where prohibited, preserve reviewer read-only behavior, and keep delegation and access semantics aligned with spec 049. Acceptance is signaled by endpoint capability coverage, empty-state and dedicated-surface integration tests, contract validation, build and test completion, and quickstart/NFR verification including latency and freshness checks.
This feature delivers the feedback workflow for reviewers by preserving their ability to comment safely in review context, see historical discussion across cycles, and retain useful comment links even when rounds are cancelled or draft targets change. It solves the continuity problem that would otherwise fragment review feedback across revisions, rounds, and rebinding events. The implementation extends the canonical comment aggregate with cancelled-draft provenance metadata, adds repository and service behavior for exact workspace/object/language draft rebinding, and updates collaboration and round services to return participant-safe comment context metadata, historical round visibility, sign-off and comment continuity, and orphan-anchor fallback cues. It also emits audit and BI events for rebinding while preserving existing spec 052 lifecycle rules around permissions, classification, attachments, delete behavior, and round-filtered querying. Critical constraints are the exact qualification rule for rebinding, the distinction between single-target rebind and ambiguous-target retention, and the need to preserve reviewer-safe visibility into current and historical comments without granting content mutation capabilities. Acceptance is shown through unit and integration coverage for lifecycle restrictions, historical visibility, rebinding behavior, audit emission, cross-cycle continuity, and missing-anchor fallback behavior.
This feature delivers the participant inbox experience for discovering assigned review work, understanding urgency, and tracking completion at both personal and aggregate levels. It solves the day-to-day reviewer and round-manager need to find active rounds quickly, understand delegation and due dates, and see progress that stays correct when scope or current revisions change. The implementation builds inbox projection models, reviewer-safe DTOs, service logic for active-round filtering and row shaping, reminder-aware due-date context, delegated-assignment summaries, and progress calculations resolved against the current in-scope revision identity. It also adds visibility controls so ordinary reviewers see only aggregate progress while round managers can later consume the same underlying calculations, and it wires reminder-related tests into notification and scheduling journeys to keep inbox-visible deadlines aligned with platform scheduling behavior. Key edge cases include context-only rows, delegated origin and handoff metadata, empty states, and invalidation semantics where newly current revisions push previously completed items back to pending without losing invalidation visibility. Acceptance is demonstrated through unit and integration coverage for multi-round discovery, reminders, personal progress recalculation, and aggregate progress behavior.