Repository navigation
chore: retain Rust/Tauri plugin integration experiment - #83
Merged
Merged
Conversation
jdylanmc
marked this pull request as ready for review
September 30, 2026 16:07
This was referenced Sep 30, 2026
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.
Purpose
Retain the Rust/Tauri integration spike at a useful, reproducible stopping
point. This is an experimental tool and findings package, not production
Rust support or a public plugin SDK.
Refs #1. The real-repository adoption work informs #46; it does not close the
human acceptance requirement.
Included
experiments/plugin-spike: explicit language/framework contributioncontract, existing TypeScript adapter, syntax-backed Rust analysis, and
bounded Tauri command bindings.
checked source-derived/source-traced explanations and a separate
topo-spikeCLI with project guidance.
receipts; no renderer substitution hidden as a successful Archify check.
Node 22 macOS/Linux workflow.
synthetic semantic-probe fixture. Full local generated artifacts, packages,
private paths and caches are excluded.
What we learned
The shared graph/evidence model is usable, but scanner capabilities, source
anchors, framework joins and coverage need deliberate language-neutral
contracts. Rust syntax extraction is useful without builds; it does not resolve
all calls, conditional compilation, macros, or runtime behavior.
The controlled rust-analyzer probe demonstrated selected definitions,
references and call hierarchy under an explicitly limited project/environment.
It is historical feasibility evidence, not a shipped semantic backend or
an operating-system sandbox.
Fresh-agent use exposed real source-binding, CLI-entrypoint, publication and
diagram-layout defects. The retained implementation includes the fixes and
regressions, while preserving the limits and failed approaches in the findings.
Deliberately not included
packages/, the existing production CI or npmpublication workflow.
build/procedural-macro execution, or universal determinism claim.
starts at its first diagram; this is not the requested Storybook-like
application shell. That foundational fix is the next separate delivery.
Evidence and validation
reserved-ID and nonempty-verification regressions.
partial scan (exit 2), source references, and both renderer paths passed.
144 original context files preserved, five substantive technical views,
336 verified excerpts across 19 files, and bounded browser measurements.
Node 22 macOS and Linux passed.
passed.
corrected and independently reverified at
6c0dc0ea4cdd00e90e14b61d862effcb5ab6fc6e.See
README,REPORT, andevidence/summary.json.The reviewed head contains the current observed
mainbaselineb64bb2fc9c1ba6319287f7c701588eee3de2d1d5.Human review remains outstanding. No merge or npm publication is authorized.