tegwick
d60175c354
Retarget INTENT, SCOPE, README, ROADMAP, and agent docs from "task landing zone" to external-tracker connector per work-record canon and architecture draft §4.2. Add UUID↔external-id mapping design; mark ISSUE-WP-0004 finished and cross-file activity-core ACTIVITY-WP-0022 for IssueSink policy.
33 lines
2.5 KiB
Markdown
33 lines
2.5 KiB
Markdown
# Work Records — issue-core
|
|
|
|
> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
|
|
> stage 3). Do not edit by hand — edit the source file/block listed for
|
|
> each record and re-run fix-consistency to refresh this index. Archived
|
|
> workplans are omitted; closed decisions/intakes/engagements stay listed
|
|
> so recently-resolved work is still visible. [auto]
|
|
|
|
| Kind | ID | Status | Lane | Source |
|
|
| --- | --- | --- | --- | --- |
|
|
| workplan | ISSC-WP-0001 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
|
|
| 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 |
|
|
| 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 |
|
|
| task | T04 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
|
|
| task | T05 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
|
|
| task | T06 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
|
|
| task | ISSUE-WP-0002-T01 | done | — | workplans/ISSUE-WP-0002-gitea-pypi-publication.md |
|
|
| task | ISSUE-WP-0003-T01 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T02 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T03 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T04 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T05 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T06 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0003-T07 | done | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
|
|
| task | ISSUE-WP-0004-T01 | done | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md |
|
|
| task | ISSUE-WP-0004-T02 | done | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md |
|
|
| 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 |
|