Store stack config as a _config@1 record

[cuibonobo]

Summary

• Removes getConfig/setConfig from StackAdapter — config is no longer a stringly-typed key/value bag on the adapter interface
• Stack-level configuration (ownerEntityId, timezone) is now stored as a singleton _config@1 record in the records table and exposed as typed readonly properties directly on the adapter
• Adapters that previously stored config in a separate mechanism (SQLite's stack_config table, API adapter's internal Map) now populate the properties from their natural source (record query / discovery endpoint)

What changed

@haverstack/core

• StackAdapter gains readonly ownerEntityId: string and readonly timezone: string; getConfig/setConfig removed
• New ConfigContent type and SYSTEM_TYPES.CONFIG ('_config') exported
• Stack.create() reads directly from adapter.ownerEntityId / adapter.timezone
• seedSystemTypes() now seeds the _config@1 type definition
• MemoryAdapter constructor changes from Record<string, string> to { ownerEntityId?, timezone? }

@haverstack/adapter-sqlite

• Config stored as a _config@1 record with id='_config' in the records table; stack_config table removed from schema
• runMigrations() handles existing databases by reading stack_config, writing the record, and dropping the table
• buildWhereClause always excludes the '_config' singleton from app-visible queries

@haverstack/adapter-api

• ownerEntityId and timezone populated from the discovery response and exposed as public properties; getConfig/setConfig removed

Test plan

• pnpm -r test passes (182 core + 75 SQLite + 48 API = 305 tests)
• Existing SQLite databases with stack_config tables are migrated cleanly on next open()
• _config record does not appear in queryRecords results

---

Generated by Claude Code