release: v0.10.0 (worker 0.3.0, receiver 0.2.1, admin 0.7.0) - #174
Merged
Conversation
Ships the issue #54 trigger/flow graph across all three packages. worker 0.3.0: run records persist triggerIndex and triggerType (the attribution join for forge runs, INT-RUN-HISTORY-FILE-CONTRACT), the shared platform browser opener at ./open-browser, the ./materialize export subpath, aiTriggerAllows exported from ./flow-gate, the chain cap defaults exported from ./config, and defaultGraphDir. receiver 0.2.1: no source change; republished so its @edgehero/ pi-dispatch range (^0.3.0) matches the worker on the registry, per the publish sync tests. admin 0.7.0: the GRAPH dashboard view (g), /dispatch graph, and /dispatch graph html with --no-open and --full-paths; the graph read-model and edge-honesty fold; loops grouped inside their skill; record-derived forge scope labels; the ASCII overlay gap closed; the review-hardening fixes (type-guarded attribution, folder-scoped refusals, raw-index trigger CRUD, Esc layering). RUNTIME_VERSION and RECEIVER_VERSION track the workspace versions per the anti-drift tests. Lock updated by hand for versions only, the npm-minor normalization noise filtered per the recorded gotcha. Suite in the CI posture: 2175 pass, 0 skipped; admin bundle builds. Signed-off-by: Rob Boerman <robboerman@live.nl>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ships the issue #54 trigger/flow graph across all three packages. Merging this fires the npm publishes (release.yml is version-gated per package) and the ghcr image retags off the root version.
triggerIndex/triggerType(forge run attribution,INT-RUN-HISTORY-FILE-CONTRACT); new export subpaths./open-browserand./materialize;aiTriggerAllowsexported from./flow-gate; chain-cap defaults exported from./config;defaultGraphDir.@edgehero/pi-dispatchrange (^0.3.0) matches the worker on the registry, per the publish sync tests.g),/dispatch graph, and/dispatch graph htmlwith--no-open/--full-paths; the graph read-model and edge-honesty fold; loops grouped inside their skill; record-derived forge scope labels; the ASCII overlay gap closed; the review-hardening fixes.RUNTIME_VERSION/RECEIVER_VERSIONand the wizard tests' two spelled-out pin literals move with the versions per the anti-drift discipline. The lock is hand-patched for versions only (the npm-minor normalization noise filtered per the recorded gotcha).Upgrade actions for existing deployments: update the console with
pi install npm:@edgehero/pi-dispatch-adminand let bare/dispatch's skew notice walk the runtime through/dispatch setup. No service unit or env changes; the new record fields are additive and old records read fine.Suite in the CI posture: 2175 pass, 0 skipped; admin bundle builds.