da3ce160b4
ci.yml calls `scripts/ci.sh` rather than restating the checks: a workflow that reimplements them becomes a second definition of "done", and the two drift. Android runs as a separate job. It fails when the SDK is absent while ci.sh skips it — a developer should not be blocked by a missing toolchain, but a silently skipped Android build in CI means regressions ship unnoticed. Every action is pinned to an exact version. LICENSE.md records that no licence is chosen yet, and why it is not a formality: the choice is upstream of the UI toolkit decision, since Slint is GPL-3.0. Co-Authored-By: Claude Code <noreply@anthropic.com>
69 lines
2.2 KiB
YAML
69 lines
2.2 KiB
YAML
name: Question
|
|
description: An open decision for the project owner, or something blocking work
|
|
title: ""
|
|
labels: ["question"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
CLAUDE.md section 10.3: any open question becomes an issue labelled
|
|
"question" instead of being buried in a chat thread where it gets lost.
|
|
|
|
Most questions here are ones the agent cannot answer alone — section 0 rule 3
|
|
requires stopping to ask before adding an unlisted dependency, changing the
|
|
architecture, or choosing between two non-obvious OS mechanisms.
|
|
|
|
- type: textarea
|
|
id: question
|
|
attributes:
|
|
label: The question
|
|
description: One question. If there are several, they need separate issues.
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: kind
|
|
attributes:
|
|
label: What kind of decision is this?
|
|
options:
|
|
- Dependency to add (section 0 rule 3)
|
|
- Architecture change (section 0 rule 3)
|
|
- Choice between OS mechanisms (section 0 rule 3)
|
|
- Licensing
|
|
- Scope or priority
|
|
- Something else
|
|
|
|
- type: input
|
|
id: blocks
|
|
attributes:
|
|
label: What does this block?
|
|
description: Which milestone, and what specifically cannot proceed.
|
|
placeholder: "M2-Linux: the KWin backend cannot be written until the block-window approach is chosen."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: options
|
|
attributes:
|
|
label: Options and trade-offs
|
|
description: |
|
|
What are the realistic choices, and what does each cost? Include binary size,
|
|
licence, and maintenance burden where they apply.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: recommendation
|
|
attributes:
|
|
label: Recommendation, if you have one
|
|
description: |
|
|
Optional. A default the agent has been proceeding with, so it can keep working
|
|
while you decide. Say here if you would rather it stop and wait.
|
|
|
|
- type: textarea
|
|
id: research
|
|
attributes:
|
|
label: Supporting research
|
|
description: |
|
|
Measurements, documentation links, or a comparison. Links are more useful than
|
|
conclusions. |