Issue Tracking

Issue Tracking

Authoritative rule: agents/rules/issue-tracking.md

TL;DR

Open an ai-task issue on noetl/ai-meta for any work that will outlive the current session. Two-tier model:

1. Umbrella issue lives on noetl/ai-meta. Goal, acceptance criteria, pointers, audit trail. Labels: ai-task + repo:<primary-submodule>.
2. Per-round sub-issues live in the owning submodule when a PR is about to ship. PR's body uses GitHub's Closes <repo>#<NN> keyword for auto-close.

When to open

• Inline (no issue): typo, one-line doc tweak, missing comma.
• Chip-spawn (no issue): well-scoped one-shot task this session dispatches now.
• Issue (this convention): anything that will outlive this session, needs human decision, is blocked, or might be picked up by another agent.

When in doubt: open the issue. One gh command, durable record.

Recipe

gh issue create --repo noetl/ai-meta \
  --title "<imperative action phrase under 70 chars>" \
  --label ai-task --label repo:<primary-submodule> \
  --body "$(cat <<'EOF'
## Context
<one paragraph; how this surfaced>

## Goal
<bulleted acceptance criteria>

## Pointers
<file paths with line numbers, error fingerprints>

## Blocked on / depends on
<GitHub auto-link syntax>

## Status
- YYYY-MM-DD: filed; no work started.
EOF
)"

Or use the slash command in any session: /issue-open "<title>" "<repo>".

How umbrellas appear here

Every umbrella opened gets a corresponding wiki page at Umbrella-<topic>.md linked from Home and the sidebar. Read the relevant umbrella page for the full state of the work — issue body holds the spec, umbrella page holds the running narrative.

See Wiki Convention for the cross-link discipline.