@pennyfarthing/core 9.2.0 → 9.3.0

package/pennyfarthing-dist/workflows/ux-design/steps/step-14-complete.md

@@ -1,234 +0,0 @@
-# Step 14: Workflow Completion
-
-<purpose>Complete the UX design workflow, validate the specification, update status tracking, and provide next step guidance to the user.</purpose>
-
-<instructions>Announce workflow completion with all accomplished sections. Update workflow status file with completion information and timestamp. Perform document quality check (completeness, consistency). Suggest next steps (wireframes, prototypes, architecture, Figma design). Provide final completion confirmation with core deliverables list. Set lastStep = 14 in frontmatter. Do NOT load additional steps.</instructions>
-
-<output>Workflow completion announced with comprehensive summary of accomplished sections. Workflow status file updated. Next step options provided to user. UX design specification validated and ready for implementation. Specification location: {planning_artifacts}/ux-design-specification.md with supporting visual assets at {planning_artifacts}/ux-color-themes.html and {planning_artifacts}/ux-design-directions.html.</output>
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ THIS IS A FINAL STEP - Workflow completion required
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- 🛑 NO content generation - this is a wrap-up step
-- 📋 FINALIZE document and update workflow status
-- 💬 FOCUS on completion, validation, and next steps
-- 🎯 UPDATE workflow status files with completion information
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Update the main workflow status file with completion information
-- 📖 Suggest potential next workflow steps for the user
-- 🚫 DO NOT load additional steps after this one
-
-## TERMINATION STEP PROTOCOLS:
-
-- This is a FINAL step - workflow completion required
-- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted to indicate all is finished..
-- Output completion summary and next step guidance
-- Update the main workflow status file with finalized document
-- Suggest potential next workflow steps for the user
-- Mark workflow as complete in status tracking
-
-## CONTEXT BOUNDARIES:
-
-- Complete UX design specification is available from all previous steps
-- Workflow frontmatter shows all completed steps
-- All collaborative content has been generated and saved
-- Focus on completion, validation, and next steps
-
-## YOUR TASK:
-
-Complete the UX design workflow, update status files, and suggest next steps for the project.
-
-## WORKFLOW COMPLETION SEQUENCE:
-
-### 1. Announce Workflow Completion
-
-Inform user that the UX design is complete:
-"🎉 **UX Design Complete, {{user_name}}!**
-
-I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.
-
-**What we've accomplished:**
-
-- ✅ Project understanding and user insights
-- ✅ Core experience and emotional response definition
-- ✅ UX pattern analysis and inspiration
-- ✅ Design system choice and implementation strategy
-- ✅ Core interaction definition and experience mechanics
-- ✅ Visual design foundation (colors, typography, spacing)
-- ✅ Design direction mockups and visual explorations
-- ✅ User journey flows and interaction design
-- ✅ Component strategy and custom component specifications
-- ✅ UX consistency patterns for common interactions
-- ✅ Responsive design and accessibility strategy
-
-**The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md`
-
-**Supporting Visual Assets:**
-
-- Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
-- Design directions mockups: `{planning_artifacts}/ux-design-directions.html`
-
-This specification is now ready to guide visual design, implementation, and development."
-
-### 2. Workflow Status Update
-
-Update the main workflow status file:
-
-- Load `{status_file}` from workflow configuration (if exists)
-- Update workflow_status["create-ux-design"] = "{default_output_file}"
-- Save file, preserving all comments and structure
-- Mark current timestamp as completion time
-
-### 3. Suggest Next Steps
-
-Provide guidance on logical next workflows:
-
-**Typical Next Workflows:**
-
-**Immediate Next Steps:**
-
-1. **Wireframe Generation** - Create detailed wireframes based on UX specification
-2. **Interactive Prototype** - Build clickable prototypes for user testing
-3. **Solution Architecture** - Technical architecture design with UX context
-4. **Figma Design** - High-fidelity visual design implementation
-
-**Visual Design Workflows:**
-
-- Wireframe Generation → Interactive Prototype → Figma Design
-- Component Showcase → AI Frontend Prompt → Design System Implementation
-
-**Development Workflows:**
-
-- Solution Architecture → Epic Creation → Development Sprints
-
-**What would be most valuable to tackle next?**
-
-### 4. Document Quality Check
-
-Perform final validation of the UX design:
-
-**Completeness Check:**
-
-- Does the specification clearly communicate the design vision?
-- Are user journeys thoroughly documented?
-- Are all critical components specified?
-- Are responsive and accessibility requirements comprehensive?
-- Is there clear guidance for implementation?
-
-**Consistency Check:**
-
-- Do all sections align with the emotional goals?
-- Is design system integration clearly defined?
-- Are patterns consistent across all user flows?
-- Does visual direction match established foundation?
-
-### 5. Final Completion Confirmation
-
-Confirm completion with user:
-"**Your UX Design Specification for {{project_name}} is now complete and ready for implementation!**
-
-**The specification contains everything needed to:**
-
-- Guide visual designers in creating the final interfaces
-- Inform developers of all UX requirements and patterns
-- Ensure consistency across all user interactions
-- Maintain accessibility and responsive design standards
-- Provide a foundation for user testing and iteration
-
-**Ready to continue with:**
-
-- Wireframe generation for detailed layouts?
-- Interactive prototype for user testing?
-- Solution architecture for technical planning?
-- Visual design implementation?
-
-**Or would you like to review the complete specification first?**
-
-[UX Design Workflow Complete]"
-
-## SUCCESS METRICS:
-
-✅ UX design specification contains all required sections
-✅ All collaborative content properly saved to document
-✅ Workflow status file updated with completion information
-✅ Clear next step guidance provided to user
-✅ Document quality validation completed
-✅ User acknowledges completion and understands next options
-
-## FAILURE MODES:
-
-❌ Not updating workflow status file with completion information
-❌ Missing clear next step guidance for user
-❌ Not confirming document completeness with user
-❌ Workflow not properly marked as complete in status tracking
-❌ User unclear about what happens next
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## WORKFLOW COMPLETION CHECKLIST:
-
-### Design Specification Complete:
-
-- [ ] Executive summary and project understanding
-- [ ] Core experience and emotional response definition
-- [ ] UX pattern analysis and inspiration
-- [ ] Design system choice and strategy
-- [ ] Core interaction mechanics definition
-- [ ] Visual design foundation (colors, typography, spacing)
-- [ ] Design direction decisions and mockups
-- [ ] User journey flows and interaction design
-- [ ] Component strategy and specifications
-- [ ] UX consistency patterns documentation
-- [ ] Responsive design and accessibility strategy
-
-### Process Complete:
-
-- [ ] All steps completed with user confirmation
-- [ ] All content saved to specification document
-- [ ] Frontmatter properly updated with all steps
-- [ ] Workflow status file updated with completion
-- [ ] Next steps clearly communicated
-
-## NEXT STEPS GUIDANCE:
-
-**Immediate Options:**
-
-1. **Wireframe Generation** - Create low-fidelity layouts based on UX spec
-2. **Interactive Prototype** - Build clickable prototypes for testing
-3. **Solution Architecture** - Technical design with UX context
-4. **Figma Visual Design** - High-fidelity UI implementation
-5. **Epic Creation** - Break down UX requirements for development
-
-**Recommended Sequence:**
-For design-focused teams: Wireframes → Prototypes → Figma Design → Development
-For technical teams: Architecture → Epic Creation → Development
-
-Consider team capacity, timeline, and whether user validation is needed before implementation.
-
-## WORKFLOW FINALIZATION:
-
-- Set `lastStep = 14` in document frontmatter
-- Update workflow status file with completion timestamp
-- Provide completion summary to user
-- Do NOT load any additional steps
-
-## FINAL REMINDER:
-
-This UX design workflow is now complete. The specification serves as the foundation for all visual and development work. All design decisions, patterns, and requirements are documented to ensure consistent, accessible, and user-centered implementation.
-
-**Congratulations on completing the UX Design Specification for {{project_name}}!** 🎉
-
-**Core Deliverables:**
-
-- ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md`
-- ✅ Color Themes Visualizer: `{planning_artifacts}/ux-color-themes.html`
-- ✅ Design Directions: `{planning_artifacts}/ux-design-directions.html`

package/pennyfarthing-dist/workflows/ux-design/ux-design-template.md

@@ -1,13 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
----
-
-# UX Design Specification {{project_name}}
-
-**Author:** {{user_name}}
-**Date:** {{date}}
-
----
-
-<!-- UX design content will be appended sequentially through collaborative workflow steps -->

package/pennyfarthing-dist/workflows/ux-design/workflow.yaml

@@ -1,41 +0,0 @@
-# UX Design Workflow - Imported for BMAD Compatibility
-#
-# This is a stepped workflow imported from BMAD that guides users through
-# comprehensive UX design planning with the UX Designer agent.
-# Single-mode workflow with 14 sequential steps covering discovery,
-# visual design, component strategy, and accessibility.
-#
-# Purpose: Create comprehensive UX design specifications
-# Role: UX facilitator working with product stakeholder
-# Output: UX design specification document
-#
-# Source: BMAD-METHOD/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/
-# Migrated: 2026-01-22
-
-workflow:
-  name: ux-design
-  description: |
-    BMAD reference workflow: Work with a peer UX Design expert to plan your
-    application's UX patterns, look and feel. Covers discovery, emotional design,
-    visual foundation, user journeys, component strategy, and accessibility.
-  version: "1.0.0"
-  type: stepped
-
-  # Step configuration
-  steps:
-    path: ./steps/
-    pattern: step-*.md
-
-  # Variables available in step files
-  variables:
-    project_root: .
-    planning_artifacts: ./artifacts
-    output_file: artifacts/ux-design-specification.md
-
-  # Agent assignment - UX Designer for visual design workflow
-  agent: ux-designer
-
-  # Triggers - when to suggest this workflow
-  triggers:
-    types: [ux-design, create-ux-design, on_demand]
-    tags: [bmad, ux, design, visual, accessibility]

package/pennyfarthing_scripts/README.md

@@ -1,66 +0,0 @@
-# Pennyfarthing Scripts (Python)
-
-**This is a distributed Python package.** It ships to users via npm alongside the bash scripts.
-
-## Installation
-
-The package is automatically available when Pennyfarthing is installed. PYTHONPATH is set by the calling script via environment variables.
-
-## Packages
-
-| Package | Purpose |
-|---------|---------|
-| `common/` | Shared utilities (output formatting, config) |
-| `jira/` | Jira CLI wrapper (sync, create, claim) |
-| `sprint/` | Sprint YAML management |
-| `story/` | Story operations |
-| `git/` | Git utilities |
-| `brownfield/` | Codebase analysis for new projects |
-| `prime/` | Context priming |
-| `preflight/` | Pre-flight checks |
-
-## Top-Level Modules
-
-| Module | Purpose |
-|--------|---------|
-| `hooks.py` | Claude Code hook implementations |
-| `bellmode_hook.py` | Bell mode hook |
-| `pretooluse_hook.py` | PreToolUse hook |
-| `welcome_hook.py` | Welcome message hook |
-| `workflow.py` | Workflow utilities |
-| `swebench.py` | SWE-bench evaluation support |
-
-## Usage
-
-Scripts invoke Python modules directly:
-
-```bash
-# From a bash script
-python -m pennyfarthing_scripts.jira.sync "$EPIC_ID"
-
-# PYTHONPATH is set by the script:
-# export PYTHONPATH="${PROJECT_ROOT}${PYTHONPATH:+:$PYTHONPATH}"
-```
-
-## Dependencies
-
-Minimal dependencies - standard library plus:
-- `httpx` - HTTP client
-- `pyyaml` - YAML parsing
-
-NO GPU dependencies here. Those belong in meta scripts (`scripts/*.py`).
-
-## Testing
-
-```bash
-cd pennyfarthing
-python -m pytest pennyfarthing_scripts/tests/
-```
-
-## What Does NOT Go Here
-
-Meta-only Python scripts belong in `scripts/`:
-- Portrait generation (requires torch, diffusers)
-- Other GPU-heavy tools
-
-See `CLAUDE.md` for the full decision tree.

package/pennyfarthing_scripts/__init__.py

@@ -1,17 +0,0 @@
-"""
-Pennyfarthing Scripts - Python utilities for agent orchestration.
-
-Modules:
-    config: Project root detection, YAML configuration loading
-    output: Colored console output utilities (success, info, warn, error)
-    sprint: Sprint YAML parsing and story access
-    jira: Jira CLI wrapper and JiraClient for REST API operations
-    jira_sync: Async epic sync to Jira
-    jira_sync_story: Single story sync to Jira
-    jira_epic_creation: Create Jira epics from sprint YAML
-    jira_bidirectional_sync: Bidirectional sync between sprint YAML and Jira
-    preflight: Async preflight checks for workflow completion
-    swebench: SWE-bench patch parsing and scenario utilities
-"""
-
-__version__ = "7.6.1"

package/pennyfarthing_scripts/bellmode_hook.py

@@ -1,154 +0,0 @@
-#!/usr/bin/env python3
-"""
-Bell Mode PostToolUse Hook (Python)
-
-This hook is called by Claude Code after each tool execution.
-When bell mode is enabled and there are queued messages, it returns
-the first queued message as additionalContext to be injected into
-Claude's next API call.
-
-Configuration files:
-  .pennyfarthing/config.local.yaml - workflow.bell_mode: true/false
-  .pennyfarthing/bell-queue.json - [{"text": "...", "images": [...]}, ...]
-
-Output format (when injecting):
-  {
-    "hookSpecificOutput": {
-      "hookEventName": "PostToolUse",
-      "additionalContext": "User feedback: <message>"
-    }
-  }
-
-Output when disabled or queue empty: (nothing - exit 0)
-
-Story: MSSCI-12409 - Hook consistency and WheelHub consolidation
-"""
-
-import json
-import sys
-from pathlib import Path
-
-# Add parent directory to path for imports
-sys.path.insert(0, str(Path(__file__).parent))
-
-from hooks import (
-    find_project_root,
-    get_cyclist_port,
-    send_to_cyclist,
-    output_hook_response,
-    HookResponse,
-    is_bell_mode_enabled,
-)
-
-
-def read_bell_queue(project_root: Path) -> list[dict]:
-    """Read the bell message queue.
-
-    Args:
-        project_root: Project root directory
-
-    Returns:
-        List of queued messages, or empty list if none
-    """
-    queue_path = project_root / ".pennyfarthing" / "bell-queue.json"
-    if not queue_path.exists():
-        return []
-
-    try:
-        with open(queue_path) as f:
-            queue = json.load(f)
-            if isinstance(queue, list):
-                return queue
-    except (json.JSONDecodeError, OSError):
-        pass
-
-    return []
-
-
-def dequeue_message(project_root: Path) -> None:
-    """Remove the first message from the queue.
-
-    Args:
-        project_root: Project root directory
-    """
-    queue_path = project_root / ".pennyfarthing" / "bell-queue.json"
-    if not queue_path.exists():
-        return
-
-    try:
-        with open(queue_path) as f:
-            queue = json.load(f)
-
-        if isinstance(queue, list) and len(queue) > 0:
-            queue = queue[1:]  # Remove first item
-            with open(queue_path, "w") as f:
-                json.dump(queue, f)
-    except (json.JSONDecodeError, OSError):
-        pass
-
-
-def notify_cyclist(project_root: Path, message_text: str) -> None:
-    """Notify Cyclist browser that a queued message was consumed.
-
-    Args:
-        project_root: Project root directory
-        message_text: The message text that was consumed
-    """
-    try:
-        send_to_cyclist(
-            endpoint="/api/bell-consumed",
-            data={"text": message_text},
-            project_root=project_root,
-            timeout=5,
-        )
-    except Exception:
-        # Ignore errors - don't block hook
-        pass
-
-
-def main() -> None:
-    """Main entry point for PostToolUse bell mode hook."""
-    try:
-        # Read and discard stdin (required by hook protocol)
-        sys.stdin.read()
-
-        # Find project root
-        project_root = find_project_root()
-        if not project_root:
-            sys.exit(0)
-
-        # Check if bell mode is enabled
-        if not is_bell_mode_enabled(project_root):
-            sys.exit(0)
-
-        # Read queue
-        queue = read_bell_queue(project_root)
-        if not queue:
-            sys.exit(0)
-
-        # Get first message
-        first_message = queue[0]
-        message_text = first_message.get("text", "")
-        if not message_text:
-            sys.exit(0)
-
-        # Output hook response with additionalContext
-        output_hook_response(HookResponse(
-            event_name="PostToolUse",
-            additional_context=f"User feedback: {message_text}",
-        ))
-
-        # Dequeue message and notify Cyclist (in background-ish - after output)
-        dequeue_message(project_root)
-        notify_cyclist(project_root, message_text)
-
-        sys.exit(0)
-
-    except Exception as e:
-        # On error, exit silently
-        print(f"[bellmode-hook] Error: {e}", file=sys.stderr)
-        sys.exit(0)
-
-
-if __name__ == "__main__":
-    main()

package/pennyfarthing_scripts/brownfield/__init__.py

@@ -1,35 +0,0 @@
-"""
-Brownfield discovery module for Pennyfarthing.
-
-Analyzes existing codebases and generates AI-ready documentation.
-"""
-
-from pennyfarthing_scripts.brownfield.discover import (
-    DepthLevel,
-    ProjectType,
-    DiscoveryResult,
-    detect_project_type,
-    detect_tech_stack,
-    scan_directory_structure,
-    detect_architecture_patterns,
-    generate_project_overview,
-    generate_tech_stack_doc,
-    generate_source_tree_doc,
-    generate_ai_guidance_doc,
-    discover,
-)
-
-__all__ = [
-    "DepthLevel",
-    "ProjectType",
-    "DiscoveryResult",
-    "detect_project_type",
-    "detect_tech_stack",
-    "scan_directory_structure",
-    "detect_architecture_patterns",
-    "generate_project_overview",
-    "generate_tech_stack_doc",
-    "generate_source_tree_doc",
-    "generate_ai_guidance_doc",
-    "discover",
-]

package/pennyfarthing_scripts/brownfield/__main__.py

@@ -1,7 +0,0 @@
-"""Entry point for python -m pennyfarthing_scripts.brownfield."""
-
-import sys
-from pennyfarthing_scripts.brownfield.cli import cli
-
-if __name__ == "__main__":
-    sys.exit(cli())