Nested consumer crate needs an empty [workspace] table (onboarding / aura new) #9
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Surfaced by the cycle-0006 fieldtest (
docs/specs/fieldtest-0006-substrate.md, friction #1).A standalone downstream-consumer crate that
path-depends on the engine crates and lives under the engine repo (as a real research project per C16 might, e.g. during authoring) is rejected by cargo:Resolution in the fieldtest fixture: add an empty
[workspace]table to the project crate'sCargo.toml(cargo's own keep-it-out hint; no edit to the engine root manifest). It works, but it is a non-obvious one-liner every nested project hits.Action: capture this in onboarding docs, and/or have the future
aura newscaffolder emit the[workspace]line. Not urgent; not a defect.Bit again in the cycle-0007 fieldtest (docs/specs/fieldtest-0007-signal-quality.md): the standalone consumer crate fieldtests/cycle-0007-signal-quality/ needed the empty [workspace] table to build. Confirms this is a standing onboarding wall, not a one-off — reinforces folding it into the future aura new scaffolder / onboarding docs.