Configurable branch prefix
The pipeline hardcodes `feature/` as the branch prefix across ~36 source and template references. Any team using a different branch convention (`dev/`, `task/`, `issue/`, bare slugs) gets broken pipeline status, incorrect validation warnings, and wrong agent instructions on first use. The user wants `branchPrefix` in `ana.json` so the prefix is configured once and read everywhere.
verdict UNKNOWNscore 0 / 22findings 0 (0 risk · 0 debt · 0 obs)duration 51mrejection cycles 0shipped Apr 24, 2026surface cli
Pipeline timeline
Intent to proven code in 51m across Think, Plan, Build, and Verify.
Think11m
Plan11m
Build34m
Verify5m
Assertion ledger
22 claims, each independently verified. Showing 8 — show all →
| ID | Says | Matcher | |
|---|---|---|---|
| A001 | Fresh installs include a branch prefix setting in the config file | verified | fail |
| A002 | Re-initializing preserves a user-modified branch prefix | verified | fail |
| A003 | The config reader returns the configured prefix when present | verified | fail |
| A004 | Older installs without a prefix setting get the default automatically | verified | fail |
| A005 | A missing config file does not crash the prefix reader | verified | fail |
| A006 | Teams using bare branch names can set an empty prefix | verified | fail |
| A007 | The schema recovers gracefully from a corrupted prefix value | verified | fail |
| A008 | Pipeline status commands show the configured prefix in branch instructions | verified | fail |
Findings 0 total
Integrity seal
scopesha256:c7e8a5d4ce215...
contractsha256:a8c31f91bfa46...
plansha256:2a6bbe0bac81b...
specsha256:84011701c7cf9...
build-reportsha256:dce786d2ad737...
verify-reportsha256:736f143ab0630...
audit cmd$ ana proof audit configurable-branch-prefix → all hashes match