CI / build-and-test (pull_request) Failing after 1m19s

Details

feat(ci,flags,ops): ship end-to-end CI, feature-flag framework, gated surfaces, and ops docs

CI (.gitea/workflows/ci.yaml): lint → typecheck → vitest w/ coverage → OpenNext build → preview smoke → bundle-size budgets; Node 20; npm ci; artifacts; safe env; D1 dry-run scaffold.

Budgets: add scripts/budgets.mjs; TOTAL_STATIC_MAX_BYTES and MAX_ASSET_BYTES thresholds; report top offenders; fail on breach; README CI section.

Flags: add lib/flags.ts with typed booleans and safe defaults (ADMIN_ENABLED, ARTISTS_MODULE_ENABLED, UPLOADS_ADMIN_ENABLED, BOOKING_ENABLED, PUBLIC_APPOINTMENT_REQUESTS_ENABLED, REFERENCE_UPLOADS_PUBLIC_ENABLED, DEPOSITS_ENABLED, PUBLIC_DB_ARTISTS_ENABLED, ADVANCED_NAV_SCROLL_ANIMATIONS_ENABLED, STRICT_CI_GATES_ENABLED, ISR_CACHE_R2_ENABLED); robust parsing; client provider; unit tests.

Wiring: gate Admin shell and admin write APIs (503 JSON on uploads and artists writes); disable booking submit and short-circuit booking mutations when off; render static Hero/Artists when advanced animations off; tests for UI and API guards.

Ops: expand docs/prd/rollback-strategy.md with “Feature Flags Operations,” Cloudflare Dashboard and wrangler.toml steps, preview simulation, incident playbook, and post-toggle smoke checklist.

Release: add docs/releases/2025-09-19-feature-flags-rollout.md with last-good commit, preview/production flag matrices, rollback notes, and smoke results; link from rollback doc.

Chore: fix TS issues (gift-cards boolean handling, Lenis options, tailwind darkMode), remove next-on-pages peer conflict, update package.json scripts, configure Gitea act_runner label, open draft PR to trigger CI.

Refs: CI-1, FF-1, FF-2, FF-3, OPS-1
Impact: defaults preserve current behavior; no runtime changes unless flags flipped

2025-09-19 21:33:09 -06:00

3.8 KiB

Raw Blame History

/create-doc Task

When this command is used, execute the following task:

Create Document from Template (YAML Driven)

⚠️ CRITICAL EXECUTION NOTICE ⚠️

THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL

When this task is invoked:

DISABLE ALL EFFICIENCY OPTIMIZATIONS - This workflow requires full user interaction
MANDATORY STEP-BY-STEP EXECUTION - Each section must be processed sequentially with user feedback
ELICITATION IS REQUIRED - When elicit: true, you MUST use the 1-9 format and wait for user response
NO SHORTCUTS ALLOWED - Complete documents cannot be created without following this workflow

VIOLATION INDICATOR: If you create a complete document without user interaction, you have violated this workflow.

Critical: Template Discovery

If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.

CRITICAL: Mandatory Elicitation Format

When elicit: true, this is a HARD STOP requiring user interaction:

YOU MUST:

Present section content
Provide detailed rationale (explain trade-offs, assumptions, decisions made)
STOP and present numbered options 1-9:
- Option 1: Always "Proceed to next section"
- Options 2-9: Select 8 methods from data/elicitation-methods
- End with: "Select 1-9 or just type your question/feedback:"
WAIT FOR USER RESPONSE - Do not proceed until user selects option or provides feedback

WORKFLOW VIOLATION: Creating content for elicit=true sections without user interaction violates this task.

NEVER ask yes/no questions or use any other format.

Processing Flow

Parse YAML template - Load template metadata and sections
Set preferences - Show current mode (Interactive), confirm output file
Process each section:
- Skip if condition unmet
- Check agent permissions (owner/editors) - note if section is restricted to specific agents
- Draft content using section instruction
- Present content + detailed rationale
- IF elicit: true → MANDATORY 1-9 options format
- Save to file if possible
Continue until complete

Detailed Rationale Requirements

When presenting section content, ALWAYS include rationale that explains:

Trade-offs and choices made (what was chosen over alternatives and why)
Key assumptions made during drafting
Interesting or questionable decisions that need user attention
Areas that might need validation

Elicitation Results Flow

After user selects elicitation method (2-9):

Execute method from data/elicitation-methods
Present results with insights
Offer options:
- 1. Apply changes and update section
- 2. Return to elicitation menu
- 3. Ask any questions or engage further with this elicitation

Agent Permissions

When processing sections with agent permission fields:

owner: Note which agent role initially creates/populates the section
editors: List agent roles allowed to modify the section
readonly: Mark sections that cannot be modified after creation

For sections with restricted access:

Include a note in the generated document indicating the responsible agent
Example: "(This section is owned by dev-agent and can only be modified by dev-agent)"

YOLO Mode

User can type #yolo to toggle to YOLO mode (process all sections at once).

CRITICAL REMINDERS

❌ NEVER:

Ask yes/no questions for elicitation
Use any format other than 1-9 numbered options
Create new elicitation methods

✅ ALWAYS:

Use exact 1-9 format when elicit: true
Select options 2-9 from data/elicitation-methods only
Provide detailed rationale explaining decisions
End with "Select 1-9 or just type your question/feedback:"

3.8 KiB Raw Blame History