Enforce headless decisions with a versioned migration contract
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start with the implementation and tests for headless decisions, then inspect the plan schema and migration fixtures referenced by the acceptance criteria. The issue depends on #22 and requires an approved schema, compatibility, migration, and SemVer plan before implementation. Done means a missing decision exits non-zero without foreign writes, and an old plan migrates under the approved version.
Written by the indexing model from the issue text.
Description
Goal
Make headless runs fail closed when a decision is missing (no foreign writes), using an approved, explicit migration and compatibility contract; any intentional breaking change requires a versioned schema and SemVer review.
Observations
- A newly required intent conflicts with absolute CLI backward compatibility.
- Any intentional break needs an approved versioned schema, migration, and SemVer decision; a breaking release has not yet been selected.
- Old syntax must not be preserved by bypassing the new gate.
Decision gate
Approve the schema, compatibility, migration, and SemVer plan before implementing any intentional break.
Acceptance criteria
- A missing headless decision performs no writes to foreign resources.
- Any intentional break ships only with an approved versioned schema, migration, and SemVer decision.
- The CLI does not preserve old syntax by bypassing the new gate.
- The failure is explicit with a non-zero exit and a clear reason.
Verification
- Headless run without a decision -> non-zero exit, zero writes.
- Schema migration fixture -> the old plan migrates under the approved version, not by bypass.
Release checkpoint
Remaining risk: any chosen break must be communicated with the reviewed version change.
Tracking
Roadmap item: B04-02. All acceptance criteria remain pending; publication does not grant approval or release authority.
Dependencies
- Depends on #22 (B04-01).
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 3
- Avg merge
- 27m
- Merged PRs (30d)
- 27
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from egdev6/github-repository-bootstrap
-
status:approved type:chore
Difficulty 5/5 Over a week Newbie friendliness 25/100
egdev6/github-repository-bootstrap#57 ·
Maintainers usually reply within 1 day
-
type:docs
Difficulty 1/5 Under an hour Newbie friendliness 20/100
egdev6/github-repository-bootstrap#50 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
egdev6/github-repository-bootstrap#49 ·
Maintainers usually reply within 1 day
-
status:approved type:chore
Difficulty 5/5 Over a week Newbie friendliness 25/100
egdev6/github-repository-bootstrap#30 ·
Maintainers usually reply within 1 day
-
status:approved type:chore
Difficulty 5/5 Over a week Newbie friendliness 42/100
egdev6/github-repository-bootstrap#29 ·
Maintainers usually reply within 1 day
All issues in egdev6/github-repository-bootstrap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 8 days
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunkPossibly taken A pull request linked to this issue is open or already merged. Openfactory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
docs hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
pacocartones/free-llm-api-hub#347 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wpilibsuite/wpilib-docs#3378 ·
Maintainers usually reply within 1 day