Skip to content

docs(readme): drop the Codebase Metrics table#2304

Merged
os-zhuang merged 1 commit into
mainfrom
docs/readme-drop-metrics
Jun 24, 2026
Merged

docs(readme): drop the Codebase Metrics table#2304
os-zhuang merged 1 commit into
mainfrom
docs/readme-drop-metrics

Conversation

@os-zhuang

Copy link
Copy Markdown
Contributor

What

Remove the Codebase Metrics table from the README. It is hand-maintained, drifts (the source-package and test-file counts were already stale and had to be patched), and several figures (exported schemas, .describe() count, service contracts, tests-passing) can't be cheaply verified. Not worth the upkeep. Docs-only.

🤖 Generated with Claude Code

Hand-maintained vanity metrics that drift (source-package and test-file counts
were already stale and patched) and add little for readers. Removing rather
than scripting upkeep.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
spec Building Building Preview, Comment Jun 24, 2026 4:16pm

Request Review

@github-actions github-actions Bot added documentation Improvements or additions to documentation size/s labels Jun 24, 2026
@os-zhuang
os-zhuang merged commit 587ea2e into main Jun 24, 2026
14 of 15 checks passed
@os-zhuang
os-zhuang deleted the docs/readme-drop-metrics branch June 24, 2026 16:20
os-zhuang added a commit that referenced this pull request Jul 10, 2026
…ain CI) (#2726)

* chore: bump objectui to 7a68d78f2a0c

chore: release packages (#2304)

objectui@7a68d78f2a0c3c1f99dafd39b75b4f117a24917b

* fix(spec): bump PROTOCOL_VERSION 12.0.0 → 13.0.0 to match spec major (lockstep)

The version-packages roll (#2720) took @objectstack/spec to major 13.0.0 but
left PROTOCOL_VERSION at 12.0.0, so protocol-version.test.ts — the lockstep
guard asserting the protocol major equals the package major — failed on main,
reddening Test Core for every open PR. Restore the lockstep so the
loader/installer handshake advertises the major the package actually ships.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
os-zhuang added a commit that referenced this pull request Jul 10, 2026
… (#2725)

* chore: bump objectui to 7a68d78f2a0c

chore: release packages (#2304)

objectui@7a68d78f2a0c3c1f99dafd39b75b4f117a24917b

* fix(runtime): resolve session identity for action body ctx.user (#2701)

The POST /actions/:object/:action route called handleActions directly,
bypassing dispatch() → resolveExecutionContext. The action body sandbox's
ctx.user was therefore hard-coded to { id: 'system' }, so handlers could not
branch on the operator's identity/roles or enforce server-side ownership.

- dispatcher-plugin: action routes now dispatch through dispatch() (like the
  automation/AI routes), resolving the session identity + per-project kernel
  per request before the action body runs.
- http-dispatcher: handleActions builds ctx.user from the request's
  ExecutionContext (id, email, positions/roles, permissions, tenantId),
  matching the MCP runAction and record-change trigger paths; falls back to a
  system principal only for a genuinely anonymous / self-invoked call.
- Tests: 4 regression cases incl. an end-to-end api-key → dispatch → action
  pipeline asserting the principal reaches ctx.user (verified red without the fix).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
os-zhuang added a commit that referenced this pull request Jul 10, 2026
…rmission sets (#2705) (#2740)

* chore: bump objectui to 7a68d78f2a0c

chore: release packages (#2304)

objectui@7a68d78f2a0c3c1f99dafd39b75b4f117a24917b

* fix(cli,plugin-security): os meta resync to re-materialize default permission sets (#2705)

Default permission sets (admin_full_access / member_default / viewer_readonly …)
were seeded INSERT-ONCE at boot: bootstrapPlatformAdmin skipped any existing row
and never wrote the shipped declaration back. So editing a default set's source,
recompiling, and restarting `os dev` WITHOUT `--fresh` left the runtime serving
the OLD value — silently, because the runtime authz resolver hydrates permission
sets from the sys_permission_set row (resolve-authz-context.ts), not from the
in-memory dist. Every OTHER metadata seed (declared sets, positions, built-in
roles, capabilities) already upserts on boot, leaving the platform-default path
the lone insert-once holdout — a gap ADR-0090 widened by persisting more facets
(system_permissions, delegated-admin admin_scope) onto the same row.

Insert-once is deliberate for prod (it protects an admin's Setup edits and keeps
the defaults env-authored), so this is NOT a blind upsert:

- bootstrapPlatformAdmin gains a `resync` option. Default boot behavior is
  unchanged. Under resync an existing row is reconciled to the shipped dist only
  when the platform still owns it (managed_by absent or 'platform'); a row an
  admin took over ('user') or a package owns ('package') is left untouched.
- New `os meta resync` command boots the runtime, reconciles the default
  permission-set rows to the compiled dist, and reports reconciled / preserved /
  newly-seeded — without touching business data and without a `--fresh` wipe.
  Confirmation-gated (--yes to skip; --json for scripting).

Verified: plugin-security 240/240, cli 466/466, and end-to-end `os meta resync`
against examples/app-todo — insert path (seeded 4 new), overwrite path
(resynced 4), and clean process exit.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant