issue-flow 0.4.4.post3__tar.gz → 0.4.5__tar.gz

{issue_flow-0.4.4.post3 → issue_flow-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: issue-flow
-Version: 0.4.4.post3
+Version: 0.4.5
 Summary: Agents should behave. Let them follow the issue flow.
 Keywords: cursor,ai,agents,issue-tracking,workflow
 Author: jepegit
@@ -57,7 +57,7 @@ your-project/
     05-epics/               # Staged epic plans (epic<N>_plan.md)
   .cursor/
     skills/                  # Agent Skills (/iflow, /iflow-pick, /iflow-init,
-                             # /iflow-plan, /iflow-start, /iflow-close, ...)
+                             # /iflow-plan, /iflow-build, /iflow-close, ...)
     rules/
       issueflow-rules.mdc    # Always-on Cursor rule for the workflow
   AGENTS.md                  # Workflow rules (managed block; shared by all editors)
@@ -71,7 +71,7 @@ The Cursor Agent Skills give agents a repeatable flow and appear in the slash me
 
 1. `/iflow-init 42` or `iflow init 42` — pulls GitHub issue #42 into `.issueflows/01-current-issues/` and archives older issues.
 2. `iflow plan` or `/iflow-plan` — drafts `issue<N>_plan.md` (Goal / Constraints / Approach / Files to touch / Test strategy / Open questions) and stops for your confirmation.
-3. `/iflow-start` — reads the confirmed plan and implements it. If no plan file exists, it offers to run `/iflow-plan` first, proceed without a plan, or abort.
+3. `/iflow-build` — reads the confirmed plan and implements it. If no plan file exists, it offers to run `/iflow-plan` first, proceed without a plan, or abort.
 4. `/iflow-close` — runs tests, optionally bumps version with `uv version --bump`, appends a `HISTORY.md` entry (or promotes `[Unreleased]` to a new release section on a bump), updates status files, commits, pushes, and opens a PR.
 5. `/iflow-cleanup` — after the PR merges, switches to the default branch, fast-forwards, prunes, and deletes the merged local branch.
 
@@ -80,12 +80,19 @@ Plus a few off-path commands:
 - `/iflow-pick` — **front door**: when you haven't chosen an issue yet, it helps pick one (parked work in `02-partly-solved-issues/` first, else open GitHub issues ranked by milestone, labels, and similarity to recently solved work), creates the `<N>-slug` branch, and runs `/iflow-init`. Pass `fix` to create a new general-fixes issue. Off-path; never auto-dispatched.
 - `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically. A branch-derived number (`42-fix-login` → `N=42`) is authoritative, so `/iflow` works from a fresh branch too.
 - `/iflow-pause` — park the current issue in `02-partly-solved-issues/` with a **Remaining work** note; optional WIP commit + switch back to the default branch.
-- `/iflow-yolo` — all-in-one chain (`init → plan → start → close`) for small, low-risk issues, with up-front safeguards (refuses on the default branch, refuses with dirty unrelated changes, requires passing tests, single consolidated confirm).
+- `/iflow-yolo` — all-in-one chain (`init → plan → build → close`) for small, low-risk issues, with up-front safeguards (refuses on the default branch, refuses with dirty unrelated changes, requires passing tests, single consolidated confirm).
 - `/iflow-fix` — interactive iterative-fixes session: creates one GitHub issue + long-lived branch, then loops over many small fixes (each gets a short plan, implemented only on confirmation and recorded in `issue<N>_status.md`), ending with `/iflow-close`. Coexists with `/iflow-pick fix` (the one-shot setup). Off-path; never auto-dispatched.
+- `/iflow-issue` — create **one well-specified normal GitHub issue** (context / spec / acceptance criteria), then optionally branch + `/iflow-init` into the standard lifecycle. Use `/iflow-issue epic …` for an epic anchor. Off-path; never auto-dispatched.
 - `/iflow-status` — **read-only** overview of where every issue stands: the local tracking state (focus / parked / solved) plus open GitHub issues cross-referenced against it. Pass `local` to skip the GitHub query. Changes nothing; off-path; never auto-dispatched.
+- `/iflow-epic` — plan a change too large for one issue as staged specs under `.issueflows/05-epics/`; `publish` creates a confirmed stage's GitHub issues behind one confirm. Off-path; never auto-dispatched.
+- `/iflow-cycle` — batch-process a queue of yolo-fit issues under one up-front confirm (`yolo` / `label:<L>` / numbers / `epic <N>`). Off-path; never auto-dispatched.
+- `/iflow-review` — review open GitHub issues and apply workflow labels (v1: the configured `yolo` label) behind one consolidated confirm. Off-path; never auto-dispatched.
+- `/iflow-doctor` — scaffold health check (missing skills/commands, stale config). Off-path; never auto-dispatched.
 - `/iflow-archive` — **condense the solved archive (destructive, gated)**: summarises selected `issue<N>_*` groups under `03-solved-issues/` into a dated `YYYY-MM-DD_archived_issues.md` file. The summary records the pre-archive git ref so every original file stays recoverable (`git show <ref>:<path>`). Deletes the source files only after one consolidated confirm. Default: archive all but the **5 most recent** solved groups; pass `keep <K>`, an explicit list of issue numbers, or `all`. Requires a **clean working tree**. Off-path; never auto-dispatched.
 
-The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-plan`, `/iflow-start`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-status`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
+See the [docs](https://issue-flow.readthedocs.io/) for worked recipes (review → cycle, epic publish, cycle queues).
+
+The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-plan`, `/iflow-build`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-issue`, `/iflow-status`, `/iflow-epic`, `/iflow-cycle`, `/iflow-review`, `/iflow-doctor`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
 
 ## Prerequisites
 
@@ -162,7 +169,7 @@ loads `.env` from the project root before invoking graphify — or export it in
 your shell environment. Cursor's own LLM is not available to subprocesses, so
 graphify needs its own backend. Other subcommands (`watch`, `cluster-only`, …)
 pass through too; trailing flags forward verbatim.
-- The scaffolded rules and `/iflow-start` mention `graphify-out/GRAPH_REPORT.md`
+- The scaffolded rules and `/iflow-build` mention `graphify-out/GRAPH_REPORT.md`
 as a recommended pre-read when the file exists. `/iflow-graphify` is **off-path** —
 `/iflow` never auto-dispatches to it.
 
@@ -217,7 +224,7 @@ That's it. Open the project in Cursor and start with `/iflow` — or step throug
 
 1. `/iflow-init 42` — pulls GitHub issue #42 into `.issueflows/01-current-issues/` and archives older issues.
 2. `/iflow-plan` — drafts `issue<N>_plan.md` (Goal / Constraints / Approach / Files to touch / Test strategy / Open questions) and stops for your confirmation.
-3. `/iflow-start` — reads the confirmed plan and implements it.
+3. `/iflow-build` — reads the confirmed plan and implements it.
 4. `/iflow-close` — runs tests, optionally bumps version, appends a `HISTORY.md` entry, updates status files, commits, pushes, and opens a PR.
 5. `/iflow-cleanup` — after the PR merges, switches to the default branch, fast-forwards, prunes, and deletes the merged local branch.
 
@@ -226,11 +233,19 @@ Plus a few off-path commands (never auto-dispatched):
 - `/iflow-pick` — **front door**: helps pick the next issue (parked work first, else open GitHub issues ranked by milestone, labels, and similarity to recent work), creates the branch, and runs `/iflow-init`.
 - `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically (a branch-derived number like `42-fix-login` is authoritative).
 - `/iflow-pause` — park the current issue with a **Remaining work** note.
-- `/iflow-yolo` — all-in-one chain (`init → plan → start → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
+- `/iflow-yolo` — all-in-one chain (`init → plan → build → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
 - `/iflow-fix` — interactive iterative-fixes session: one GitHub issue + long-lived branch, many small confirmed fixes.
+- `/iflow-issue` — create one well-specified normal GitHub issue; optional branch + `/iflow-init`.
 - `/iflow-status` — **read-only** overview of where every issue stands, locally and on GitHub.
+- `/iflow-epic` — staged epic plan + publish; decomposes into normal single-issue work.
+- `/iflow-cycle` — batch yolo queue (`yolo` / `label:<L>` / numbers / epic).
+- `/iflow-review` — propose and apply workflow labels on open issues (v1: `yolo`).
+- `/iflow-doctor` — scaffold health check.
 - `/iflow-archive` — condense old solved-issue files into a dated summary (destructive, gated behind one consolidated confirm; originals stay recoverable via git).
 
+Docs cover epics, cycles, and reviews with examples:
+https://issue-flow.readthedocs.io/
+
 ## CLI overview
 
 ```
@@ -275,12 +290,75 @@ See [docs/developing.md](https://github.com/jepegit/issue-flow/blob/main/docs/de
 
 See [HISTORY.md](https://github.com/jepegit/issue-flow/blob/main/HISTORY.md) for release notes.
 
+## GitHub Actions sync
+
+Sync `.issueflows/` folder placement (`01-current-issues` / `02-partly-solved-issues` /
+`03-solved-issues`) to GitHub issue labels (one-way: files → GitHub).
+
+**CLI (local or CI):**
+
+```bash
+issue-flow sync              # dry-run (shows planned label changes)
+issue-flow sync --apply      # push labels via gh
+issue-flow sync --json       # machine-readable report
+```
+
+**Managed labels** (default prefix `status:`): `status:current`, `status:parked`,
+`status:solved`. Only labels with that prefix are added/removed; other labels
+(e.g. `yolo`) are left alone.
+
+**Bootstrap labels once** (if they do not exist yet):
+
+```bash
+gh label create 'status:current' --color 0E8A16
+gh label create 'status:parked' --color FBCA04
+gh label create 'status:solved' --color 6E7781
+```
+
+By default, `issue-flow sync --apply` **auto-creates** any missing managed labels
+(`bootstrap_labels = true` in `[issueflow.sync]`). Set `bootstrap_labels = false`
+to keep the manual-only behaviour.
+
+**Configuration** — optional `[issueflow.sync]` in `.issueflows/config.toml`:
+
+```toml
+[issueflow.sync]
+enabled = true
+label_prefix = "status:"
+labels = true
+milestones = false
+close_on_solved = false
+bootstrap_labels = true
+
+[issueflow.sync.milestone_map]
+current = ""
+parked = ""
+solved = ""
+```
+
+**Reusable workflow** — add a caller in your repo (pin to a release tag):
+
+```yaml
+on:
+  push:
+    paths: ['.issueflows/**']
+jobs:
+  sync:
+    uses: jepegit/issue-flow/.github/workflows/issue-flow-sync.yml@v0.4.4
+    with:
+      dry_run: false
+    secrets: inherit
+```
+
+Requires `permissions: issues: write` on the job. The workflow installs
+`issue-flow` from PyPI by default (`install_mode: pypi`); this repo dogfoods
+with `install_mode: workspace` via [`.github/workflows/issueflow-sync.yml`](.github/workflows/issueflow-sync.yml).
+
 ## Future plans
 
 - **More editors** — extend `--editor` coverage to further AI coding tools (e.g. Windsurf) on top of the current Cursor / Claude Code / opencode / Codex support.
 - **Custom templates** — let users supply their own Jinja2 templates to tailor slash commands and rules to their team's conventions.
 - **Git hook integration** — optionally move issue files on commit based on status markers.
-- **GitHub Actions workflow** — ship a reusable action that syncs issue state between `.issueflows/` and GitHub issue labels/milestones.
 
 ## Acknowledgements
 

{issue_flow-0.4.4.post3 → issue_flow-0.4.5}/README.md

@@ -30,7 +30,7 @@ your-project/
     05-epics/               # Staged epic plans (epic<N>_plan.md)
   .cursor/
     skills/                  # Agent Skills (/iflow, /iflow-pick, /iflow-init,
-                             # /iflow-plan, /iflow-start, /iflow-close, ...)
+                             # /iflow-plan, /iflow-build, /iflow-close, ...)
     rules/
       issueflow-rules.mdc    # Always-on Cursor rule for the workflow
   AGENTS.md                  # Workflow rules (managed block; shared by all editors)
@@ -44,7 +44,7 @@ The Cursor Agent Skills give agents a repeatable flow and appear in the slash me
 
 1. `/iflow-init 42` or `iflow init 42` — pulls GitHub issue #42 into `.issueflows/01-current-issues/` and archives older issues.
 2. `iflow plan` or `/iflow-plan` — drafts `issue<N>_plan.md` (Goal / Constraints / Approach / Files to touch / Test strategy / Open questions) and stops for your confirmation.
-3. `/iflow-start` — reads the confirmed plan and implements it. If no plan file exists, it offers to run `/iflow-plan` first, proceed without a plan, or abort.
+3. `/iflow-build` — reads the confirmed plan and implements it. If no plan file exists, it offers to run `/iflow-plan` first, proceed without a plan, or abort.
 4. `/iflow-close` — runs tests, optionally bumps version with `uv version --bump`, appends a `HISTORY.md` entry (or promotes `[Unreleased]` to a new release section on a bump), updates status files, commits, pushes, and opens a PR.
 5. `/iflow-cleanup` — after the PR merges, switches to the default branch, fast-forwards, prunes, and deletes the merged local branch.
 
@@ -53,12 +53,19 @@ Plus a few off-path commands:
 - `/iflow-pick` — **front door**: when you haven't chosen an issue yet, it helps pick one (parked work in `02-partly-solved-issues/` first, else open GitHub issues ranked by milestone, labels, and similarity to recently solved work), creates the `<N>-slug` branch, and runs `/iflow-init`. Pass `fix` to create a new general-fixes issue. Off-path; never auto-dispatched.
 - `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically. A branch-derived number (`42-fix-login` → `N=42`) is authoritative, so `/iflow` works from a fresh branch too.
 - `/iflow-pause` — park the current issue in `02-partly-solved-issues/` with a **Remaining work** note; optional WIP commit + switch back to the default branch.
-- `/iflow-yolo` — all-in-one chain (`init → plan → start → close`) for small, low-risk issues, with up-front safeguards (refuses on the default branch, refuses with dirty unrelated changes, requires passing tests, single consolidated confirm).
+- `/iflow-yolo` — all-in-one chain (`init → plan → build → close`) for small, low-risk issues, with up-front safeguards (refuses on the default branch, refuses with dirty unrelated changes, requires passing tests, single consolidated confirm).
 - `/iflow-fix` — interactive iterative-fixes session: creates one GitHub issue + long-lived branch, then loops over many small fixes (each gets a short plan, implemented only on confirmation and recorded in `issue<N>_status.md`), ending with `/iflow-close`. Coexists with `/iflow-pick fix` (the one-shot setup). Off-path; never auto-dispatched.
+- `/iflow-issue` — create **one well-specified normal GitHub issue** (context / spec / acceptance criteria), then optionally branch + `/iflow-init` into the standard lifecycle. Use `/iflow-issue epic …` for an epic anchor. Off-path; never auto-dispatched.
 - `/iflow-status` — **read-only** overview of where every issue stands: the local tracking state (focus / parked / solved) plus open GitHub issues cross-referenced against it. Pass `local` to skip the GitHub query. Changes nothing; off-path; never auto-dispatched.
+- `/iflow-epic` — plan a change too large for one issue as staged specs under `.issueflows/05-epics/`; `publish` creates a confirmed stage's GitHub issues behind one confirm. Off-path; never auto-dispatched.
+- `/iflow-cycle` — batch-process a queue of yolo-fit issues under one up-front confirm (`yolo` / `label:<L>` / numbers / `epic <N>`). Off-path; never auto-dispatched.
+- `/iflow-review` — review open GitHub issues and apply workflow labels (v1: the configured `yolo` label) behind one consolidated confirm. Off-path; never auto-dispatched.
+- `/iflow-doctor` — scaffold health check (missing skills/commands, stale config). Off-path; never auto-dispatched.
 - `/iflow-archive` — **condense the solved archive (destructive, gated)**: summarises selected `issue<N>_*` groups under `03-solved-issues/` into a dated `YYYY-MM-DD_archived_issues.md` file. The summary records the pre-archive git ref so every original file stays recoverable (`git show <ref>:<path>`). Deletes the source files only after one consolidated confirm. Default: archive all but the **5 most recent** solved groups; pass `keep <K>`, an explicit list of issue numbers, or `all`. Requires a **clean working tree**. Off-path; never auto-dispatched.
 
-The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-plan`, `/iflow-start`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-status`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
+See the [docs](https://issue-flow.readthedocs.io/) for worked recipes (review → cycle, epic publish, cycle queues).
+
+The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-plan`, `/iflow-build`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-issue`, `/iflow-status`, `/iflow-epic`, `/iflow-cycle`, `/iflow-review`, `/iflow-doctor`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
 
 ## Prerequisites
 
@@ -135,7 +142,7 @@ loads `.env` from the project root before invoking graphify — or export it in
 your shell environment. Cursor's own LLM is not available to subprocesses, so
 graphify needs its own backend. Other subcommands (`watch`, `cluster-only`, …)
 pass through too; trailing flags forward verbatim.
-- The scaffolded rules and `/iflow-start` mention `graphify-out/GRAPH_REPORT.md`
+- The scaffolded rules and `/iflow-build` mention `graphify-out/GRAPH_REPORT.md`
 as a recommended pre-read when the file exists. `/iflow-graphify` is **off-path** —
 `/iflow` never auto-dispatches to it.
 
@@ -190,7 +197,7 @@ That's it. Open the project in Cursor and start with `/iflow` — or step throug
 
 1. `/iflow-init 42` — pulls GitHub issue #42 into `.issueflows/01-current-issues/` and archives older issues.
 2. `/iflow-plan` — drafts `issue<N>_plan.md` (Goal / Constraints / Approach / Files to touch / Test strategy / Open questions) and stops for your confirmation.
-3. `/iflow-start` — reads the confirmed plan and implements it.
+3. `/iflow-build` — reads the confirmed plan and implements it.
 4. `/iflow-close` — runs tests, optionally bumps version, appends a `HISTORY.md` entry, updates status files, commits, pushes, and opens a PR.
 5. `/iflow-cleanup` — after the PR merges, switches to the default branch, fast-forwards, prunes, and deletes the merged local branch.
 
@@ -199,11 +206,19 @@ Plus a few off-path commands (never auto-dispatched):
 - `/iflow-pick` — **front door**: helps pick the next issue (parked work first, else open GitHub issues ranked by milestone, labels, and similarity to recent work), creates the branch, and runs `/iflow-init`.
 - `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically (a branch-derived number like `42-fix-login` is authoritative).
 - `/iflow-pause` — park the current issue with a **Remaining work** note.
-- `/iflow-yolo` — all-in-one chain (`init → plan → start → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
+- `/iflow-yolo` — all-in-one chain (`init → plan → build → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
 - `/iflow-fix` — interactive iterative-fixes session: one GitHub issue + long-lived branch, many small confirmed fixes.
+- `/iflow-issue` — create one well-specified normal GitHub issue; optional branch + `/iflow-init`.
 - `/iflow-status` — **read-only** overview of where every issue stands, locally and on GitHub.
+- `/iflow-epic` — staged epic plan + publish; decomposes into normal single-issue work.
+- `/iflow-cycle` — batch yolo queue (`yolo` / `label:<L>` / numbers / epic).
+- `/iflow-review` — propose and apply workflow labels on open issues (v1: `yolo`).
+- `/iflow-doctor` — scaffold health check.
 - `/iflow-archive` — condense old solved-issue files into a dated summary (destructive, gated behind one consolidated confirm; originals stay recoverable via git).
 
+Docs cover epics, cycles, and reviews with examples:
+https://issue-flow.readthedocs.io/
+
 ## CLI overview
 
 ```
@@ -248,12 +263,75 @@ See [docs/developing.md](https://github.com/jepegit/issue-flow/blob/main/docs/de
 
 See [HISTORY.md](https://github.com/jepegit/issue-flow/blob/main/HISTORY.md) for release notes.
 
+## GitHub Actions sync
+
+Sync `.issueflows/` folder placement (`01-current-issues` / `02-partly-solved-issues` /
+`03-solved-issues`) to GitHub issue labels (one-way: files → GitHub).
+
+**CLI (local or CI):**
+
+```bash
+issue-flow sync              # dry-run (shows planned label changes)
+issue-flow sync --apply      # push labels via gh
+issue-flow sync --json       # machine-readable report
+```
+
+**Managed labels** (default prefix `status:`): `status:current`, `status:parked`,
+`status:solved`. Only labels with that prefix are added/removed; other labels
+(e.g. `yolo`) are left alone.
+
+**Bootstrap labels once** (if they do not exist yet):
+
+```bash
+gh label create 'status:current' --color 0E8A16
+gh label create 'status:parked' --color FBCA04
+gh label create 'status:solved' --color 6E7781
+```
+
+By default, `issue-flow sync --apply` **auto-creates** any missing managed labels
+(`bootstrap_labels = true` in `[issueflow.sync]`). Set `bootstrap_labels = false`
+to keep the manual-only behaviour.
+
+**Configuration** — optional `[issueflow.sync]` in `.issueflows/config.toml`:
+
+```toml
+[issueflow.sync]
+enabled = true
+label_prefix = "status:"
+labels = true
+milestones = false
+close_on_solved = false
+bootstrap_labels = true
+
+[issueflow.sync.milestone_map]
+current = ""
+parked = ""
+solved = ""
+```
+
+**Reusable workflow** — add a caller in your repo (pin to a release tag):
+
+```yaml
+on:
+  push:
+    paths: ['.issueflows/**']
+jobs:
+  sync:
+    uses: jepegit/issue-flow/.github/workflows/issue-flow-sync.yml@v0.4.4
+    with:
+      dry_run: false
+    secrets: inherit
+```
+
+Requires `permissions: issues: write` on the job. The workflow installs
+`issue-flow` from PyPI by default (`install_mode: pypi`); this repo dogfoods
+with `install_mode: workspace` via [`.github/workflows/issueflow-sync.yml`](.github/workflows/issueflow-sync.yml).
+
 ## Future plans
 
 - **More editors** — extend `--editor` coverage to further AI coding tools (e.g. Windsurf) on top of the current Cursor / Claude Code / opencode / Codex support.
 - **Custom templates** — let users supply their own Jinja2 templates to tailor slash commands and rules to their team's conventions.
 - **Git hook integration** — optionally move issue files on commit based on status markers.
-- **GitHub Actions workflow** — ship a reusable action that syncs issue state between `.issueflows/` and GitHub issue labels/milestones.
 
 ## Acknowledgements
 

{issue_flow-0.4.4.post3 → issue_flow-0.4.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "issue-flow"
-version = "0.4.4.post3"
+version = "0.4.5"
 description = "Agents should behave. Let them follow the issue flow."
 readme = "README.md"
 license = "MIT"