feat(research): add project detail presentation model

[hubab1]

Summary

• add a closure-injected, explicitly @MainActor project-detail model for scoped keyword membership management
• thread every returned project revision through add, remove, and edit operations
• keep ranking and popularity refresh lanes independent for each exact keyword incarnation
• preserve valid pagination while requiring reconciliation when a mutation supersedes an unknown initial page
• preserve the follow-up fix that hides continuation availability while reconciliation is required

Correctness

• mutations and provider refreshes check cancellation before starting but publish successful committed returns without a post-commit cancellation lie
• replacement projects and stale completions are generation-checked
• refresh lanes are keyed by full keyword generation, so remove/recreate with the same UUID cannot inherit stale evidence or a stuck spinner
• continuation availability matches the guarded paging operation
• destructive conflicts are surfaced and never retried automatically

This progresses #3 but does not close it.

Validation

• focused detail-model tests passed
• full OpenASO suite passed: 573 tests (577 parameterized test invocations)
• project-file lint and whitespace checks passed