Aura/crates/aura-cli/tests/fixtures/nested-nodes-project/Aura.toml at 1f6b55a8e1d7304af89f446698f170281769a72b - Aura - Gitea: Git with a cup of tea

Brummel/Aura

Files

T

claude 1f6b55a8e1 feat(cli,engine): data-only project tier at the load boundary (#241 T1-T2)

- ProjectProvenance namespace/dylib_sha256 widen to Option (Tier-1
  additive serde): a data-only run stamps commit-only provenance; old
  string-field manifests keep parsing.
- The load boundary tier-selects: a [nodes] pointer list in Aura.toml
  (one entry honored; MultiCrate / pointer-context refusals) loads the
  pointed-at crate; a root Cargo.toml stays the pre-#241 native project,
  unchanged; neither means data-only (std vocabulary, project-local
  runs/, both-tier provenance).
- ProjectEnv splits into directory facts + Option<NativeEnv>; the crate
  pipeline (metadata -> artifact -> staleness -> ABI -> charter)
  relocates byte-identical into load_crate.
- e2e fixtures: dataonly-project, multicrate-project,
  nested-nodes-project (a pointer crate resolves and stamps its
  namespace end to end).

refs #241

2026-07-12 14:42:57 +02:00

6 lines

254 B

TOML

Raw Blame History

 # nested-nodes fixture (#241): the node crate lives at a [nodes] pointer, NOT
 # at the project root (no root Cargo.toml here) — the load boundary must
 # resolve the crate through the pointer, not assume root-collocation.
 [nodes]
 crates = ["nodecrate"]