Skip to content

GitLineage M2 — Unified Repository Explorer, Discovery V2 & Git History - #1

Merged
yunmin311 merged 64 commits into
mainfrom
review/gitlineage-development
Oct 14, 2026
Merged

yunmin311 merged 64 commits into
mainfrom
review/gitlineage-development

Conversation

@yunmin311

@yunmin311 yunmin311 commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

Result

GitLineage now uses one Repository Explorer for coexisting Origins, Dependencies, References, structure and discovery observations, with an independent Git History log that returns to the preserved graph. Local expansion, collapse, focus, search and restored exploration state retain object identity. Inspector evidence, source comparison and exports remain available without promoting similarity to ancestry.

This closure fixes the following regressions:

  • Private Beta acceptance waited for removed .plate-row elements. It now expands a real group, selects a member by keyboard, opens its relationship evidence and explicitly opens the export disclosure. Login, authorization, framing protection, selection/camera continuity, download redaction and logout checks remain intact.

  • A shared node could obstruct the router's preferred exit. Routing now retries real boundary ports and checks endpoint interiors as well as unrelated obstacles. Canonical and composed renderers no longer silently omit failed routes or substitute unsafe curves: paired inspectable endpoint badges expose an obstructed connection without inventing a line or changing its identity, direction or evidence.

  • Responsive focus acceptance now waits for replacement of the old SVG node before asserting focus on its replacement. CSS width alone could satisfy the old wait before the resize redraw. The focus requirement is unchanged.

docs/project-state.md now describes implemented workspace/History behavior, current anonymous request accounting and bounded continuation. Earlier live/deployment results are explicitly historical.

Validation

Local typecheck, production build, Unit (613 pass, 3 existing live skips) and Discovery (136 pass) passed. Chromium fixture acceptance covers Canvas, Landing, Analysis, Preflight, stale A→B, UI Contract, Responsive, Mobile, Deep Search, unified workspace/History and anonymous exploration, normal Private Beta and trusted loopback TLS/Caddy staging. Spatial regressions sample actual SVG paths and check collision clearance, visible parent connectivity, unique shared objects, collapse/restore and actionable routing fallback. Key flows run at 390, 430, 1280 and 1920 px. Production-disabled guards and unchanged production bundle hashes are checked.

Both native ARM64 merge-review gates passed on final development HEAD cb79ba97776e652d764528249c506d321bc4cecc:

Workflow results refer to the same final HEAD; earlier successful SHAs are not used as acceptance evidence.

Boundaries

Canonical Graph Schema 2.0.0, Presentation View and Discovery Sidecar remain separate. Discovery keeps verification: pending, lineageClaim: none; similarity is not Fork/Derived proof. Anonymous exploration and authenticated Private Beta retain separate ownership and budgets. Production opt-in defaults and cache isolation are preserved.

Evidence uses offline repository fixtures and fixed Mock GitHub Transport. TLS staging uses a real temporary CA, isolated browser trust and loopback Caddy; it changes no system trust or production configuration. Fresh GitHub API, WebKit/Safari and physical-device acceptance are not claimed. CPU hard isolation, absolute wire-byte caps, exhaustive repository coverage and durable server exploration sessions remain outside established acceptance.

Keep this PR Draft. No merge, main push, rebase, force push or deployment. Existing untracked tools/ remains untouched and excluded.

@yunmin311 yunmin311 changed the title GitLineage development review: Discovery V2 and gated M2 Alpha GitLineage development review: Discovery V2 and operational M2 Alpha Oct 9, 2026
@yunmin311 yunmin311 changed the title GitLineage development review: Discovery V2 and operational M2 Alpha GitLineage development review: Discovery V2 and M2 Alpha.1 source selection Oct 9, 2026
@yunmin311 yunmin311 changed the title GitLineage development review: Discovery V2 and M2 Alpha.1 source selection GitLineage development review: Discovery V2 and M2 Beta candidate layer Oct 10, 2026
Preserve current repository relation canvas, independent Git history, hierarchical exploration, Inspector and workspace UI refinements as a development checkpoint. This commit does not represent final UI acceptance. No production deployment or main integration.
…ions

Update Private Beta selectors for classified canvas nodes without weakening authorization, comparison or download checks. Retry safe boundary ports and expose inspectable endpoint badges when no collision-free connection exists. Verify painted paths and redraw focus, and align product state with the implemented workspace and budgets.
@yunmin311 yunmin311 changed the title GitLineage development review: Discovery V2 and M2 Beta candidate layer GitLineage M2 — Unified Repository Explorer, Discovery V2 & Git History Oct 14, 2026
Clarify that opening exploration tools does not dispatch Discovery requests, while canonical cache misses can still analyze GitHub data. Extend the existing production-disabled guard to the anonymous exploration endpoint.
@yunmin311
yunmin311 marked this pull request as ready for review October 14, 2026 03:18
@yunmin311
yunmin311 merged commit 24cd567 into main Oct 14, 2026
4 checks passed
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