docs(getting-started): the first-project page lists the starter test and @objectstack/verify

The blank starter now ships note.test.ts, vitest.config.ts and
@objectstack/verify as a devDependency, so the "What was generated" tree
gains the two root files and the package table, which calls itself the
entire framework surface a project installs, gains the verify row.

Claude-Session: https://claude.ai/code/session_01VoSxBQujKLZKPwK2u5ehQ6
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

content/docs/getting-started/your-first-project.mdx

@@ -89,6 +89,8 @@ my-app/
 ├── objectstack.manifest.json    # name, namespace, specVersion
 ├── package.json
 ├── tsconfig.json
+├── note.test.ts                 # the starter test `npm test` runs
+├── vitest.config.ts             # its test-runner config
 ├── AGENTS.md                    # conventions for coding agents
 └── src/
     ├── objects/
@@ -232,6 +234,7 @@ framework surface you install:
 | `@objectstack/plugin-hono-server` | The HTTP server that mounts the generated REST API. |
 | `@objectstack/connector-rest` · `-openapi` · `-mcp` | The three generic connector executors — register the `rest` / `openapi` / `mcp` provider factories so declarative `connectors:` entries materialize ([ADR-0097](/docs/automation/flows)). |
 | `@objectstack/cli` *(dev)* | The `os` / `objectstack` CLI: `dev`, `validate`, `build`, `start`. |
+| `@objectstack/verify` *(dev)* | The test harness: `bootStack` boots this app's own stack in-process, on an in-memory database and with no server port, and returns the handle a test asserts through. `npm test` runs the starter test `note.test.ts` with it. |
 
 No driver package is listed because none is installed directly: `@objectstack/runtime`
 depends on `driver-sql`, `driver-sqlite-wasm` and `driver-memory`, and the CLI carries