4 Commits

Include renames

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	15d69799bf	Make the config file the only home for settings ... With no production instance yet, there is no reason to carry two ways of configuring the agent. Every environment variable that duplicated a config key is gone; the environment now supplies only the secrets the file references by ${…}, plus NISSE_CONFIG and NISSE_ENV to find the files. - AgentConfig loads from a file (load, from_file) or a parsed tree (from_tree, for tests); a missing file is an error naming the example - The from_env constructors on LiteLLMClient, AnthropicPassthroughClient, GiteaClient, MatrixConfig and RoleMap are removed, with the env reading for max output tokens; clients take their settings from config - The live integration tests share a committed agent config, tests/integration/nisse-test.yaml, aimed at test resources, and one conftest that loads it and builds clients. NISSE_LIVE_PLANNER_MODEL becomes its planner role; NISSE_CAPABILITY_MODELS stays as a per-run switch - A missing secret now fails the live tests instead of skipping them - CI passes only the three tokens - .env.example is secrets only; spec A5 says config comes from the file Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-23 23:25:58 +00:00
dongarandClaude Opus 5	e04d786840	Assert the live Matrix tests run as a testing identity ... Two invariants only a live homeserver can check, now enforced rather than verified by hand: - The configured NISSE_MATRIX_USER_ID must be the token's real owner. MatrixTransport filters its own messages by comparing sender to that value, so a mismatch would make the bot read its own posts as operator input. - The account must be a testing identity, so a stray live run can never act as the production agent. Both hold today; this keeps them holding when the production nisse-dev account is created. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 20:16:18 +00:00
dongarandClaude Opus 5	10aa77899e	Gate live tests on one sentinel var each, fail on partial config ... Skipping now keys solely on NISSE_LLM_BASE_URL and NISSE_MATRIX_HOMESERVER: if the sentinel is set, the live path is expected to work and any other missing variable is an assertion failure naming it, not a silent skip. A misnamed or misplaced CI secret previously produced a green run with no live coverage. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 14:33:14 +00:00
dongarandClaude Fable 5	5db6d9d96e	Add MatrixTransport (A1) — step-2 PR B ... - matrix.py: Transport implementation over the Matrix client-server HTTP API directly (token auth, /sync long-poll, /send) using the existing httpx dependency — no Matrix SDK; four endpoints total. Deviation from the presented plan (matrix-nio) flagged in the PR - First sync learns position and skips backlog, so room history is never delivered as context (A1); own messages and non-message events filtered; sender MXID passed through for the orchestrator's operator allowlist - Sync loop backs off (capped at 60s) and retries indefinitely on homeserver errors, mirroring B2's polling posture - Encrypted rooms unsupported: bot rooms are created unencrypted until E2E lands (operator decision; room recreated accordingly) - NISSE_MATRIX_TEST_ROOM_ID added: the live smoke test binds only to the dedicated test room, never the production room - 8 unit tests over a mocked HTTP layer; live integration test verified against the real homeserver Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-09-06 23:52:45 +00:00