Skip to content

batch 6b/6: factory-level docs absorb — 20 docs/*.md updates #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AceHack merged 1 commit into from
Apr 21, 2026
Merged

batch 6b/6: factory-level docs absorb — 20 docs/*.md updates #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions docs/AGENT-ISSUE-WORKFLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,6 @@ picked at setup time:
## Adapter choices (adopter picks at setup)

### (1) GitHub Issues

- Pros: free, integrated with PRs, good label / milestone
tooling, `gh` CLI scriptable, Claude Code `github` plugin
provides MCP access.
Expand All @@ -43,7 +42,6 @@ picked at setup time:
See "Zeta-specific: GitHub Issues configuration" below.

### (2) Jira (or any ticketing SaaS — Linear, Asana, Shortcut)

- Pros: richer workflow states, cross-repo visibility,
enterprise SSO.
- Requirements: agent access via MCP (Anthropic provides
Expand All @@ -56,7 +54,6 @@ picked at setup time:
transfers 1:1.

### (3) Git-native only

- Pros: zero external dependency, fully offline, perfect for
private / air-gapped work.
- Requirements: none beyond git.
Expand All @@ -69,7 +66,6 @@ picked at setup time:
visible to parallel agents running `git log docs/BACKLOG.md`.

### Choosing at setup

The canonical setup script under `tools/setup/` currently does
not prompt for this. A **BACKLOG row is open** to add the
prompt: "Which issue tracker will this project use?
Expand All @@ -90,7 +86,6 @@ adapters; only the mechanism differs:
| Git-native | Short commit touching the row: `BACKLOG: claim row #42 — session <id> <UTC-ts>` | Commit touching the row: `BACKLOG: release row #42 — landed in <SHA>` | `git log --grep="claim row" docs/BACKLOG.md` |

### Claim windows and stale-claim force-release

- A claim is considered **active** for 24 hours.
- After 24 hours of inactivity (no release, no
progress-signal comment / commit), a claim is **stale**.
Expand Down
Loading
Loading