bvandeusenandClaude Opus 5 2e39dca9cf fix(tasks): import minted_kind by name — a stubbed service must not stub the guard (#3129) ...

CI 4682: test_create_task_issue_sets_kind_provenance_and_systems asserted
task_kind == "issue" and got a MagicMock. That test patches the whole
notes_svc module to keep the database out, so reaching validation through
`notes_svc.minted_kind(...)` handed back a mock — the guard approved
anything and returned nothing real.

The product was wrong, not the test. minted_kind is pure validation, not a
service call, so it is imported by name. A test that stubs the service to
avoid I/O now keeps the guard intact, which is the behaviour you want from
a guard: the only way to disable it should be to say so explicitly.

That test now exercises the real validation, so it doubles as the guard
against this recurring.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-27 15:57:06 -04:00

..

tools

fix(tasks): import minted_kind by name — a stubbed service must not stub the guard (#3129)

2026-08-27 15:57:06 -04:00

__init__.py

refactor: rename package fabledassistant -> scribe (code-only)

2026-06-03 15:48:35 -04:00

_context.py

refactor: rename package fabledassistant -> scribe (code-only)

2026-06-03 15:48:35 -04:00

auth.py

refactor(mcp): one rules_payload() for every surface that hands rules to an agent; drop the dead bearer resolver (#2828, milestone 296 area 4)

2026-08-21 11:20:36 -04:00

server.py

feat(systems): the area vocabulary becomes a global table so a rule can point at one (#3027, milestone 307 step 1)

2026-08-26 12:31:18 -04:00