docs: add repository Pages landing source

[seonghobae]

Outcome

Add a concise repository-facing docs/index.md landing source for the already-enabled GitHub Pages surface without changing runtime behavior or competing with active feature stacks.

The page corrects one public-positioning mismatch in the current repository: LineageWeave has progressed beyond the original synthetic reconstruction demo into an authenticated PostgreSQL/API/web product stack, while synthetic fixtures remain test/example evidence rather than the entire product boundary.

This PR intentionally does not rewrite the large README while many active product branches exist. Repository description/topics and the exact DeepWiki badge remain separate public-surface work; Pages publication/source configuration is not claimed changed until the merged default branch and live Pages state are verified.

---

Summary by CodeRabbit

• 문서
  • LineageWeave의 주요 목적과 기능을 소개하는 문서를 추가했습니다.
  • 계보 재구성, 운영 대시보드, 증거 기반 질의, 인증 API 및 웹 클라이언트 등의 제품 영역을 설명합니다.
  • 관련 문서 링크와 현재 제품 상태 정보를 제공하며, 테스트 및 예제용 합성 데이터 사용 현황을 안내합니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 4c73a598-ac66-4c11-8aa2-526015703cf0

📥 Commits

Reviewing files that changed from the base of the PR and between cb187ca and 08a95e3.

📒 Files selected for processing (1)

• docs/index.md

---

📝 Walkthrough

Walkthrough

docs/index.md에 LineageWeave의 목적, 제품 표면, 관련 문서, 현재 상태와 증거 기준을 설명하는 새 문서 페이지를 추가했습니다.

Changes

LineageWeave 문서

Layer / File(s)	Summary
제품 개요와 문서 정보 docs/index.md	LineageWeave의 목적과 사용 시점을 설명합니다. 제품 표면, 관련 문서 링크, 인증된 제품 스택의 상태와 증거 기준을 추가합니다.

Estimated code review effort: 1 (Trivial) | ~2 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/repository-pages-surface

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🟡 Pages ignores the new landing source

On Pages deployments, index.md never enters the generated artifact because the workflow publishes only _site. The public landing page remains unchanged.

Prompt for agents

Integrate docs/index.md into the existing deterministic GitHub Pages publication path. The workflow in .github/workflows/ontology-pages.yml currently triggers only for ontology publication inputs and uploads the `_site` tree produced by scripts/publish_ontology_site.py. The renderer in scripts/build_ontology_site.py creates its own root index.html and never reads docs/index.md. Update the governed renderer/publication contract and workflow paths so this source deterministically produces the deployed root landing page, while preserving the ADR 0159 fail-closed publication and deterministic-output requirements. Add contract tests proving changes to docs/index.md affect the generated root page and trigger Pages validation/publication.

---

Was this helpful? React with 👍 or 👎 to provide feedback.