Create a minimal local PocketContext Hello World project. Use synthetic demo data only.

1. Check this computer is supported: Linux amd64/arm64, or macOS 15+ on Apple Silicon. You need curl, tar and sha256sum or shasum. If something is missing, explain it rather than claiming success.

2. First check whether PocketContext is already installed at "$HOME/.local/bin/pocketcontext". Inspect its version and preserve existing applications; do not replace a running server's executable. If installation is needed and safe, run:
   curl -fsSL https://pocketcontext.com/pocketcontext/install.sh | sh
   Verify it with "$HOME/.local/bin/pocketcontext" --version.

3. Create ./hello-pocketcontext without overwriting existing files. If that directory already exists, use a new sibling directory. Keep application configuration, migrations, credentials and data inside the project. Exclude pb_data, credentials, tokens and logs from Git. Use private permissions for credential files; never print passwords or tokens.

4. Create a pb_migrations migration for a base collection named messages, with a required text field named message. Require authentication for all messages record operations. Use the existing default users auth collection, not a new agents collection. Keep user signup locked; provision the demo user administratively.

5. Add pocketcontext.json:
   {
     "authCollection": "users",
     "tables": { "messages": ["id", "message"] }
   }
   This minimal example uses shared-workspace SQL: authenticated users can read the configured messages. It does not provide per-user private records.

6. From the project directory, apply migrations and start PocketContext on 127.0.0.1:8090. Pass --dir ./pb_data to every server command and use the installed executable by absolute path. If the port is occupied, choose another free loopback port; do not stop another application. Do not expose the server publicly or create cloud resources.

7. Bootstrap a local superuser with a generated password using the server's superuser command. Authenticate it through the standard REST API, create one demo account in users, then discard the superuser token. Keep administrative credentials separate from the demo user's credentials. Use the ordinary demo user for all subsequent record writes and SQL reads.

8. Authenticate the demo user, then:
   - Create a record containing "Hello, world!" through POST /api/collections/messages/records.
   - Discover the allowed columns through GET /api/context/schema.
   - Read the record through POST /api/context/query with:
     SELECT id, message FROM messages
   - Verify that SQL without authentication is rejected.
   - Verify that an attempted SQL write is rejected.
   - Restart this project's server and verify the saved message is still returned.
   Never use direct SQLite edits to create application records.

9. Write a short README with the exact setup, start, stop and demonstration commands. Finish by showing the project files, running server address and successful Hello World query result, without credentials. Report any failed checks honestly.

Keep this a small local API example, without a frontend or AI model inside the server. Do not run real imports or connect external accounts. Once Hello World works, ask what I want to automate next.