coulomb/adaptive-pricing
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
adaptive-pricing/workplans/ADHOC-2026-07-02.md

43 lines
1.2 KiB
Markdown
Raw Normal View History

Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
---
fix(workplans): qualify ad-hoc identifiers with the repository prefix `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
2026-08-28 00:28:19 +02:00
id: ADAPTIVE-WP-ADHOC-2026-07-02
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
type: workplan
Restore pytest execution and stabilize tests
2026-07-02 21:34:44 +02:00
title: "Ad hoc repo maintenance - 2026-07-02"
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
domain: financials
repo: adaptive-pricing
status: finished
owner: codex
topic_slug: helix-forge
created: "2026-07-02"
updated: "2026-07-02"
Review remaining ceiling work and record contract blockers Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76a-f84c-7fb2-8309-fdbddf620a43
2026-09-28 11:51:44 +02:00
state_hub_workstream_id: "e7b3e090-f9a7-5a54-8108-406c71df78ac"
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
---
Restore pytest execution and stabilize tests
2026-07-02 21:34:44 +02:00
# Ad hoc repo maintenance - 2026-07-02
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
## Normalize Repo Metadata And Status Docs
```task
fix(workplans): qualify ad-hoc identifiers with the repository prefix `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
2026-08-28 00:28:19 +02:00
id: ADAPTIVE-WP-ADHOC-2026-07-02-T01
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
status: done
priority: medium
repo.work.assign_missing_identifiers source: repo-manager reason: deterministic projection registration Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76a-f84c-7fb2-8309-fdbddf620a43
2026-09-28 11:54:07 +02:00
state_hub_task_id: "50667b16-49a0-5c7a-9376-cdfde2c22cc0"
Normalize repo metadata and sync docs
2026-07-02 10:21:02 +02:00
```
Align repo-managed metadata with the primary `financials` classification while
keeping the State Hub topic mapping explicit (`helix-forge`). Refresh stale
root status text and fill the remaining Claude rule placeholders with the
actual repo architecture, workflow, and boundary notes.
Restore pytest execution and stabilize tests
2026-07-02 21:34:44 +02:00
## Restore Pytest Execution And Repair Regressions
```task
fix(workplans): qualify ad-hoc identifiers with the repository prefix `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
2026-08-28 00:28:19 +02:00
id: ADAPTIVE-WP-ADHOC-2026-07-02-T02
Restore pytest execution and stabilize tests
2026-07-02 21:34:44 +02:00
status: done
priority: medium
repo.work.assign_missing_identifiers source: repo-manager reason: deterministic projection registration Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e76a-f84c-7fb2-8309-fdbddf620a43
2026-09-28 11:54:07 +02:00
state_hub_task_id: "b448874b-7e4a-5852-8d96-fee561b6787d"
Restore pytest execution and stabilize tests
2026-07-02 21:34:44 +02:00
```
Make `python3 -m pytest` available in the current environment, run the Coulomb
test suite, and repair any regressions or environment-sensitive tests needed to
restore a green test run.
Reference in a new issue Copy permalink