fix: update theseus engine

[Asifdotexe]

The action didn't have logging for rust processing pipeline, added that.

Summary by CodeRabbit

• New Features

  • Added simplified workflow run options to either resume processing or complete a full extraction from scratch.
  • Full fossil scanning remains available during workflow runs.

• Documentation

  • Improved command-line help for reprocessing targets, including rebuilding everything, processing the latest period, or specifying a month.

• Data Updates

  • Refreshed repository composition history and analysis snapshots with additional periods and updated file-level statistics.

[coderabbitai]

Warning

Review limit reached

@Asifdotexe, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c469f327-d403-4fb7-9194-d4df1f4163ac

📥 Commits

Reviewing files that changed from the base of the PR and between 57a10fa and a539d65.

📒 Files selected for processing (2)

• scripts/analyse_repository.py
• scripts/run_pipeline.py

📝 Walkthrough

Walkthrough

The workflow now selects resume or complete-extraction runs, with complete extraction mapping to --reprocess all. CLI help documents broader reprocess targets, composition snapshots were updated, and PyLint now initializes from the repository root.

Changes

Pipeline interface

Layer / File(s)	Summary
Reprocess target contract scripts/analyse_repository.py, scripts/run_pipeline.py	CLI help now documents all, last, and explicit YYYY-MM reprocess targets.
Workflow run mode wiring .github/workflows/theseus-engine.yml	run_mode replaces the dispatch reprocess input, and complete extraction adds --reprocess "all" to the pipeline arguments.

Composition artifacts

Layer / File(s)	Summary
Composition history and state data/raw/claude-code_history.jsonl, data/state/*_state.json	Monthly composition history and persisted Claude-Code, NumPy, and Zed file-composition mappings were added or regenerated.

Lint configuration

Layer / File(s)	Summary
PyLint module path pyproject.toml	The PyLint init hook now adds the repository root to sys.path instead of scripts.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Asifdotexe/Theseus#34: Shares the --reprocess CLI plumbing and snapshot filtering behavior.
• Asifdotexe/Theseus#71: Overlaps the workflow and CLI --reprocess argument interface.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is too generic and does not clearly describe the main workflow and data-state updates in this changeset.	Use a specific title that mentions the Theseus workflow and repository state updates, e.g. adding run-mode handling and refreshing state snapshots.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-data-and-action-flow

---

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/state/langchain_state.json`:
- Line 1: Remove duplicate keys from the file_compositions object in the
generated langchain_state snapshot, specifically ensuring
libs/langchain/tests/integration_tests/test_compile.py appears only once with
merged metadata. Regenerate the artifact or validate JSON with duplicate-key
detection before committing.

In `@data/state/zed_state.json`:
- Line 1: Remove the duplicate file_compositions entries for
assets/icons/replace_all.svg and assets/icons/terminal.svg in the snapshot JSON,
ensuring each key appears exactly once and retains its complete composition
data. Validate the resulting JSON through the downstream json.loads path before
committing.

In `@scripts/analyse_repository.py`:
- Around line 484-486: The reprocessing documentation and log wording must
reflect the full target contract (`all`, `last`, or a specific period) instead
of only `YYYY-MM`. In scripts/analyse_repository.py lines 484-486, update the
process_repository/main docstrings and “Re-processing period” log wording; in
scripts/run_pipeline.py lines 171-174, update the run_pipeline/main docstrings
to describe a general target.

🪄 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 Plus

Run ID: 01de64b7-4a13-4180-bdf8-df29947b5bac

📥 Commits

Reviewing files that changed from the base of the PR and between bab478d and 57a10fa.

📒 Files selected for processing (16)

• .github/workflows/theseus-engine.yml
• data/raw/claude-code_history.jsonl
• data/raw/langchain_history.jsonl
• data/raw/numpy_history.jsonl
• data/raw/react_history.jsonl
• data/raw/tensorflow_history.jsonl
• data/raw/zed_history.jsonl
• data/state/claude-code_state.json
• data/state/langchain_state.json
• data/state/numpy_state.json
• data/state/react_state.json
• data/state/tensorflow_state.json
• data/state/zed_state.json
• pyproject.toml
• scripts/analyse_repository.py
• scripts/run_pipeline.py