Release binding
Name the release before the patch.
A target-specific baseline gives every later check an exact identity. The project binding contains safe scope identifiers, not credentials or signing material.
hyfens init → hyfens release androidProduct
A patch path that starts with source.
The familiar Flutter workflow, with the release identity and trust boundary kept visible at every handoff.
The commands stay close to the work.
Hyfens does not ask developers to author bytecode, function IDs, source-unit files, or a second UI layer.
Source checkout
# from a Flutter project
$ hyfens doctor
$ hyfens init
$ hyfens release android
$ hyfens patch android
$ hyfens verify
$ hyfens deployNormal source in. A bounded artifact out.
Build-time instrumentation supports a declared subset of ordinary Dart and Flutter source while normal Flutter AOT remains the fallback. The runtime interprets only a bounded, signed payload with capabilities owned by the release.
If the change needs a normal store release, the command surface says so. That stop is a correctness feature.
Each handoff has one job.
Change analysis
Let the toolchain classify the edit.
Analyze ordinary source against the release. Supported changes can continue. Native, dependency, or unsupported inputs stop with a clear diagnostic.
hyfens analyzeArtifact trust
Inspect the exact bytes.
Patch Format v1 carries the signed artifact boundary. Inspect and verify the digest, signature, capabilities, and release binding before deployment.
hyfens patch android → hyfens verifyControlled delivery
Deploy through a chosen profile.
The active profile selects the endpoint and organization, application, and environment scope. Managed and self-hosted delivery use the same CLI and identity authority.
hyfens profile current → hyfens deployA clear stop beats a risky success.
Native code, manifests, permissions, entitlements, dependency changes, and unsupported Dart or Flutter constructs are outside the patch boundary. Use a normal store release for those edits.
Boundary result
hyfens analyze
change: unsupported input
result: store-release-requiredSee the security boundary.
Understand what the device checks, what the service can do, and what remains outside the claim.