The next pilot combines reusable labels, accessible controls and a package handoff. Each exercise resets to its own fictional app. Keep the current-input behavior while making the requested configuration change, and read the actual local version marker rather than relying on a familiar name.
Some tasks ask you to explain a real release decision instead of simulating an unsupported tenant operation. Be explicit about dependencies, connection references and generated source limits. Saving, publishing and access remain separate concerns. This practice revisits earlier material without adding a new deployment mechanism. The goal is a handoff another maker can inspect without mistaking local practice evidence for production.