`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.
Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.
The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
1.3 KiB
1.3 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| QONTO-WP-ADHOC-2026-07-21 | workplan | Post-Phase-1 cleanup and local smoke support | infotech | qonto-assistant | finished | codex | the-custodian | 2026-07-21 | 2026-07-21 |
Post-Phase-1 cleanup and local smoke support
Low-risk follow-up after QONTO-WP-0002 completion:
- add fixture-backed local Qonto source so the service can run without real bank credentials
- add a real HTTP smoke script around the Phase 1 REST surface
- add repo classification metadata so
fix-consistencyno longer warns about the missing file
Task: Fixture-backed local smoke mode
id: QONTO-WP-ADHOC-2026-07-21-T01
status: done
priority: medium
Add a local fixture-backed Qonto client path and a smoke script that starts the
service against canned organization/transaction payloads, then verifies
/v1/health, /v1/accounts, and /v1/snapshot.
Done when: the service can be run locally without real Qonto credentials and a documented smoke path exists.
Task: Repo classification metadata
id: QONTO-WP-ADHOC-2026-07-21-T02
status: done
priority: low
Add .repo-classification.yaml for qonto-assistant so State Hub consistency
checks no longer warn about the missing classification file.
Done when: fix-consistency reports no classification-gap warning for this repo.