@spec-wave/cli 1.7.6 → 1.8.0
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.
- package/README.md +1 -1
- package/package.json +1 -1
- package/src/agent/errors.mjs +31 -1
- package/src/agent/openrouter-agent.mjs +25 -2
- package/src/api/github-graphql.mjs +31 -0
- package/src/api/github-rest.mjs +20 -0
- package/src/cli.mjs +93 -36
- package/src/commands/auth-check.mjs +72 -0
- package/src/commands/decompose.mjs +14 -2
- package/src/commands/doctor.mjs +139 -2
- package/src/commands/generate-bug.mjs +6 -6
- package/src/commands/generate-plan.mjs +9 -8
- package/src/commands/generate-qa-plan.mjs +9 -6
- package/src/commands/generate-spec.mjs +12 -7
- package/src/commands/init.mjs +2 -2
- package/src/commands/preflight.mjs +38 -2
- package/src/commands/relink.mjs +105 -0
- package/src/commands/report-failure.mjs +99 -0
- package/src/commands/retry.mjs +91 -0
- package/src/commands/update.mjs +70 -0
- package/src/config.mjs +8 -8
- package/src/lib/cited-paths.mjs +89 -0
- package/src/lib/claude.mjs +4 -2
- package/src/lib/cli-line.mjs +153 -0
- package/src/lib/cli-ref.mjs +53 -2
- package/src/lib/failure-report.mjs +319 -0
- package/src/lib/repo-identity.mjs +55 -0
- package/src/lib/spec-index.mjs +114 -0
- package/src/lib/tech-context.mjs +144 -5
- package/src/plugin/.claude-plugin/plugin.json +1 -1
- package/src/plugin/skills/plan/SKILL.md +1 -1
- package/src/plugin/skills/plan/reference/tech-context.md +12 -4
- package/src/plugin/skills/setup/SKILL.md +1 -1
- package/src/plugin/skills/spec/model-prompt.md +8 -1
- package/src/plugins/scm-github/index.mjs +8 -1
- package/src/plugins/tracker-github-projects/index.mjs +11 -4
- package/src/ports/tracker.mjs +2 -1
- package/src/setup/labels.mjs +5 -3
- package/src/setup/project.mjs +5 -3
- package/src/templates/config/tech_context.yml +29 -25
- package/src/templates/skill/SKILL.md +27 -9
- package/src/templates/skill/core.md +25 -7
- package/src/templates/workflows/code-review.yml +1 -0
- package/src/templates/workflows/critique.yml +11 -0
- package/src/templates/workflows/decompose.yml +27 -0
- package/src/templates/workflows/generate-bug.yml +26 -0
- package/src/templates/workflows/generate-plan.yml +26 -0
- package/src/templates/workflows/generate-qa-plan.yml +27 -0
- package/src/templates/workflows/generate-spec.yml +26 -0
- package/src/templates/workflows/pr-events.yml +5 -0
- package/src/templates/workflows/qa.yml +1 -0
- package/src/templates/workflows/validate.yml +11 -0
|
@@ -67,6 +67,19 @@ jobs:
|
|
|
67
67
|
app-id: ${{ secrets.SPEC_WAVE_APP_ID }}
|
|
68
68
|
private-key: ${{ secrets.SPEC_WAVE_APP_PRIVATE_KEY }}
|
|
69
69
|
|
|
70
|
+
# Testa as credenciais DE VERDADE antes de qualquer trabalho: lê a issue
|
|
71
|
+
# com o token deste passo e o Project com o PROJECT_TOKEN. O doctor só vê
|
|
72
|
+
# o NOME dos secrets; um PAT expirado só aparecia como 401 no meio do run,
|
|
73
|
+
# sem dizer qual. Falhou aqui → o passo report-failure diz qual trocar.
|
|
74
|
+
- name: Verifica as credenciais
|
|
75
|
+
run: spec-wave auth check --issue ${{ github.event.issue.number }}
|
|
76
|
+
env:
|
|
77
|
+
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
78
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
79
|
+
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
80
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
81
|
+
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
82
|
+
|
|
70
83
|
# Multi-repo (RFC-005 §7.2): clona em .spec-wave/repos/<slug>/ os repos
|
|
71
84
|
# de código que a issue declara (labels repo:<slug>; a Feature agrega as
|
|
72
85
|
# Stories), para o modelo ler CÓDIGO e não só o markdown do hub. Sem repo
|
|
@@ -76,6 +89,7 @@ jobs:
|
|
|
76
89
|
run: spec-wave workspace prepare --issue ${{ github.event.issue.number }}
|
|
77
90
|
env:
|
|
78
91
|
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
92
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
79
93
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
80
94
|
|
|
81
95
|
- name: Generate QA plan
|
|
@@ -83,8 +97,21 @@ jobs:
|
|
|
83
97
|
env:
|
|
84
98
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
85
99
|
GH_PR_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PR_TOKEN }}
|
|
100
|
+
SPEC_WAVE_PR_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PR_TOKEN' }}
|
|
86
101
|
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
102
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
87
103
|
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
88
104
|
CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
|
|
89
105
|
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
|
|
90
106
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
107
|
+
|
|
108
|
+
# A falha chega à issue: causa classificada (auth, max_turns, provider…),
|
|
109
|
+
# qual secret trocar e o próximo passo. Quando o próprio comando já
|
|
110
|
+
# comentou, o registro em $RUNNER_TEMP diz isso e nada se repete. Também
|
|
111
|
+
# remove a label de gatilho — com ela aplicada, reaplicá-la não dispara.
|
|
112
|
+
- name: Reporta a falha na issue
|
|
113
|
+
if: failure()
|
|
114
|
+
run: spec-wave report-failure --issue ${{ github.event.issue.number }} --label "${{ github.event.label.name }}" --step generate-qa-plan
|
|
115
|
+
env:
|
|
116
|
+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
117
|
+
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
@@ -90,6 +90,19 @@ jobs:
|
|
|
90
90
|
app-id: ${{ secrets.SPEC_WAVE_APP_ID }}
|
|
91
91
|
private-key: ${{ secrets.SPEC_WAVE_APP_PRIVATE_KEY }}
|
|
92
92
|
|
|
93
|
+
# Testa as credenciais DE VERDADE antes de qualquer trabalho: lê a issue
|
|
94
|
+
# com o token deste passo e o Project com o PROJECT_TOKEN. O doctor só vê
|
|
95
|
+
# o NOME dos secrets; um PAT expirado só aparecia como 401 no meio do run,
|
|
96
|
+
# sem dizer qual. Falhou aqui → o passo report-failure diz qual trocar.
|
|
97
|
+
- name: Verifica as credenciais
|
|
98
|
+
run: spec-wave auth check --issue ${{ github.event.issue.number }}
|
|
99
|
+
env:
|
|
100
|
+
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
101
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
102
|
+
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
103
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
104
|
+
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
105
|
+
|
|
93
106
|
# Multi-repo (RFC-005 §7.2): clona em .spec-wave/repos/<slug>/ os repos
|
|
94
107
|
# de código que a issue declara (labels repo:<slug>; a Feature agrega as
|
|
95
108
|
# Stories), para o modelo ler CÓDIGO e não só o markdown do hub. Sem repo
|
|
@@ -99,6 +112,7 @@ jobs:
|
|
|
99
112
|
run: spec-wave workspace prepare --issue ${{ github.event.issue.number }}
|
|
100
113
|
env:
|
|
101
114
|
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
115
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
102
116
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
103
117
|
|
|
104
118
|
- name: Generate spec.md
|
|
@@ -106,7 +120,19 @@ jobs:
|
|
|
106
120
|
env:
|
|
107
121
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
108
122
|
GH_PR_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PR_TOKEN }}
|
|
123
|
+
SPEC_WAVE_PR_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PR_TOKEN' }}
|
|
109
124
|
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
110
125
|
CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
|
|
111
126
|
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
|
|
112
127
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
128
|
+
|
|
129
|
+
# A falha chega à issue: causa classificada (auth, max_turns, provider…),
|
|
130
|
+
# qual secret trocar e o próximo passo. Quando o próprio comando já
|
|
131
|
+
# comentou, o registro em $RUNNER_TEMP diz isso e nada se repete. Também
|
|
132
|
+
# remove a label de gatilho — com ela aplicada, reaplicá-la não dispara.
|
|
133
|
+
- name: Reporta a falha na issue
|
|
134
|
+
if: failure()
|
|
135
|
+
run: spec-wave report-failure --issue ${{ github.event.issue.number }} --label "${{ github.event.label.name }}" --step generate-spec
|
|
136
|
+
env:
|
|
137
|
+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
138
|
+
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
@@ -68,6 +68,7 @@ jobs:
|
|
|
68
68
|
--resolve-only
|
|
69
69
|
env:
|
|
70
70
|
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
71
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
71
72
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
72
73
|
|
|
73
74
|
move:
|
|
@@ -110,7 +111,9 @@ jobs:
|
|
|
110
111
|
--pr-repo ${{ github.event.client_payload.pr_repo }}
|
|
111
112
|
env:
|
|
112
113
|
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
114
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
113
115
|
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
116
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
114
117
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
115
118
|
|
|
116
119
|
qa:
|
|
@@ -144,5 +147,7 @@ jobs:
|
|
|
144
147
|
--pr-repo ${{ github.event.client_payload.pr_repo }}
|
|
145
148
|
env:
|
|
146
149
|
GITHUB_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN || secrets.GITHUB_TOKEN }}
|
|
150
|
+
SPEC_WAVE_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || secrets.GH_PROJECT_TOKEN && 'GH_PROJECT_TOKEN' || 'GITHUB_TOKEN' }}
|
|
147
151
|
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
152
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
148
153
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
@@ -73,4 +73,5 @@ jobs:
|
|
|
73
73
|
env:
|
|
74
74
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
75
75
|
PROJECT_TOKEN: ${{ steps.app.outputs.token || secrets.GH_PROJECT_TOKEN }}
|
|
76
|
+
SPEC_WAVE_PROJECT_TOKEN_SOURCE: ${{ steps.app.outputs.token && 'GitHub App (SPEC_WAVE_APP_*)' || 'GH_PROJECT_TOKEN' }}
|
|
76
77
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
@@ -52,3 +52,14 @@ jobs:
|
|
|
52
52
|
env:
|
|
53
53
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
54
54
|
GITHUB_REPOSITORY: ${{ github.repository }}
|
|
55
|
+
|
|
56
|
+
# A falha chega à issue: causa classificada (auth, max_turns, provider…),
|
|
57
|
+
# qual secret trocar e o próximo passo. Quando o próprio comando já
|
|
58
|
+
# comentou, o registro em $RUNNER_TEMP diz isso e nada se repete. Também
|
|
59
|
+
# remove a label de gatilho — com ela aplicada, reaplicá-la não dispara.
|
|
60
|
+
- name: Reporta a falha na issue
|
|
61
|
+
if: failure()
|
|
62
|
+
run: spec-wave report-failure --issue ${{ github.event.issue.number }} --label "${{ github.event.label.name }}" --step validate
|
|
63
|
+
env:
|
|
64
|
+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
65
|
+
GITHUB_REPOSITORY: ${{ github.repository }}
|