chore: update fossils for 2026-06-23

[Asifdotexe]

Summary by CodeRabbit

• Chores
  • Updated metadata records across several processed datasets to include more complete source provenance and reference details.
  • Added or refined historical record entries while keeping the underlying snapshot data unchanged.

[coderabbitai]

📝 Walkthrough

Walkthrough

Five processed graph JSON files (claude-code, langchain, numpy, react, zed) have their top-level fossils metadata updated. Placeholder fossils.survivor entries with empty fields and max timestamps are replaced with populated fossils.genesis records and, where applicable, real fossils.survivor records containing source file paths, content, commit references, and line numbers. The snapshots arrays remain unchanged.

Changes

Fossils Metadata Population

Layer / File(s)	Summary
Populate fossils metadata in all graph JSON files data/processed/claude-code_graph.json, data/processed/langchain_graph.json, data/processed/numpy_graph.json, data/processed/react_graph.json, data/processed/zed_graph.json	Replaces placeholder fossils.survivor entries (empty fields, max timestamps) with real fossils.genesis and fossils.survivor records containing source file paths, content snippets, commit/view_commit references, timestamps, years, and line numbers. snapshots data is unchanged in all five files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Asifdotexe/Theseus#49: Directly modifies the same data/processed/*_graph.json fossils metadata fields, switching between fossils.genesis presence and placeholder vs. populated fossils.survivor provenance details.

Poem

🐇 Hop, hop through the JSON fields so deep,
Where old placeholder fossils once did sleep.
A genesis record rises, survivor made whole,
With commits and content to fill every role.
The snapshots unchanged, the provenance now true —
This bunny approves what the data came through! 🦴

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: updating fossils metadata in the processed graph files for 2026-06-23.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/fossil-update

---

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.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@data/processed/claude-code_graph.json`:
- Line 1: The fossil metadata is inconsistent because fossils.genesis is newer
than fossils.survivor, which violates the expected oldest-first ordering.
Regenerate the dataset in claude-code_graph.json so the earliest-authored line
is assigned to fossils.genesis and the later one to fossils.survivor, and make
sure the timestamps and associated file/commit fields in the fossils object
reflect that corrected ordering.

In `@data/processed/langchain_graph.json`:
- Line 1: The fossils metadata in this graph is inconsistent because the
recorded genesis entry is newer than the survivor entry, violating the
oldest-ever versus oldest-still-present contract. Recompute the fossils block
for langchain_graph.json so that fossils.genesis and fossils.survivor reflect
the correct earliest historical snapshot and the oldest file still present, and
ensure their timestamps are ordered correctly.

In `@data/processed/zed_graph.json`:
- Line 1: The fossils metadata in this JSON is inconsistent because the genesis
entry is newer than the survivor entry, so regenerate this snapshot data to
restore the expected ordering. Update the `fossils.genesis` and
`fossils.survivor` values together in `zed_graph.json` so the genesis timestamp
is older than the survivor timestamp and the associated file/commit metadata
remains consistent with that ordering.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8b78c7b4-c95e-438c-aa9c-5f18de001259

📥 Commits

Reviewing files that changed from the base of the PR and between 2938372 and c797f7a.

📒 Files selected for processing (8)

• data/processed/claude-code_graph.json
• data/processed/langchain_graph.json
• data/processed/numpy_graph.json
• data/processed/react_graph.json
• data/processed/zed_graph.json
• data/raw/langchain_data.json
• data/raw/react_data.json
• data/raw/zed_data.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift

Genesis is newer than survivor on Line 1

fossils.genesis.timestamp (1740421074) is greater than fossils.survivor.timestamp (1740245022). That breaks the fossil contract (genesis should be the oldest-authored line overall). Please regenerate this dataset so genesis is not newer than survivor.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@data/processed/claude-code_graph.json` at line 1, The fossil metadata is
inconsistent because fossils.genesis is newer than fossils.survivor, which
violates the expected oldest-first ordering. Regenerate the dataset in
claude-code_graph.json so the earliest-authored line is assigned to
fossils.genesis and the later one to fossils.survivor, and make sure the
timestamps and associated file/commit fields in the fossils object reflect that
corrected ordering.

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift

Genesis is newer than survivor on Line 1

fossils.genesis.timestamp (1666666586) is greater than fossils.survivor.timestamp (1666648275). This violates the fossils contract for oldest-ever vs oldest-still-present lineage. Please recompute fossils metadata for this graph.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@data/processed/langchain_graph.json` at line 1, The fossils metadata in this
graph is inconsistent because the recorded genesis entry is newer than the
survivor entry, violating the oldest-ever versus oldest-still-present contract.
Recompute the fossils block for langchain_graph.json so that fossils.genesis and
fossils.survivor reflect the correct earliest historical snapshot and the oldest
file still present, and ensure their timestamps are ordered correctly.

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift

Genesis is newer than survivor on Line 1

fossils.genesis.timestamp (1613862336) is greater than fossils.survivor.timestamp (1613840554). This contradicts the documented fossils meaning and should be regenerated to restore consistency.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@data/processed/zed_graph.json` at line 1, The fossils metadata in this JSON
is inconsistent because the genesis entry is newer than the survivor entry, so
regenerate this snapshot data to restore the expected ordering. Update the
`fossils.genesis` and `fossils.survivor` values together in `zed_graph.json` so
the genesis timestamp is older than the survivor timestamp and the associated
file/commit metadata remains consistent with that ordering.