feat(z8run-lance): native report nodes over the lance-graph ABI substrate - #1
Merged
Merged
Conversation
…rate
Adds a workspace-excluded crate with eight native nodes (lance-source,
-filter, -axis, -measure, -pivot, -top-k, -execute, -materialize) that
build a lance-graph `ReportPlan` node by node. FlowMessages carry only a
~100-byte `{"$kind":"lance-abi",...}` handle; populations, masks and
aggregate cells never enter JSON. Only `lance-materialize` produces text.
- Names/labels in node config resolve to FieldIds/ordinals when the node
is configured (catalog + CAM); emitted plans hold ids only.
- `lance-pivot` on a result handle re-views the same aggregate space; on a
plan it rewrites roles. `lance-execute` caches by the role-free physical
key, so a rotated plan reuses its twin's fold.
- A republished source bumps its generation; older handles fail closed.
Excluded from the workspace because it path-depends on the sibling
lance-graph checkout, which z8run's own CI does not clone.
Tests: 5 node-level falsifiers (envelope size independent of population
at 1k and 200k rows; z8run plan == native plan incl. lowered programs;
no refold on rotation; stale handle refusal; materialize refuses plans).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DCEP2fZdHYdMCtcEVcTpS2
…rough OGAR composition lance-graph-report dropped its HTML terminal (the reporting engine must not become a paper engine). lance-materialize now accepts json/csv and refuses html/typst/pdf with a pointer to the OGAR composition path, where a report is embedded by reference (lance-graph-report-ogar) and rendered by OGAR's emitters. New test: the refusal fires, and json/csv still configure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DCEP2fZdHYdMCtcEVcTpS2
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_4b5be112-de4d-446e-a0bd-9873b65defec) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_b99e37b2-1581-4218-ac92-bd389cf48da2) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new workspace-excluded crate,
crates/z8run-lance, adds eight native nodes. Together they build a lance-graphReportPlaninside a visual flow:lance-sourcelance-filter/lance-axis/lance-measure/lance-top-klance-pivotlance-executelance-materializePaged and screen output (HTML, Typst → PDF) is not a report node's job.
lance-materializerefuses those formats at configure time, and its error message points to OGAR composition: the result is embedded in aDocComposeby reference and rendered by OGAR's renderers (vialance-graph-report-ogarin the companion lance-graph PR).The control-plane rule
A
FlowMessagepayload is only a handle, about 100 bytes:{"$kind":"lance-abi","role":"plan","handle":17,"generation":4,"source":9}Rows, lanes, masks and aggregate cells never enter JSON. The only node that produces text is
lance-materialize, and it resolves CAM labels only for the members it presents.The strings in node config (field names, labels) are resolved to
FieldIds and ordinals when the node is configured. The plans the nodes emit hold ids only.A source that is republished gets a new generation, and handles minted against the old generation fail closed.
Why the crate is excluded
It path-depends on the sibling
AdaWorldAPI/lance-graphcheckout, and through that onAdaWorldAPI/ndarray. z8run's own CI checks out z8run alone. The crate carries its ownrust-toolchain.toml(1.98.1, matching lance-graph).To build it from a fleet checkout:
Depends on
The
lance-graph-reportcrate in the companion PR AdaWorldAPI/lance-graph#1271, on branchclaude/brave-mayer-65y3cy.Tests (6, all green locally)
Arcis shared.lance-materializerefuses a plan handle.format: htmlfails to configure with a pointer to OGAR composition. Its stay-silent twin checks thatjsonandcsvstill configure.🤖 Generated with Claude Code
https://claude.ai/code/session_01DCEP2fZdHYdMCtcEVcTpS2