chore: rename residual framework→objectstack dir/pin references

.changeset/rename-framework-objectstack-tier2.md

@@ -0,0 +1,4 @@
+---
+---
+
+Tier-2 of the framework -> objectstack rename: retarget the core symlink and update residual local checkout-dir / pin-file references (.objectstack-sha mentions, personal paths, a skills-path comment). Symlink + docs/comments only, no package code changes, so this releases nothing.

.github/workflows/scaffold-e2e.yml

@@ -118,7 +118,7 @@ jobs:
         # 15.1 third-party eval: the repo-internal dogfood-verification skill
         # (.claude/skills/) leaked into scaffolded projects. Two leak paths,
         # two assertions against THIS checkout:
-        #   1. The scaffolder/docs command is `skills add …/framework/skills
+        #   1. The scaffolder/docs command is `skills add …/objectstack/skills
         #      --all` — the /skills subpath is the hard boundary, because the
         #      skills CLI's --all implies --skill '*' which INCLUDES
         #      metadata.internal skills. Install from the subpath and assert

core

@@ -1 +1 @@
-/tmp/workspace/objectstack-ai/framework/packages/core
+/tmp/workspace/objectstack-ai/objectstack/packages/core

docs/adr/0078-no-silently-inert-metadata.md

@@ -87,7 +87,7 @@ v1 = the shared predicate + the audit's **verified Tier-A** shapes (authoring co
 ## Consequences
 
 - **Positive.** Closes the gate-1 instance-completeness hole and the path asymmetry: one predicate, enforced on every authoring surface, so a hand/CLI/MCP author gets the same protection the cloud build agent does. Silent inertness becomes a *loud, self-correctable* error (ADR-0038 loop) instead of a false "done". The three gates compose into an honest chain — *valid* → *complete* → *has a live consumer* → *runs correctly*. §3 makes a correct authoring un-strippable.
-- **Negative / cost.** A shared predicate plus dual wiring is more than a cloud-only rule; mitigated by reusing the `isIncoherentAggregate` pattern and the existing `@objectstack/lint` harness. The audit is a candidate list — each rule costs a verification pass before it ships (deliberately; see the sharing-rule reversal). Cloud `.framework-sha` must bump when graph-lint re-homes onto the shared predicate.
+- **Negative / cost.** A shared predicate plus dual wiring is more than a cloud-only rule; mitigated by reusing the `isIncoherentAggregate` pattern and the existing `@objectstack/lint` harness. The audit is a candidate list — each rule costs a verification pass before it ships (deliberately; see the sharing-rule reversal). Cloud `.objectstack-sha` must bump when graph-lint re-homes onto the shared predicate.
 - **Follow-up.** (1) Define the authoritative Tier-A predicate set. (2) cloud#687 is the first instance — its rules re-home onto the shared predicate in Phase 1. (3) Each Tier-B shape files its verification note before becoming a rule.
 
 ## Non-goals

docs/audits/2026-06-handwritten-docs-accuracy-followups.md

@@ -157,7 +157,7 @@ Out of scope here (generated, DO-NOT-EDIT); fix by regenerating from spec in a d
 - The `visible` type label was changed to `Expression`. Strictly, ExpressionInputSchema (packages/spec/src/shared/expression.zod.ts:83-86) accepts either a bare CEL string OR a canonical Expression envelope at input time; the doc's `Expression` label + 'CEL expression' description is accurate enough, but a reader might not realize a raw string shorthand is also accepted. Minor; not an inaccuracy.
 
 ### `guides/metadata/dashboard.mdx`
-- Descriptive prose at /Users/oszhuang/Documents/GitHub/framework/content/docs/ui/dashboards.mdx:165-169 ('ObjectUI currently renders dataset-backed metric, chart, table/list, pivot, funnel, and gauge-style widgets ... drill-down affordances') is a runtime-renderer capability claim not directly backed by the spec schemas I read. It is not false on its face (all named chart types are in ChartTypeSchema) but the specific rendering/drill-down feature claims live in ObjectUI (objectui repo / client-react), which is outside packages/spec — not independently verified here. Low priority, no evidence it is wrong.
+- Descriptive prose at /Users/oszhuang/Documents/GitHub/objectstack/content/docs/ui/dashboards.mdx:165-169 ('ObjectUI currently renders dataset-backed metric, chart, table/list, pivot, funnel, and gauge-style widgets ... drill-down affordances') is a runtime-renderer capability claim not directly backed by the spec schemas I read. It is not false on its face (all named chart types are in ChartTypeSchema) but the specific rendering/drill-down feature claims live in ObjectUI (objectui repo / client-react), which is outside packages/spec — not independently verified here. Low priority, no evidence it is wrong.
 - Line 102: filter is documented as type `FilterCondition` with note '(runtimeFilter)'. Schema (dashboard.zod.ts:121-122) confirms widget.filter is FilterConditionSchema applied as runtimeFilter — accurate. No action needed; noting only that the parenthetical 'runtimeFilter' is internal naming that may confuse authors but is faithful to the schema describe() text.
 
 ### `guides/metadata/doc.mdx`

packages/cli/CHANGELOG.md

@@ -54,7 +54,7 @@
   Migration: use the canonical kebab-case tokens `ai-studio` / `ai-seat`. All
   first-party configs were migrated in #862/#863; only stacks still carrying the
   legacy spelling are affected. Cloud's `objectos-runtime` (pinned to an older
-  framework) follows on its next `.framework-sha` bump.
+  framework) follows on its next `.objectstack-sha` bump.
 
 ### Patch Changes
 
@@ -424,7 +424,7 @@ extract` seeds bundles from it. Coverage now honours that contract — an inline
   Migration: use the canonical kebab-case tokens `ai-studio` / `ai-seat`. All
   first-party configs were migrated in #862/#863; only stacks still carrying the
   legacy spelling are affected. Cloud's `objectos-runtime` (pinned to an older
-  framework) follows on its next `.framework-sha` bump.
+  framework) follows on its next `.objectstack-sha` bump.
 
 ### Patch Changes
 

packages/plugins/driver-sqlite-wasm/scripts/restart-proof.mjs

@@ -11,7 +11,7 @@ import { createRequire } from 'node:module';
 import { dirname, join } from 'node:path';
 
 const FILENAME =
-  '/Users/zhuangjianguo/Documents/GitHub/framework/examples/app-todo/.objectstack/data/todo.wasm.db';
+  '/Users/zhuangjianguo/Documents/GitHub/objectstack/examples/app-todo/.objectstack/data/todo.wasm.db';
 const STATE_FILE = new URL('./.restart-proof-id', import.meta.url);
 
 const require = createRequire(import.meta.url);

packages/spec/CHANGELOG.md

@@ -282,7 +282,7 @@
   Migration: use the canonical kebab-case tokens `ai-studio` / `ai-seat`. All
   first-party configs were migrated in #862/#863; only stacks still carrying the
   legacy spelling are affected. Cloud's `objectos-runtime` (pinned to an older
-  framework) follows on its next `.framework-sha` bump.
+  framework) follows on its next `.objectstack-sha` bump.
 
 - b659111: feat(spec)!: remove dead author-facing metadata properties (#2377, ADR-0049 enforce-or-remove)
 
@@ -857,7 +857,7 @@
   Migration: use the canonical kebab-case tokens `ai-studio` / `ai-seat`. All
   first-party configs were migrated in #862/#863; only stacks still carrying the
   legacy spelling are affected. Cloud's `objectos-runtime` (pinned to an older
-  framework) follows on its next `.framework-sha` bump.
+  framework) follows on its next `.objectstack-sha` bump.
 
 ## 16.0.0-rc.0
 

scripts/bump-objectui.sh

@@ -13,7 +13,7 @@
 #
 # Assumes sibling layout:
 #   ~/work/objectui
-#   ~/work/framework   ← run from here
+#   ~/work/objectstack   ← run from here
 #
 # objectui ships @object-ui/console as a static SPA. The framework
 # release pipeline reads .objectui-sha, clones objectui at that commit,