Skip to content

Add Codiff Web review-history foundations#4

Open
xortive wants to merge 8 commits into
codiff-existing-uifrom
codiff-web-review-history-foundations
Open

Add Codiff Web review-history foundations#4
xortive wants to merge 8 commits into
codiff-existing-uifrom
codiff-web-review-history-foundations

Conversation

@xortive

@xortive xortive commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Summary

  • define provider-neutral review-history contracts and shared walkthrough authoring
  • add forge-neutral commit matching and evolution projection
  • add GitLab transport, comparison, strategy, and evolution support with focused fixtures
  • add host-neutral walkthrough generation orchestration and Codiff Web migration documentation

Stacked on #3.

Validation

  • 59 focused Core and GitLab provider tests pass
  • vpr build passes at this revision

banana banana banana

xortive added 8 commits July 21, 2026 17:54
Introduce forge-neutral revision, range, comparison, evolution, version, and review-plan types plus the constructors and plan-resolution helpers that operate on them. Keeping this domain model independent gives Codiff Web and provider adapters a stable contract before any shared review UI is introduced.
Centralize draft parsing, prompt construction, hunk indexing, normalization, comment attachment, and unit composition in Core. This gives Codiff Web and Electron one deterministic authoring pipeline while leaving model execution, retries, caching, and storage in their respective hosts.
Implement patch-signature generation and confidence-based pairing for commits across rewritten review stacks. The matcher lives in Core so GitLab and GitHub can share retained, revised, removed, ambiguous, and absorbed-into-base classification without duplicating provider logic.
Introduce the GitLab transport abstraction and read-side provider implementation for versions, commit diffs, comparisons, review strategy, and commit evolution. Build the provider on Core review-history contracts and the shared matcher so Codiff Web can supply authenticated HTTP transport without carrying provider logic in its host.
Add focused fixtures for pure rebases, edited rebases, conflict resolutions, strategy classification, and commit pairing. Keeping the high-volume scenario coverage separate makes the provider implementation reviewable while preserving regression coverage for the analysis behavior Codiff Web will depend on.
Describe the shared Core and GitLab APIs, walkthrough-authoring ownership, generation inputs, and the Codiff Web migration checklist. Keep local Electron authentication and IPC guidance out of this document so the foundation MR remains scoped to reusable Web-facing packages.
Resolve review plans into whole-diff or per-unit generation, invoke a host-supplied model runner, normalize each authored result, and compose unit walkthroughs in Core. This lets Codiff Web share one orchestration contract while retaining ownership of model selection, queues, retries, and persistence.
Move commit-evolution projection and shared unit helpers into Core so provider adapters produce the same review-history model. Update the GitLab adapter to consume that shared projection instead of owning provider-specific copies, preparing the API used by Codiff Web and later GitHub integration.
@xortive

xortive commented Jul 21, 2026

Copy link
Copy Markdown
Owner Author

This stack of pull requests is managed by jj-ryu.

@xortive xortive changed the title Centralize provider-neutral evolution projection Add Codiff Web review-history foundations Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant