diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index 8925230..e13b94a 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -12,6 +12,7 @@ | workplan | ISSUE-WP-0002 | finished | — | workplans/ISSUE-WP-0002-gitea-pypi-publication.md | | workplan | ISSUE-WP-0003 | finished | — | workplans/ISSUE-WP-0003-railiance01-deployment.md | | workplan | ISSUE-WP-0004 | finished | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md | +| workplan | ISSUE-WP-0005 | proposed | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | | task | T01 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md | | task | T02 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md | | task | T03 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md | @@ -31,3 +32,12 @@ | task | ISSUE-WP-0004-T03 | done | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md | | task | ISSUE-WP-0004-T04 | done | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md | | task | ISSUE-WP-0004-T05 | done | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md | +| task | ISSUE-WP-0005-T01 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T02 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T03 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T04 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T05 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T06 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T07 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T08 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | +| task | ISSUE-WP-0005-T09 | todo | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md | diff --git a/workplans/ISSUE-WP-0005-connector-alignment-implementation.md b/workplans/ISSUE-WP-0005-connector-alignment-implementation.md index cf2ee15..1ee6a58 100644 --- a/workplans/ISSUE-WP-0005-connector-alignment-implementation.md +++ b/workplans/ISSUE-WP-0005-connector-alignment-implementation.md @@ -9,6 +9,7 @@ owner: codex topic_slug: infotech created: "2026-07-22" updated: "2026-07-22" +state_hub_workstream_id: "22167b3c-0707-4c24-8407-58c4bd8b8f75" --- # Implement connector alignment: mapping, docs hygiene, scope gaps vs refined INTENT @@ -67,6 +68,7 @@ without turning issue-core back into a work origin or fleet task board. id: ISSUE-WP-0005-T01 status: todo priority: high +state_hub_task_id: "f538d48e-11b1-4859-9f39-a1103b90c05b" ``` Ensure INTENT, SCOPE, README “See also”, and the alignment review all point at @@ -83,6 +85,7 @@ done; no reintroduction of landing-zone language in those files. id: ISSUE-WP-0005-T02 status: todo priority: medium +state_hub_task_id: "53889021-53ed-4f98-a144-f7c211a58def" ``` Align packaging/metadata with connector intent (not “authoritative task @@ -104,6 +107,7 @@ capability summary matches SCOPE §1 honesty. id: ISSUE-WP-0005-T03 status: todo priority: high +state_hub_task_id: "d2fa5a3c-12ef-4a75-a8c9-b7843d507396" ``` Turn INTENT’s boundary-sync discipline into an implementable policy doc under @@ -127,6 +131,7 @@ policy. id: ISSUE-WP-0005-T04 status: todo priority: high +state_hub_task_id: "a8f0d528-1b1f-4dfb-8df0-9c9ffd56e47c" ``` Per `docs/uuid-external-id-mapping.md`: @@ -149,6 +154,7 @@ note until CLI/API land. id: ISSUE-WP-0005-T05 status: todo priority: high +state_hub_task_id: "1866bec4-e4df-444c-b633-aa97c83c0940" ``` Ship operator surface: @@ -171,6 +177,7 @@ backend; idempotent re-project returns existing mapping. id: ISSUE-WP-0005-T06 status: todo priority: medium +state_hub_task_id: "8e02509b-d304-45d9-b99b-1016dc325cfd" ``` - Add optional `work_record_uuid` (and optional `work_record_id` / @@ -190,6 +197,7 @@ uses it. id: ISSUE-WP-0005-T07 status: todo priority: medium +state_hub_task_id: "5bea7ad1-3df5-4cf3-b79a-e89ac7ad5af1" ``` Implement **outward-only** application of T03 rules for mapped records @@ -209,6 +217,7 @@ SCOPE distinguishes backend sync vs work-record boundary sync clearly. id: ISSUE-WP-0005-T08 status: todo priority: medium +state_hub_task_id: "ca55014a-694d-4a46-beea-cb1f2f438ada" ``` After T04–T07, rewrite SCOPE §1 / §1.8 / §2 so shipped vs target matches @@ -224,6 +233,7 @@ leakage into “shipped today.” id: ISSUE-WP-0005-T09 status: todo priority: low +state_hub_task_id: "fe209013-d9de-4709-bc58-41abe186959d" ``` - Confirm ACTIVITY-WP-0022 still covers default sink policy