@fabricorg/platform-host 7.2.1 → 7.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,19 @@
1
1
  # @fabricorg/platform-host
2
2
 
3
+ ## 7.2.3
4
+
5
+ ### Patch Changes
6
+
7
+ - fd1f88f: Publish the current packaged documentation, product names and resolved workspace dependency minimums under new patch versions. The release audit found retained package versions whose consumer-visible metadata differs from their registry tarballs. Runtime source is unchanged apart from regenerated generator version stamps.
8
+
9
+ The release guard now retains nested manifest fields while canonicalizing key order, so dependency, peer and export changes cannot disappear from the comparison. Development-only dependencies remain excluded.
10
+
11
+ ## 7.2.2
12
+
13
+ ### Patch Changes
14
+
15
+ - 796b9d5: Ship `MIGRATION-7.md`. Version 7.0.0 carried no source change of its own, only a peer range that moved, and the support policy promises every major carries a migration document. The document says exactly that, and points at what 7.1 and 7.2 did change.
16
+
3
17
  ## 7.2.1
4
18
 
5
19
  ### Patch Changes
package/MIGRATION-7.md ADDED
@@ -0,0 +1,34 @@
1
+ # Migrating to @fabricorg/platform-host 7
2
+
3
+ **Nothing in your code has to change.** Version 7.0.0 carries no source change
4
+ of its own. Its only entry is a dependency update: `@fabricorg/assembly` went
5
+ to 0.4.0, and a peer range on a pre-1.0 package moved, which forces a major
6
+ here even though this package's behaviour and public surface are identical to
7
+ 6.x.
8
+
9
+ This document exists because the support policy says a major carries one. A
10
+ major with nothing to migrate should say so plainly rather than leave you
11
+ reading a changelog to find out.
12
+
13
+ ## What to check anyway
14
+
15
+ Upgrade `@fabricorg/assembly` alongside it. The supported set is pinned in
16
+ `contracts/fabric-family/compatibility.v1.json`; mixing versions across the
17
+ family may work and is not supported.
18
+
19
+ ## What actually changed after 7.0.0
20
+
21
+ The releases that follow it do carry behaviour, and are worth reading if you
22
+ are coming from 6.x:
23
+
24
+ - **7.1.0** — the host reads an action's `completion` mode. An adapter that
25
+ returns `acceptedExternalOperation` parks the invocation with a durable
26
+ handoff; `completeExternalInvocation` settles it by external reference;
27
+ `reconcileOverdueCompletions` sweeps handoffs past their deadline. A custom
28
+ store must persist `pendingCompletion` and `externalCompletion`, or the
29
+ worker re-runs a handoff. PostgreSQL migration 3 adds the columns.
30
+ - **7.1.1** — a repeated completion is judged by a content digest, so a second
31
+ callback carrying a different result is a contradiction rather than an
32
+ absorbed replay.
33
+ - **7.2.0** — `tenantIsolationChecks()`, six checks proving scope is a key on
34
+ every read, write, claim, and completion. Run them against your store.
package/README.md CHANGED
@@ -8,7 +8,7 @@ pnpm add @fabricorg/platform@^1.2.0 @fabricorg/platform-host@^6.0.0 @fabricorg/a
8
8
 
9
9
  ## AI agent integration boundary
10
10
 
11
- Application and vertical owners install this package. Hermes, Fabric Harness, and other external agent
11
+ Application and vertical owners install this package. Hermes, TechFabric Harness, and other external agent
12
12
  runtimes do not import Platform Host merely to call a deployed application. They connect to the
13
13
  application's authenticated REST or MCP gateway, discover only the actions allowed by their
14
14
  registration, and submit stable idempotent commands. The gateway derives tenant and actor identity and
@@ -16,7 +16,7 @@ calls `submitAction()`; an agent must never call handlers, adapters, workflow in
16
16
  writes directly.
17
17
 
18
18
  See the [Platform Host 6.x agent integration
19
- guide](https://platform.fabric.pro/docs/platform/reference/platform-host) for application wiring,
19
+ guide](https://platform.techfabric.com/docs/platform/reference/platform-host) for application wiring,
20
20
  execution-time authorization, the PostgreSQL transaction binder, recovery semantics, and the external
21
21
  gateway contract.
22
22
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fabricorg/platform-host",
3
- "version": "7.2.1",
3
+ "version": "7.2.3",
4
4
  "description": "Canonical governed mutation host for @fabricorg/platform: durable invocation, policy, state-machine, handler, event, and adapter orchestration behind persistence ports.",
5
5
  "keywords": [
6
6
  "fabric",
@@ -41,6 +41,7 @@
41
41
  "README.md",
42
42
  "MIGRATION-2-IDEMPOTENCY.md",
43
43
  "MIGRATION-6-PRODUCTION.md",
44
+ "MIGRATION-7.md",
44
45
  "CHANGELOG.md",
45
46
  "LICENSE"
46
47
  ],
@@ -53,8 +54,8 @@
53
54
  "tsup": "^8.5.0",
54
55
  "typescript": "^5.7.3",
55
56
  "vitest": "^4.1.5",
56
- "@fabricorg/platform": "1.5.1",
57
- "@fabricorg/assembly": "^0.4.2"
57
+ "@fabricorg/platform": "1.6.0",
58
+ "@fabricorg/assembly": "^0.4.3"
58
59
  },
59
60
  "engines": {
60
61
  "node": ">=20"