Implement wayfinding maps and child tickets #21

New Issue

2026-08-17T22:01:08-04:00

steve commented

2026-08-17 22:01:08 -04:00

Part of Provider-neutral tracker automation CLI and library

Parent

Provider-neutral tracker automation CLI and library

What to build

Deliver wayfinding map and child-ticket management. An AI agent can create a canonical map, create typed child issues, and preserve the relationship using native tracker support or the documented fallback conventions.

Acceptance criteria

Map creation applies the wayfinder map label and records the required destination, notes, decisions, fog, and scope sections.
Child creation applies the requested wayfinder type label and links the child to the map.
Native child/sub-issue relationships are used where supported.
Parent-body/task-list or parent-marker fallback metadata is written where native child relationships are unavailable.
Map and child results expose normalized links, numbers, labels, and provider details.
Repeating child relationship setup does not create duplicate relationships where the provider supports idempotent checks.
End-to-end fake-provider tests cover map creation and each wayfinder ticket type.

Blocked by

Part of [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## Parent [Provider-neutral tracker automation CLI and library](http://gitea.sagacity.ca/steve/skills/issues/16) ## What to build Deliver wayfinding map and child-ticket management. An AI agent can create a canonical map, create typed child issues, and preserve the relationship using native tracker support or the documented fallback conventions. ## Acceptance criteria - [ ] Map creation applies the wayfinder map label and records the required destination, notes, decisions, fog, and scope sections. - [ ] Child creation applies the requested wayfinder type label and links the child to the map. - [ ] Native child/sub-issue relationships are used where supported. - [ ] Parent-body/task-list or parent-marker fallback metadata is written where native child relationships are unavailable. - [ ] Map and child results expose normalized links, numbers, labels, and provider details. - [ ] Repeating child relationship setup does not create duplicate relationships where the provider supports idempotent checks. - [ ] End-to-end fake-provider tests cover map creation and each wayfinder ticket type. ## Blocked by - [Implement the issue lifecycle across providers](http://gitea.sagacity.ca/steve/skills/issues/18) - [Implement idempotent labels and assignment](http://gitea.sagacity.ca/steve/skills/issues/19)

steve added the ready-for-agent label 2026-08-17 22:01:08 -04:00

steve referenced this issue

2026-08-17 22:01:08 -04:00

Implement dependencies and frontier queries #22

steve added a new dependency 2026-08-17 22:02:10 -04:00

#18 Implement the issue lifecycle across providers

steve added a new dependency 2026-08-17 22:02:10 -04:00

#19 Implement idempotent labels and assignment

steve added a new dependency 2026-08-17 22:02:10 -04:00

#22 Implement dependencies and frontier queries

Sign in to join this conversation.