Skip to content

feat(io): export deterministic graph data subsets with referential closure - #849

Merged
DecisionNerd merged 3 commits into
mainfrom
feat/786-graph-data-subset-export
Aug 20, 2026
Merged

DecisionNerd merged 3 commits into
mainfrom
feat/786-graph-data-subset-export

Conversation

@DecisionNerd

@DecisionNerd DecisionNerd commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Closes #786

Summary

  • add portable-v2 graph-data-subset preview/plan APIs over pinned generations
  • support induced-edges and referential closure with property redaction
  • emit verified expanded/bundle packages with content-free selection.graph_subset receipts

Test plan

  • cargo test -p graphforge-storage --lib project_portable_v2_subset
  • cargo clippy -p graphforge-storage --lib -- -D warnings
  • CI Gate green on exact head

Made with Cursor


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Add induced-edges and referential graph-data-subset planning with
property redaction, deterministic fingerprints, and verified package
emission for #786.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 20, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 46 minutes

Limit details: You’ve used the included review currently available. Your 67 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

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?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c70d7592-347f-445a-95f9-b62b99df7855

📥 Commits

Reviewing files that changed from the base of the PR and between a000745 and 71d9e8a.

⛔ Files ignored due to path filters (1)
  • docs/book/architecture/portable-project-v2.md is excluded by !**/*.md, !**/docs/**
📒 Files selected for processing (6)
  • crates/graphforge-api/src/belief_projection.rs
  • crates/graphforge-storage/src/graph_projection.rs
  • crates/graphforge-storage/src/lib.rs
  • crates/graphforge-storage/src/project_portable_v2_export.rs
  • crates/graphforge-storage/src/project_portable_v2_selection.rs
  • crates/graphforge-storage/src/project_portable_v2_subset.rs

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

@github-actions github-actions Bot added core Core source code changes documentation Improvements or additions to documentation labels Aug 20, 2026
Keep GraphProjectionSelection callers compiling after adding closure
and property-redaction fields for portable graph-data subsets.

Co-authored-by: Cursor <cursoragent@cursor.com>
@codspeed

codspeed Bot commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Merging this PR will regress 1 benchmark

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 1 regressed benchmark
✅ 61 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ Simulation transaction_classification[1] 339.6 ns 404.8 ns -16.12%
⚡ WallTime durable_open 27.4 µs 19.1 µs +43.7%
⚡ WallTime spill_compaction 4.3 ms 3.9 ms +10.29%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing feat/786-graph-data-subset-export (71d9e8a) with main (91544c3)1

Open in CodSpeed

Footnotes

  1. No successful run was found on main (a000745) during the generation of this report, so 91544c3 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@DecisionNerd
DecisionNerd merged commit f76691a into main Aug 20, 2026
26 checks passed
@DecisionNerd
DecisionNerd deleted the feat/786-graph-data-subset-export branch September 17, 2026 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Core source code changes documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(io): export deterministic graph data subsets with referential closure

1 participant