Skip to content

@augmentworks/cli 0.3.9

Choose a tag to compare

View all tags
@cursor cursor released this 13 Oct 20:16
v0.3.9
9e7919c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.3.9

Immutable patch so customers get the hosted run-scope lookup hardening. This does not replace @augmentworks/cli@0.3.8.

Highlights

  • Hosted runs no longer crash when the server returns an HTML error page (AUG-335). Synthetic and saved-suite v2 bindings do not request an execution scope. A looked-up scope uses the same usability checks as the pinned path, except the revision and hash comparison when there is no suite reference. A 404 from that lookup on a packet that requires a scope stays INVALID_EXECUTION_SCOPE. Other lookup failures propagate. A non-JSON error body keeps http_status instead of INVALID_CLOUD_RESPONSE; a non-JSON success body still fails as INVALID_CLOUD_RESPONSE.
  • Documented a reproducible support/FAQ example at examples/faq-chatbot/ (AUG-282). The same response-quality server accepts AW_FAQ_POLICY=stale so one local aw-packet/0.1 check exits 0 or 10. No CLI command was added. Published npm 0.3.8 and 0.3.7 do not contain the example directory or that switch.
  • Recorded the independent inspection of npm @augmentworks/cli@0.3.8. The published tarball is unchanged and still embeds the prior 0.3.7 LAST_VERIFIED snapshot.

published_package_verified is published-line identity, not a live registry probe of this tarball. Independently inspected npm 0.3.8 remains the previous pin. Do not overwrite @augmentworks/cli@0.3.8.

Assets 2
Loading