fixme-tickets-md

Markdown-based ticket tracking stores bugs and tasks as ticket.md files within session folders, using YAML frontmatter to log state transitions and durations for auditability. It organizes assets, research, plans, and verifications to support plan-execute cycles.

Frontmatter-based state management logs task transitions and durations directly in YAML frontmatter. This creates an auditable record of retries and lifecycle changes within the markdown store, ensuring persistent session-scoped state tracking.

Orchestrate plan-execute cycles by generating ticket.md files and organizing per-ticket assets, research, plans, and verifications. This structure supports continuous iteration and local task orchestration throughout the session.

Yes, ticket creation and session management rely on the fixme-tools.cjs CLI. It handles create, transition, and list operations, generating ticket.md files and managing the local file-based ticket store.

Yes, session-scoped ticket tracking provides local, file-based orchestration for bug tracking and task management. It operates per-session, integrating with broader workflows to manage state and transitions locally.

File-based ticket backends operate locally per-session, meaning state and ticket.md files are stored on the local filesystem. This approach lacks centralized database synchronization, relying entirely on local file-based orchestration and YAML frontmatter for state persistence.