A release package needs a stable name, a four-part version and the components required by its target. The app can depend on tables, relationships, flows, connection references and environment values. A package with the right title can still route operations to the wrong source.
The local workspace records an unmanaged or managed choice and a published marker. Those fields teach a bounded release vocabulary; they do not export or import a solution. The reasoning tasks cover real dependency checks and the documented read-only status of generated pa.yaml files. Verify the supported authoring path and target app version before treating a source-file edit as a published change.