refactor: make ARNES external-repo based with ticket publish flow
This commit is contained in:
66
docs/scripts-reference.md
Normal file
66
docs/scripts-reference.md
Normal file
@@ -0,0 +1,66 @@
|
||||
# Scripts reference
|
||||
|
||||
## `./scripts/install_into_repo.sh /path/to/project-repo`
|
||||
Copies ARNES core into a different project repo.
|
||||
|
||||
What it does:
|
||||
- refuses to install into the ARNES source repo itself
|
||||
- initializes git repo at target if missing
|
||||
- copies ARNES core files into target repo
|
||||
|
||||
## `./scripts/start.sh`
|
||||
Interactive bootstrap wizard.
|
||||
|
||||
What it does:
|
||||
- asks project metadata
|
||||
- chooses default app directory (`project/` by default)
|
||||
- writes `harness/project.config.json`
|
||||
- creates `scripts/verify.local.sh`
|
||||
- can seed one bootstrap ticket
|
||||
- resets runtime status
|
||||
|
||||
## `./scripts/verify.sh`
|
||||
Core harness verification.
|
||||
|
||||
What it checks:
|
||||
- required core files exist
|
||||
- project is inside a git repo
|
||||
- warns if no git remote exists
|
||||
- backlog JSON is valid
|
||||
- only one feature is `in_progress`
|
||||
- done features have all required artifacts, including publish evidence
|
||||
- runtime status JSON is valid
|
||||
- optional local overlay runs if present
|
||||
|
||||
## `python3 scripts/new_ticket.py`
|
||||
Interactive ticket creator.
|
||||
|
||||
Writes one new backlog entry with:
|
||||
- `type`
|
||||
- `title`
|
||||
- `problem`
|
||||
- `goal`
|
||||
- `scope_in`
|
||||
- `scope_out`
|
||||
- `priority`
|
||||
- `risk`
|
||||
- `acceptance`
|
||||
|
||||
## `python3 scripts/publish_ticket.py --feature-id F-001`
|
||||
Final publish step for one ticket.
|
||||
|
||||
What it does:
|
||||
- validates git repo, remote, and git identity
|
||||
- writes `work/artifacts/<feature_id>/publish.json`
|
||||
- creates one commit for the ticket
|
||||
- pushes the branch to remote
|
||||
|
||||
## `python3 scripts/agent_status.py`
|
||||
Runtime status helper.
|
||||
|
||||
Commands:
|
||||
- `show`
|
||||
- `set`
|
||||
- `reset`
|
||||
|
||||
The `set` command validates stage and agent names against harness files.
|
||||
Reference in New Issue
Block a user