@autocode-cli/autocode 0.1.15 → 0.1.17

package/templates/prompts/review-security.fr.md

@@ -17,10 +17,10 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <ticket-key> "Review security OK"`
-10. Avancer : `autocode next <ticket-key>`
+9. Documenter : `autocode comment <issue-key> "Review security OK"`
+10. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/specification.en.md

@@ -2,7 +2,7 @@
 
 ## Role
 
-Write detailed technical specifications for the ticket. Define the implementation approach clearly.
+Write detailed technical specifications for the issue. Define the implementation approach clearly.
 
 ## Actions
 
@@ -15,11 +15,11 @@ Write detailed technical specifications for the ticket. Define the implementatio
 7. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-8. Document: `autocode comment <ticket-key> "Specification complete: <technical approach>"`
-9. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+8. Document: `autocode comment <issue-key> "Specification complete: <technical approach>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/specification.fr.md

@@ -16,10 +16,10 @@ Rediger les specifications techniques detaillees pour le ticket. Definir clairem
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <ticket-key> "Specification terminee : <approche technique>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Specification terminee : <approche technique>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/splitter.en.md

@@ -2,7 +2,7 @@
 
 ## Role
 
-Break down large requirements into smaller, focused tickets **when needed** to limit responsibility and improve traceability. Create atomic tasks that can be independently implemented and verified.
+Break down large requirements into smaller, focused issues **when needed** to limit responsibility and improve traceability. Create atomic tasks that can be independently implemented and verified.
 
 ## When to Split
 
@@ -16,23 +16,23 @@ If the task is small enough to be completed in one go, proceed directly without
 
 1. Analyze the requirement to identify distinct functional components
 2. Identify natural boundaries between features, layers, or responsibilities
-3. Define clear acceptance criteria for each sub-ticket
-4. Ensure each split ticket is independently testable and deployable
-5. Create sub-tickets: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-6. Verify no functionality has been forgotten or duplicated across tickets
-7. Create an integration ticket that references all sub-tickets to validate cohesion
-8. Document: `autocode comment <ticket-key> "[summary]"`
-9. Advance: `autocode next <ticket-key>`
+3. Define clear acceptance criteria for each sub-issue
+4. Ensure each split issue is independently testable and deployable
+5. Create sub-issues: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
+6. Verify no functionality has been forgotten or duplicated across issues
+7. Create an integration issue that references all sub-issues to validate cohesion
+8. Document: `autocode comment <issue-key> "[summary]"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 
-- [ ] All sub-tickets are atomic and independently implementable
+- [ ] All sub-issues are atomic and independently implementable
 - [ ] No functionality from the original requirement has been forgotten
-- [ ] An integration ticket exists to verify all parts work together cohesively
-- [ ] Each sub-ticket has clear acceptance criteria
+- [ ] An integration issue exists to verify all parts work together cohesively
+- [ ] Each sub-issue has clear acceptance criteria
 
 ## Notes
 
-Smaller tickets reduce cognitive load and merge conflicts. Always create an integration ticket to ensure the split parts form a coherent whole.
+Smaller issues reduce cognitive load and merge conflicts. Always create an integration issue to ensure the split parts form a coherent whole.

package/templates/prompts/splitter.fr.md

@@ -21,10 +21,10 @@ Si la tâche est suffisamment petite pour être complétée en une fois, procéd
 5. Créer les sous-tickets : `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
 6. Vérifier qu'aucune fonctionnalité n'a été oubliée ou dupliquée entre les tickets
 7. Créer un ticket d'intégration qui référence tous les sous-tickets pour valider la cohésion
-8. Documenter : `autocode comment <ticket-key> "[résumé]"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "[résumé]"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retourner : `autocode move <ticket-key> <target-column-slug>`
+> Ou retourner : `autocode move <issue-key> <target-column-slug>`
 
 ## Critères de Validation
 

package/templates/prompts/template-validation.en.md

@@ -11,7 +11,7 @@ Verify project templates are correct and functional.
    - Test generation with `autocode init`
 3. Verify generated structure:
    - .autocode/
-   - .autocode/tickets/
+   - .autocode/issues/
    - .autocode/config.yml
    - pipeline.yml
 4. Test different configurations

package/templates/prompts/template-validation.fr.md

@@ -11,7 +11,7 @@ Vérifier que les templates de projet sont corrects et fonctionnels.
    - Tester la génération avec `autocode init`
 3. Vérifier la structure générée:
    - .autocode/
-   - .autocode/tickets/
+   - .autocode/issues/
    - .autocode/config.yml
    - pipeline.yml
 4. Tester différentes configurations

package/templates/prompts/testing-coverage.en.md

@@ -8,7 +8,7 @@ Measure and validate code coverage by unit tests.
 2. Analyze generated coverage report
 3. Identify files with insufficient coverage (<80%)
 4. Check coverage of critical modules:
-   - src/core/ (ticket.ts, column.ts, workflow.ts)
+   - src/core/ (issue.ts, column.ts, workflow.ts)
    - src/server/api.ts
    - src/services/
 5. Add tests for uncovered areas if needed

package/templates/prompts/testing-coverage.fr.md

@@ -8,7 +8,7 @@ Mesurer et valider la couverture de code par les tests unitaires.
 2. Analyser le rapport de couverture généré
 3. Identifier les fichiers avec couverture insuffisante (<80%)
 4. Vérifier la couverture des modules critiques:
-   - src/core/ (ticket.ts, column.ts, workflow.ts)
+   - src/core/ (issue.ts, column.ts, workflow.ts)
    - src/server/api.ts
    - src/services/
 5. Ajouter des tests pour les zones non couvertes si nécessaire

package/templates/prompts/testing-cypress.en.md

@@ -12,11 +12,11 @@ Write AND execute E2E automated tests to prevent regressions.
 4. Describe tests clearly (describe/it)
 5. Execute tests: npx cypress run
 6. If failures: fix tests or code
-7. Do not write tests for code outside the ticket scope
-8. Document: `autocode comment <ticket-key> "Cypress tests OK"`
-9. Advance: `autocode next <ticket-key>`
+7. Do not write tests for code outside the issue scope
+8. Document: `autocode comment <issue-key> "Cypress tests OK"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-cypress.fr.md

@@ -13,10 +13,10 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
 5. Executer les tests : npx cypress run
 6. Si echecs : corriger les tests ou le code
 7. Ne pas ecrire de tests pour du code hors scope du ticket
-8. Documenter : `autocode comment <ticket-key> "Tests Cypress OK"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Tests Cypress OK"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-integration.en.md

@@ -13,11 +13,11 @@ Run integration tests to verify components work correctly together. Ensure syste
 5. Test database operations
 6. Test external service connections
 7. Fix any failing tests
-8. Do not write tests for code outside the ticket scope
-9. Document: `autocode comment <ticket-key> "Integration tests passed"`
-10. Advance: `autocode next <ticket-key>`
+8. Do not write tests for code outside the issue scope
+9. Document: `autocode comment <issue-key> "Integration tests passed"`
+10. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-integration.fr.md

@@ -14,10 +14,10 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
 6. Tester les connexions aux services externes
 7. Corriger les tests en echec
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <ticket-key> "Tests d'integration OK"`
-10. Avancer : `autocode next <ticket-key>`
+9. Documenter : `autocode comment <issue-key> "Tests d'integration OK"`
+10. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-playwright.en.md

@@ -12,11 +12,11 @@ Live functional testing with Playwright. Manually verify feature works by naviga
 4. Test edge cases
 5. Verify error handling
 6. Capture screenshots if needed
-7. Do not test functionality outside the ticket scope
-8. Document: `autocode comment <ticket-key> "Playwright tests OK"`
-9. Advance: `autocode next <ticket-key>`
+7. Do not test functionality outside the issue scope
+8. Document: `autocode comment <issue-key> "Playwright tests OK"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-playwright.fr.md

@@ -13,10 +13,10 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
 5. Verifier la gestion d'erreurs
 6. Capturer des screenshots si necessaire
 7. Ne pas tester de fonctionnalites hors scope du ticket
-8. Documenter : `autocode comment <ticket-key> "Tests Playwright OK"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Tests Playwright OK"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-unit.en.md

@@ -13,11 +13,11 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
 5. Run all unit tests: `npm test` or equivalent
 6. Fix any failing tests
 7. Verify coverage meets project standards
-8. Do not write tests for code outside the ticket scope
-9. Document: `autocode comment <ticket-key> "Unit tests passed: <coverage>%"`
-10. Advance: `autocode next <ticket-key>`
+8. Do not write tests for code outside the issue scope
+9. Document: `autocode comment <issue-key> "Unit tests passed: <coverage>%"`
+10. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-unit.fr.md

@@ -14,10 +14,10 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
 6. Corriger les tests en echec
 7. Verifier que la couverture respecte les standards du projet
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <ticket-key> "Tests unitaires OK : <couverture>%"`
-10. Avancer : `autocode next <ticket-key>`
+9. Documenter : `autocode comment <issue-key> "Tests unitaires OK : <couverture>%"`
+10. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/update-docs.en.md

@@ -11,10 +11,10 @@ Document changes for future developers and users.
 3. Document new features
 4. Update existing guides if impacted
 5. Verify doc consistency
-6. Document: `autocode comment <ticket-key> "Documentation updated"`
-7. Advance: `autocode next <ticket-key>`
+6. Document: `autocode comment <issue-key> "Documentation updated"`
+7. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/update-docs.fr.md

@@ -11,10 +11,10 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
 3. Documenter les nouvelles features
 4. Mettre a jour les guides existants si impactes
 5. Verifier la coherence de la doc
-6. Documenter : `autocode comment <ticket-key> "Documentation mise a jour"`
-7. Avancer : `autocode next <ticket-key>`
+6. Documenter : `autocode comment <issue-key> "Documentation mise a jour"`
+7. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/validate-staging.en.md

@@ -12,10 +12,10 @@ Final validation: verify everything works in staging AND git repo is clean.
 4. Verify visually everything is OK
 5. Capture proof (screenshot)
 6. Confirm feature works
-7. Document: `autocode comment <ticket-key> "Staging validation OK"`
-8. Advance: `autocode next <ticket-key>`
+7. Document: `autocode comment <issue-key> "Staging validation OK"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/validate-staging.fr.md

@@ -12,10 +12,10 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
 4. Verifier visuellement que tout est OK
 5. Capturer une preuve (screenshot)
 6. Confirmer que la feature fonctionne
-7. Documenter : `autocode comment <ticket-key> "Validation staging OK"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Validation staging OK"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/websocket-test.en.md

@@ -7,7 +7,7 @@ Verify WebSocket connection works for real-time updates.
 1. Start server with WebSocket enabled
 2. Connect to WebSocket: `ws://localhost:3456/ws`
 3. Verify connection message received
-4. Create/modify a ticket via API
+4. Create/modify an issue via API
 5. Verify event received via WebSocket
 6. Test automatic reconnection
 7. Check performance with multiple clients

package/dist/core/ticket.d.ts

@@ -1,50 +0,0 @@
-/**
- * Ticket CRUD operations - Multi-file structure
- */
-import type { Ticket, TicketCreateInput, TicketUpdateInput } from '../types/index.js';
-/**
- * Find a ticket directory by its key
- */
-export declare function findTicketDir(rootDir: string, key: string): string | null;
-/**
- * Find a ticket path by its key (for backwards compatibility)
- * @deprecated Use findTicketDir instead
- */
-export declare function findTicketPath(rootDir: string, key: string): string | null;
-/**
- * Get a ticket by its key
- */
-export declare function getTicket(rootDir: string, key: string): Ticket | null;
-/**
- * Create a new ticket
- */
-export declare function createTicket(rootDir: string, input: TicketCreateInput): Ticket;
-/**
- * Update a ticket
- */
-export declare function updateTicket(rootDir: string, key: string, updates: TicketUpdateInput): Ticket | null;
-/**
- * Add a comment to a ticket
- */
-export declare function addComment(rootDir: string, key: string, text: string, column?: string, source?: 'user' | 'claude'): Ticket | null;
-/**
- * Move a ticket to a new column
- */
-export declare function moveTicket(rootDir: string, key: string, toColumnSlug: string, force?: boolean): Ticket | null;
-/**
- * Move a ticket to the next column
- */
-export declare function nextTicket(rootDir: string, key: string): Ticket | null;
-/**
- * List all tickets
- */
-export declare function listTickets(rootDir: string): Ticket[];
-/**
- * List tickets in a specific column
- */
-export declare function listTicketsInColumn(rootDir: string, columnSlug: string): Ticket[];
-/**
- * Find the first actionable ticket (for Claude processing)
- */
-export declare function findActionableTicket(rootDir: string): Ticket | null;
-//# sourceMappingURL=ticket.d.ts.map

package/dist/core/ticket.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ticket.d.ts","sourceRoot":"","sources":["../../src/core/ticket.ts"],"names":[],"mappings":"AAAA;;GAEG;AAuBH,OAAO,KAAK,EAAE,MAAM,EAAE,iBAAiB,EAAE,iBAAiB,EAAY,MAAM,mBAAmB,CAAC;AAEhG;;GAEG;AACH,wBAAgB,aAAa,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAgBzE;AAED;;;GAGG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAI1E;AAED;;GAEG;AACH,wBAAgB,SAAS,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAKrE;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,iBAAiB,GAAG,MAAM,CAiC9E;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,GAAG,MAAM,GAAG,IAAI,CA0BpG;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,EAAE,MAAM,GAAE,MAAM,GAAG,QAAiB,GAAG,MAAM,GAAG,IAAI,CAWzI;AAED;;GAEG;AACH,wBAAgB,UAAU,CACxB,OAAO,EAAE,MAAM,EACf,GAAG,EAAE,MAAM,EACX,YAAY,EAAE,MAAM,EACpB,KAAK,UAAQ,GACZ,MAAM,GAAG,IAAI,CA6Bf;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAWtE;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,EAAE,CAmBrD;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,EAAE,CAgBjF;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAgBnE"}

package/dist/core/ticket.js

@@ -1,224 +0,0 @@
-/**
- * Ticket CRUD operations - Multi-file structure
- */
-import { join, dirname, basename } from 'node:path';
-import { ensureDir, listDirs, pathExists, generateTicketKey, slugify, getTimestamp, moveDir, } from '../utils/fs.js';
-import { loadTicket, updateMetadata, updateDescription, addCommentFile, addHistoryEntry, createTicketStructure, } from '../services/ticket-io.js';
-import { getColumns, getColumnBySlug } from './column.js';
-/**
- * Find a ticket directory by its key
- */
-export function findTicketDir(rootDir, key) {
-    const columns = getColumns();
-    for (const column of columns) {
-        const ticketsDir = join(rootDir, column.slug, 'tickets');
-        if (!pathExists(ticketsDir))
-            continue;
-        const ticketDirs = listDirs(ticketsDir);
-        for (const ticketDir of ticketDirs) {
-            if (ticketDir.startsWith(`${key}__`)) {
-                return join(ticketsDir, ticketDir);
-            }
-        }
-    }
-    return null;
-}
-/**
- * Find a ticket path by its key (for backwards compatibility)
- * @deprecated Use findTicketDir instead
- */
-export function findTicketPath(rootDir, key) {
-    const ticketDir = findTicketDir(rootDir, key);
-    if (!ticketDir)
-        return null;
-    return join(ticketDir, 'metadata.json');
-}
-/**
- * Get a ticket by its key
- */
-export function getTicket(rootDir, key) {
-    const ticketDir = findTicketDir(rootDir, key);
-    if (!ticketDir)
-        return null;
-    return loadTicket(ticketDir);
-}
-/**
- * Create a new ticket
- */
-export function createTicket(rootDir, input) {
-    const key = generateTicketKey(rootDir);
-    const timestamp = getTimestamp();
-    const titleSlug = slugify(input.title);
-    // Default to backlog
-    const column = getColumnBySlug('00_backlog');
-    const ticketDir = join(rootDir, column.slug, 'tickets', `${key}__${titleSlug}`);
-    const metadata = {
-        key,
-        title: input.title,
-        priority: input.priority || 'P2',
-        labels: input.labels || [],
-        acceptance_criteria: input.acceptance_criteria || [],
-        semver: input.semver || 'patch',
-        history: [
-            {
-                at: timestamp,
-                action: 'created',
-                from: null,
-                to: column.slug,
-            },
-        ],
-        created_at: timestamp,
-        updated_at: timestamp,
-    };
-    const description = input.description || '';
-    createTicketStructure(ticketDir, metadata, description);
-    return loadTicket(ticketDir);
-}
-/**
- * Update a ticket
- */
-export function updateTicket(rootDir, key, updates) {
-    const ticketDir = findTicketDir(rootDir, key);
-    if (!ticketDir)
-        return null;
-    const ticket = loadTicket(ticketDir);
-    if (!ticket)
-        return null;
-    // Build metadata updates
-    const metadataUpdates = {};
-    if (updates.title !== undefined)
-        metadataUpdates.title = updates.title;
-    if (updates.priority !== undefined)
-        metadataUpdates.priority = updates.priority;
-    if (updates.labels !== undefined)
-        metadataUpdates.labels = updates.labels;
-    if (updates.acceptance_criteria !== undefined)
-        metadataUpdates.acceptance_criteria = updates.acceptance_criteria;
-    if (updates.semver !== undefined)
-        metadataUpdates.semver = updates.semver;
-    // Update metadata if any changes
-    if (Object.keys(metadataUpdates).length > 0) {
-        updateMetadata(ticketDir, metadataUpdates);
-    }
-    // Update description if changed
-    if (updates.description !== undefined) {
-        updateDescription(ticketDir, updates.description);
-    }
-    return loadTicket(ticketDir);
-}
-/**
- * Add a comment to a ticket
- */
-export function addComment(rootDir, key, text, column, source = 'user') {
-    const ticketDir = findTicketDir(rootDir, key);
-    if (!ticketDir)
-        return null;
-    const ticket = loadTicket(ticketDir);
-    if (!ticket)
-        return null;
-    const commentColumn = column || ticket.status || 'N/A';
-    addCommentFile(ticketDir, text, commentColumn, source);
-    return loadTicket(ticketDir);
-}
-/**
- * Move a ticket to a new column
- */
-export function moveTicket(rootDir, key, toColumnSlug, force = false) {
-    const ticketDir = findTicketDir(rootDir, key);
-    if (!ticketDir)
-        return null;
-    const ticket = loadTicket(ticketDir);
-    if (!ticket)
-        return null;
-    const toColumn = getColumnBySlug(toColumnSlug);
-    if (!toColumn)
-        return null;
-    const fromColumn = getColumnBySlug(ticket.column_slug);
-    if (!fromColumn)
-        return null;
-    // Determine action
-    const action = force ? 'forced' : 'moved';
-    // Add history entry
-    addHistoryEntry(ticketDir, action, fromColumn.slug, toColumn.slug);
-    // Move directory
-    const ticketDirName = basename(ticketDir);
-    const newTicketDir = join(rootDir, toColumn.slug, 'tickets', ticketDirName);
-    if (ticketDir !== newTicketDir) {
-        ensureDir(dirname(newTicketDir));
-        moveDir(ticketDir, newTicketDir);
-    }
-    return loadTicket(newTicketDir);
-}
-/**
- * Move a ticket to the next column
- */
-export function nextTicket(rootDir, key) {
-    const ticket = getTicket(rootDir, key);
-    if (!ticket)
-        return null;
-    const currentColumn = getColumnBySlug(ticket.column_slug);
-    if (!currentColumn)
-        return null;
-    const nextColumn = getColumns().find(c => c.index === currentColumn.index + 1);
-    if (!nextColumn)
-        return null;
-    return moveTicket(rootDir, key, nextColumn.slug);
-}
-/**
- * List all tickets
- */
-export function listTickets(rootDir) {
-    const tickets = [];
-    const columns = getColumns();
-    for (const column of columns) {
-        const ticketsDir = join(rootDir, column.slug, 'tickets');
-        if (!pathExists(ticketsDir))
-            continue;
-        const ticketDirs = listDirs(ticketsDir);
-        for (const ticketDirName of ticketDirs) {
-            const ticketDir = join(ticketsDir, ticketDirName);
-            const ticket = loadTicket(ticketDir);
-            if (ticket) {
-                tickets.push(ticket);
-            }
-        }
-    }
-    return tickets;
-}
-/**
- * List tickets in a specific column
- */
-export function listTicketsInColumn(rootDir, columnSlug) {
-    const ticketsDir = join(rootDir, columnSlug, 'tickets');
-    if (!pathExists(ticketsDir))
-        return [];
-    const tickets = [];
-    const ticketDirs = listDirs(ticketsDir);
-    for (const ticketDirName of ticketDirs) {
-        const ticketDir = join(ticketsDir, ticketDirName);
-        const ticket = loadTicket(ticketDir);
-        if (ticket) {
-            tickets.push(ticket);
-        }
-    }
-    return tickets;
-}
-/**
- * Find the first actionable ticket (for Claude processing)
- */
-export function findActionableTicket(rootDir) {
-    const columns = getColumns();
-    // Skip backlog (0) and done (12)
-    for (const column of columns.slice(1, -1)) {
-        const tickets = listTicketsInColumn(rootDir, column.slug);
-        if (tickets.length > 0) {
-            // Return highest priority ticket
-            return tickets.sort((a, b) => {
-                const priorityOrder = { P0: 0, P1: 1, P2: 2, P3: 3 };
-                return priorityOrder[a.priority] - priorityOrder[b.priority];
-            })[0];
-        }
-    }
-    return null;
-}
-//# sourceMappingURL=ticket.js.map