@davidbyoung/software-factory 0.1.10 → 0.1.11

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.
Files changed (51) hide show
  1. package/agents/factory-ticket-readiness.md +20 -15
  2. package/dist/board.d.mts +1 -1
  3. package/dist/board.mjs +3 -4
  4. package/dist/cli.mjs +17 -4
  5. package/dist/code-host/github.mjs +2 -0
  6. package/dist/code-host/types.d.mts +4 -0
  7. package/dist/commands.d.mts +7 -2
  8. package/dist/commands.mjs +86 -16
  9. package/dist/config.d.mts +3 -4
  10. package/dist/config.mjs +7 -8
  11. package/dist/init.d.mts +11 -0
  12. package/dist/init.mjs +56 -1
  13. package/dist/lib/work-status.d.mts +5 -5
  14. package/dist/lib/work-status.mjs +7 -8
  15. package/dist/merge-policy.mjs +7 -3
  16. package/dist/pr.d.mts +8 -6
  17. package/dist/pr.mjs +39 -22
  18. package/dist/review-verdict.d.mts +22 -4
  19. package/dist/review-verdict.mjs +55 -17
  20. package/dist/specs/index.d.mts +6 -0
  21. package/dist/specs/index.mjs +15 -0
  22. package/dist/specs/openspec.d.mts +2 -0
  23. package/dist/specs/openspec.mjs +78 -0
  24. package/dist/specs/types.d.mts +53 -0
  25. package/dist/specs/types.mjs +4 -0
  26. package/dist/ticket.d.mts +3 -1
  27. package/dist/ticket.mjs +36 -3
  28. package/dist/tickets/github-access.d.mts +5 -0
  29. package/dist/tickets/github-access.mjs +22 -0
  30. package/dist/tickets/github.mjs +2 -0
  31. package/dist/tickets/types.d.mts +4 -0
  32. package/dist/tool-names.d.mts +2 -0
  33. package/dist/tool-names.mjs +3 -0
  34. package/dist/tools.d.mts +2 -0
  35. package/dist/tools.mjs +3 -0
  36. package/docs/builds.md +4 -1
  37. package/docs/cli.md +19 -4
  38. package/docs/configuration.md +50 -38
  39. package/docs/developing.md +104 -59
  40. package/docs/existing-repo.md +4 -3
  41. package/docs/github/setup.md +20 -3
  42. package/docs/glossary.md +7 -6
  43. package/docs/limitations.md +8 -5
  44. package/docs/updating.md +18 -0
  45. package/docs/workflow.md +25 -8
  46. package/package.json +1 -1
  47. package/rules.md +36 -30
  48. package/skills/factory-address-review/SKILL.md +40 -39
  49. package/skills/factory-build/SKILL.md +46 -53
  50. package/skills/factory-refine/SKILL.md +30 -22
  51. package/skills/factory-resolve-conflicts/SKILL.md +8 -7
@@ -11,7 +11,7 @@ Working the review itself, the threads, the checks, the coverage report,
11
11
  the replies, the rounds, and the report, is in the `factory-address-review`
12
12
  skill, as is the run a review of the owner's starts; this one says what a
13
13
  run does before and around that. The section numbers below are
14
- `factory-address-review`'s. The owner's login, which reviews count, and
14
+ `factory-address-review`'s. Who is an approver, whose reviews count, and
15
15
  the `<!-- agent -->` marker are defined in `factory-address-review`
16
16
  section 0a, and where the marker goes in a comment in its section 4.
17
17
 
@@ -79,13 +79,13 @@ in the report.
79
79
  settled it:
80
80
 
81
81
  ```bash
82
- OWNER_LOGIN=$(npx --no-install factory config get repository | cut -d/ -f1)
83
- npx --no-install factory pr comments N --author "$OWNER_LOGIN" \
82
+ npx --no-install factory pr comments N --from-approvers \
84
83
  --contains "conflict-stop head=HEAD_SHA"
85
84
  ```
86
85
 
87
- Agents post through the owner's account (section 0a), so the marker,
88
- not the author, is what makes it a stop comment.
86
+ Agents post through an approver's account, a person's or an agent
87
+ account's (section 0a), so the marker, not who posted it, is what makes
88
+ it a stop comment.
89
89
 
90
90
  4. **Nothing `dirty` without a stop comment:** stop, with no comment, no
91
91
  push. Otherwise go on: the workflow has already run the setup. Before
@@ -187,8 +187,9 @@ Run the gate, `npx --no-install factory gate`. Then, when
187
187
  repository's end-to-end suite covers, which its `CLAUDE.md` names, install
188
188
  what the suite needs, such as a browser, and run the suite as `CLAUDE.md`
189
189
  says, so a missing browser does not read as a failed gate. Run the spec
190
- check, `npx --no-install factory specs check`, when a file under
191
- `openspec/` conflicted.
190
+ check, `npx --no-install factory specs check`, when a file under a
191
+ folder `npx --no-install factory specs list` prints conflicted, or one
192
+ under the spec change it starts.
192
193
 
193
194
  Fix what the merge broke and run the gate once more. A second failure is
194
195
  a stop.