chore: version packages

Author: github-actions[bot]

.changeset/21923-datasource-origin-from-provenance.md

@@ -75,7 +75,7 @@ docker run -p 8080:8080 \
   -e OS_DATABASE_URL="postgres://user:pass@db-host:5432/myapp" \
   -e OS_AUTH_SECRET \
   -e OS_SECRET_KEY \
-  ghcr.io/objectstack-ai/objectstack:17.7.0
+  ghcr.io/objectstack-ai/objectstack:17.7.1
 ```
 
 (`OS_ARTIFACT_PATH` also accepts an `https://` URL, so the artifact can come
@@ -93,7 +93,7 @@ docker run -p 8080:8080 \
   -e OS_ARTIFACT_URL="https://releases.example.com/hotcrm-2.2.2.json#sha256=<64 hex chars>" \
   -e OS_DATABASE_URL="postgres://user:pass@db-host:5432/myapp" \
   -e OS_AUTH_SECRET -e OS_SECRET_KEY \
-  ghcr.io/objectstack-ai/objectstack:17.7.0
+  ghcr.io/objectstack-ai/objectstack:17.7.1
 ```
 
 Both schemes work: `https://…` is fetched at boot, `file:///…` is read directly
@@ -144,7 +144,7 @@ COPY . .
 RUN npx os build              # → dist/objectstack.json
 
 # ── Runtime: the official ObjectStack runtime image ──────────────────
-FROM ghcr.io/objectstack-ai/objectstack:17.7.0
+FROM ghcr.io/objectstack-ai/objectstack:17.7.1
 COPY --from=build --chown=node:node /app/dist/objectstack.json /srv/app/objectstack.json
 ```
 
@@ -162,7 +162,7 @@ image)? The official image is nothing more than:
 
 ```dockerfile title="Dockerfile (self-built runtime, equivalent)"
 FROM node:22-slim
-RUN npm install -g @objectstack/cli@17.7.0
+RUN npm install -g @objectstack/cli@17.7.1
 
 WORKDIR /srv/app
 RUN chown node:node /srv/app

.changeset/21967-view-expansion-per-package.md

@@ -18,7 +18,7 @@ migration steps, then covers new capabilities and notable fixes.
 
 ## Versions
 
-- [v17.0.0](/docs/releases/v17) — Files become owned `sys_file` records with server-enforced `accept`/`maxSize` and a governed download path, bulk export becomes its own opt-in privilege, the SDK is reconciled against the routes the server actually mounts (21 dead methods out, 40+ real ones in), approval nodes route approvers dynamically via CEL expressions and decision outputs, a datasource that cannot connect fails the boot, and Node 22 becomes the supported floor; 17.1 adds partial field masking, record-view auditing on `sys_audit_log`, and a per-object read-only approval visibility tier — and makes a deactivated permission set or position actually stop granting access, withdraws the bulk-export wildcard from the shipped admin sets, and gives all three flow doors one honest HTTP status table; 17.2 tightens by-id `update`/`delete` against a silently-dropped `where` predicate or a mismatched id, retires `sys_position.permissions` and other dead ADR-0049 surfaces, and stops analytics from answering the wrong number on a cross-object filter (current series: 17.7.0, released 2026-10-06).
+- [v17.0.0](/docs/releases/v17) — Files become owned `sys_file` records with server-enforced `accept`/`maxSize` and a governed download path, bulk export becomes its own opt-in privilege, the SDK is reconciled against the routes the server actually mounts (21 dead methods out, 40+ real ones in), approval nodes route approvers dynamically via CEL expressions and decision outputs, a datasource that cannot connect fails the boot, and Node 22 becomes the supported floor; 17.1 adds partial field masking, record-view auditing on `sys_audit_log`, and a per-object read-only approval visibility tier — and makes a deactivated permission set or position actually stop granting access, withdraws the bulk-export wildcard from the shipped admin sets, and gives all three flow doors one honest HTTP status table; 17.2 tightens by-id `update`/`delete` against a silently-dropped `where` predicate or a mismatched id, retires `sys_position.permissions` and other dead ADR-0049 surfaces, and stops analytics from answering the wrong number on a cross-object filter (current series: 17.7.1, released 2026-10-06).
 - [v16.0.0](/docs/releases/v16) — One org identifier (`organizationId`) across hooks and actions, quorum + per-group sign-off (会签) approvals with metadata-declared decision actions, time-relative automations, filtered roll-ups, strict dashboard widgets, an identity-scoped MCP stdio transport, and a platform-wide enforce-or-remove sweep that makes dead metadata loud; 16.1 adds a `requires` capability-provider preflight, two more dashboard build gates, and `runAs:'user'` automations that run with the triggering user's real grants (final release: 16.1.0).
 - [v15.0.0](/docs/releases/v15) — Explain record access layer by layer, a docked AI workspace in the Console, project-ready Gantt charts, and phone sign-in; 15.1 adds permission-following attachments, no-code third-party connectors, dashboard-wide filters, pinyin search, and whole-record inline editing — with materially safer multi-tenant and write-path defaults (final release: 15.1.1).
 - [v14.0.0](/docs/releases/v14) — ADR-0090 vocabulary convergence completed, object `enable.*` flags become real gates, admin user management, phone/SMS auth, book-audience enforcement, data-lifecycle contract, and effective-dated grants (final release: 14.8.0).

.changeset/21968-spec-default-agent-chat-door.md

@@ -52,7 +52,7 @@ The official image is `ghcr.io/objectstack-ai/objectstack`, and its tags mirror
 
 ```bash
 # docker-compose.yml, or your orchestrator's manifest
-image: ghcr.io/objectstack-ai/objectstack:17.7.0
+image: ghcr.io/objectstack-ai/objectstack:17.7.1
 ```
 
 On a host running the artifact directly under systemd, the same move is a file

content/docs/deployment/self-hosting.mdx

@@ -29,7 +29,7 @@ Multi-arch: `linux/amd64` + `linux/arm64`.
 [Self-Hosted Deployment](https://objectstack.ai/docs/deployment/self-hosting)):
 
 ```dockerfile
-FROM ghcr.io/objectstack-ai/objectstack:17.7.0
+FROM ghcr.io/objectstack-ai/objectstack:17.7.1
 COPY --chown=node:node dist/objectstack.json /srv/app/objectstack.json
 ```
 
@@ -40,7 +40,7 @@ docker run -p 8080:8080 \
   -v "$PWD/dist/objectstack.json:/srv/app/objectstack.json:ro" \
   -e OS_DATABASE_URL="postgres://user:pass@db-host:5432/myapp" \
   -e OS_AUTH_SECRET -e OS_SECRET_KEY \
-  ghcr.io/objectstack-ai/objectstack:17.7.0
+  ghcr.io/objectstack-ai/objectstack:17.7.1
 ```
 
 `OS_ARTIFACT_PATH` also accepts an `https://` URL, so the artifact can come
@@ -72,7 +72,7 @@ for a `file:…` path — one box only, wrong for multi-node) and MongoDB
 (`libsql://…` / Turso). Add one by extending the image:
 
 ```dockerfile
-FROM ghcr.io/objectstack-ai/objectstack:17.7.0
+FROM ghcr.io/objectstack-ai/objectstack:17.7.1
 USER root
 RUN npm install -g tedious
 USER node
@@ -100,5 +100,5 @@ reverse-proxy / multi-node guidance:
 ## Local build of this image
 
 ```bash
-docker build -t objectstack:dev --build-arg OS_CLI_VERSION=17.7.0 docker/
+docker build -t objectstack:dev --build-arg OS_CLI_VERSION=17.7.1 docker/
 ```

content/docs/releases/index.mdx

@@ -1,5 +1,14 @@
 # @objectstack/example-crm
 
+## 4.0.100
+
+### Patch Changes
+
+- Updated dependencies [04e776b]
+  - @objectstack/spec@17.7.1
+  - @objectstack/runtime@17.7.1
+  - @objectstack/service-i18n@17.7.1
+
 ## 4.0.99
 
 ### Patch Changes

content/docs/upgrading.mdx

@@ -1,6 +1,6 @@
 {
   "name": "@objectstack/example-crm",
-  "version": "4.0.99",
+  "version": "4.0.100",
   "description": "Minimal CRM example \u2014 a smoke-test workspace that exercises the metadata loading pipeline (objects \u2192 views \u2192 app \u2192 dashboard \u2192 hook \u2192 flow \u2192 seed). For a full-featured enterprise CRM see https://github.com/objectstack-ai/hotcrm.",
   "license": "Apache-2.0",
   "private": true,

docker/README.md

@@ -1,5 +1,12 @@
 # @objectstack/example-multi-package
 
+## 0.0.7
+
+### Patch Changes
+
+- Updated dependencies [04e776b]
+  - @objectstack/spec@17.7.1
+
 ## 0.0.6
 
 ### Patch Changes