v0.2.2

Clearer banking and marketing setup instructions for platform v0.4.0.

Changes

• Distinguish fresh-platform initialization from adding Java monthly banking to
  an existing marketing installation. The banking archive includes the complete
  second-domain procedure; the marketing guide directs operators to that route.
• Preserve existing platform and network identity, customer and partner model
  settings, marketing credentials, shared A2A budgets and saved results when
  adding banking. Reject duplicate connections or partial starter setup before
  writes, and retain a private backup of the Runtime connection file.
• Explain the initial Runtime recreation required for static connections, then
  check configured banking capabilities and a saved marketing run through the
  native Python SDK without launching a simulation.
• Refresh versioned archive names and download instructions. The scenarios,
  service images, SDKs and model profiles are unchanged from v0.2.1.

Compatibility

• Platform: v0.4.0, distributed separately.
• Java: ai.astraform:sdk-java:0.4.5 from Maven Central.
• Python: astraform-sdk==0.3.5 from PyPI.
• Provider contracts: 1.2.3.

These archives retain the existing image digests and image-source revision.
The release manifest separately identifies the packaging revision and archive
checksums. Updating the packaged guides does not upgrade platform capabilities
or change an older archive. No new SDK installation is needed for the supplied
container workflow.

Downloads and operation

Choose Python issued banking, Java issued banking, Java monthly banking or
scheduled marketing from the release assets. Verify the matching .sha256 file
before extraction and follow the bundled README. The shared
release-manifest.json records the four archives, image identities and source
revisions; each archive includes its own file manifest. A source version does
not establish that release assets are available.

For an existing marketing installation, use the Java monthly-banking guide's
second-domain procedure. Do not rerun a fresh initializer over existing
connections or delete them to bypass its refusal. Finish active runs before
changing static connections and recreating Runtime. This procedure does not
provide automatic live registration or modify accepted runs.

Preserve platform database and evidence volumes, configuration and deployment
identity. Marketing domain and agency conversation state remain in memory.
These trusted single-host examples do not establish production isolation,
high availability or population capacity. Keep credentials and evidence private.
A completed simulation does not certify advice quality or execute a real payment
or campaign launch.

Published v0.2.1 and earlier archives retain their original bytes, image pins
and instructions. Use each archive's guide and manifest rather than replacing
its images with another version's selection. The online
monthly-banking guide
also describes the additive route for unchanged v0.2.1 downloads.

Astraform-authored samples retain Apache License 2.0. Platform software and
third-party dependencies retain their separate terms.