agent-issues 0.0.119 → 0.0.121

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (18) hide show
  1. package/dist/open-storage-driver.d.ts +2 -0
  2. package/dist/open-storage-driver.js +3 -1
  3. package/dist/open-storage-driver.js.map +1 -1
  4. package/dist/site/cloud-events-relay.d.ts +2 -4
  5. package/dist/site/cloud-events-relay.js.map +1 -1
  6. package/dist/site/server.js +319 -7
  7. package/dist/site/server.js.map +1 -1
  8. package/dist/skill-installer.js +9 -3
  9. package/dist/skill-installer.js.map +1 -1
  10. package/package.json +1 -1
  11. package/site/dist/assets/index-Cx-fLU3e.js +4496 -0
  12. package/site/dist/index.html +1 -1
  13. package/skills/agent-issues-operating-contract.md +1 -1
  14. package/skills/{ai-wayfinder → ai-pioneer}/SKILL.md +9 -9
  15. package/skills/recipes/README.md +2 -2
  16. package/skills/recipes/{wayfinder-map.md → pioneer-map.md} +2 -2
  17. package/skills/recipes/{wayfinder-ticket.md → pioneer-ticket.md} +2 -2
  18. package/site/dist/assets/index-DSR4mIml.js +0 -4396
package/site/dist/index.html CHANGED
@@ -5,7 +5,7 @@
5
5
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6
6
  <title>agent-issues viewer</title>
7
7
  <style>#app { min-height: 100vh; }</style>
8
- <script type="module" crossorigin src="/assets/index-DSR4mIml.js"></script>
8
+ <script type="module" crossorigin src="/assets/index-Cx-fLU3e.js"></script>
9
9
  <link rel="stylesheet" crossorigin href="/assets/index-DKEVC0aQ.css">
10
10
  </head>
11
11
  <body>
package/skills/agent-issues-operating-contract.md CHANGED
@@ -173,7 +173,7 @@ These operations have no MCP equivalent. Use the CLI: `install-mcp`, `list-mcp`,
173
173
 
174
174
  Before you create or replace authored body content, identify the record type and read its matching recipe in [`recipes`](./recipes/README.md).
175
175
 
176
- - When the catalog has a recipe for the record type, use that recipe for the body. This applies to context summaries, context terms, entities, handoffs, issue comments, and Wayfinder records.
176
+ - When the catalog has a recipe for the record type, use that recipe for the body. This applies to context summaries, context terms, entities, handoffs, issue comments, and Pioneer records.
177
177
  - Do this before the **Entity Create And Edit** recipe, **Context Write** recipe, **Plan Entry Write** recipe, **Issue Comment Write** recipe, or **Handoff Write** recipe creates or replaces a body.
178
178
  - Tracker actions that do not create or replace a body do not need a recipe.
179
179
 
package/skills/{ai-wayfinder → ai-pioneer}/SKILL.md RENAMED
@@ -1,5 +1,5 @@
1
1
  ---
2
- name: ai-wayfinder
2
+ name: ai-pioneer
3
3
  description: Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
4
4
  disable-model-invocation: true
5
5
  ---
@@ -7,13 +7,13 @@ disable-model-invocation: true
7
7
  Follow the shared [language standard](../agent-issues-language.md).
8
8
  Follow the shared [skill operating contract](../agent-issues-operating-contract.md).
9
9
 
10
- A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a **shared map** in `agent-issues`, then works its **decision tickets** — questions whose resolution is a decision, not slices of a build to execute — one at a time until the route is clear.
10
+ A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Pioneering is about finding that way, not charging at the destination. This skill charts the way as a **shared map** in `agent-issues`, then works its **decision tickets** — questions whose resolution is a decision, not slices of a build to execute — one at a time until the route is clear.
11
11
 
12
12
  The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
13
13
 
14
14
  ## Plan, don't do
15
15
 
16
- Wayfinder is **planning** by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its **Notes** — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
16
+ Pioneer is **planning** by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its **Notes** — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
17
17
 
18
18
  ## Refer by title
19
19
 
@@ -25,17 +25,17 @@ The map is a single `agent-issues` issue under the active initiative — the can
25
25
 
26
26
  The map is an **index**, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links.
27
27
 
28
- Use `agent-issues` as the source of truth. Run the **Entity Create And Edit** recipe to create the map as a `wayfinder-map` issue under the initiative and each ticket as a `wayfinder-ticket` child of the map. Run the **Entity Relations** recipe to add dependencies after creation with `blocks` relations.
28
+ Use `agent-issues` as the source of truth. Run the **Entity Create And Edit** recipe to create the map as a `pioneer-map` issue under the initiative and each ticket as a `pioneer-ticket` child of the map. Run the **Entity Relations** recipe to add dependencies after creation with `blocks` relations.
29
29
 
30
30
  ### The map body
31
31
 
32
32
  The whole map at low resolution, loaded once per session. Open tickets are **not** listed — run the **Entity List** recipe for child issues under the map when needed.
33
- Use the [Wayfinder Map recipe](../recipes/wayfinder-map.md). It preserves the current map format.
33
+ Use the [Pioneer Map recipe](../recipes/pioneer-map.md). It preserves the current map format.
34
34
 
35
35
  ### Tickets
36
36
 
37
37
  Each ticket is a **child issue** of the map. Its body contains one question, sized to one 100K token agent session:
38
- Use the [Wayfinder Ticket recipe](../recipes/wayfinder-ticket.md). It preserves the current ticket format.
38
+ Use the [Pioneer Ticket recipe](../recipes/pioneer-ticket.md). It preserves the current ticket format.
39
39
 
40
40
  The `## Ticket type` value is one of `research`, `prototype`, `grilling`, or `task`; see Ticket Types below.
41
41
 
@@ -49,7 +49,7 @@ Run the **Entity Create And Edit** recipe to record the answer in `## Resolution
49
49
 
50
50
  For a grilling ticket, give `ai-plan` the complete ticket reference. It runs the **Entity Create And Edit** recipe to create an initiative-owned Plan for a new effort, or resumes only an explicit Plan reference. Every Plan entry from that session uses the **Plan Entry Write** recipe to link back to the ticket reference.
51
51
 
52
- The Plan is the canonical detailed resolution. When the ticket is done, retain its Question and status, and use a concise Resolution link to the Plan. Do not copy the detailed reasoning into the ticket. A Plan does not inform a Wayfinder map.
52
+ The Plan is the canonical detailed resolution. When the ticket is done, retain its Question and status, and use a concise Resolution link to the Plan. Do not copy the detailed reasoning into the ticket. A Plan does not inform a Pioneer map.
53
53
 
54
54
  ## Ticket Types
55
55
 
@@ -92,8 +92,8 @@ User invokes with a loose idea.
92
92
  1. **Resolve the tracked scope.** Run the **Entity Read** recipe and the **Context Read** recipe to find the active initiative and read its context. For a new feature, run the **Entity Create And Edit** recipe to create a new initiative by default. Do not create a map outside an initiative.
93
93
  2. **Name the destination.** Run `ai-plan` with `ai-domain-modeling` active to pin down what this map is finding its way to — the spec, decision, or change. The destination fixes the scope, so settle it first.
94
94
  3. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surface the open decisions and the first steps that are possible now. **If this finds no fog** — the way to the destination is already clear and small enough for one session — do not create a map. Ask the user how to proceed.
95
- 4. **Create the map** as a `wayfinder-map` child issue of the initiative: Destination and Notes filled in, Decisions-so-far empty, and the fog recorded in **Not yet specified**.
96
- 5. **Create the tickets you can specify now** as `wayfinder-ticket` child issues of the map. Then wire `blocks` relations in a second pass, because issues need references before they can link to each other. This separates the frontier from blocked tickets. Keep everything you cannot yet specify in **Not yet specified**.
95
+ 4. **Create the map** as a `pioneer-map` child issue of the initiative: Destination and Notes filled in, Decisions-so-far empty, and the fog recorded in **Not yet specified**.
96
+ 5. **Create the tickets you can specify now** as `pioneer-ticket` child issues of the map. Then wire `blocks` relations in a second pass, because issues need references before they can link to each other. This separates the frontier from blocked tickets. Keep everything you cannot yet specify in **Not yet specified**.
97
97
  6. **Start research subagents.** For each new `research` ticket, start a read-only research subagent. It returns its findings to the current agent, which records the resolution and updates the ticket. Do not create a branch unless the research needs a prototype or another tracked artifact.
98
98
  7. Stop — charting is one session's work; it does not resolve a HITL ticket.
99
99
 
package/skills/recipes/README.md CHANGED
@@ -25,5 +25,5 @@ Use the recipe for the record that you create or edit.
25
25
  - [ADR](./adr.md)
26
26
  - [Handoff](./handoff.md)
27
27
  - [Issue Comment](./issue-comment.md)
28
- - [Wayfinder Map](./wayfinder-map.md)
29
- - [Wayfinder Ticket](./wayfinder-ticket.md)
28
+ - [Pioneer Map](./pioneer-map.md)
29
+ - [Pioneer Ticket](./pioneer-ticket.md)
package/skills/recipes/{wayfinder-map.md → pioneer-map.md} RENAMED
@@ -1,6 +1,6 @@
1
- # Wayfinder Map Recipe
1
+ # Pioneer Map Recipe
2
2
 
3
- Use this recipe for the canonical Wayfinder issue under an initiative. It is an index for the route to a destination and has child decision tickets.
3
+ Use this recipe for the canonical Pioneer issue under an initiative. It is an index for the route to a destination and has child decision tickets.
4
4
 
5
5
  ```markdown
6
6
  ## Destination
package/skills/recipes/{wayfinder-ticket.md → pioneer-ticket.md} RENAMED
@@ -1,6 +1,6 @@
1
- # Wayfinder Ticket Recipe
1
+ # Pioneer Ticket Recipe
2
2
 
3
- Use this recipe for a child issue of a Wayfinder map. A ticket resolves one decision or investigation.
3
+ Use this recipe for a child issue of a Pioneer map. A ticket resolves one decision or investigation.
4
4
 
5
5
  ```markdown
6
6
  ## Ticket type