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

2.7 KiB

Raw Blame History

/kb-mode-interaction Task

When this command is used, execute the following task:

KB Mode Interaction Task

Purpose

Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.

Instructions

When entering KB mode (*kb-mode), follow these steps:

1. Welcome and Guide

Announce entering KB mode with a brief, friendly introduction.

2. Present Topic Areas

Offer a concise list of main topic areas the user might want to explore:

What would you like to know more about?

Setup & Installation - Getting started with BMad
Workflows - Choosing the right workflow for your project
Web vs IDE - When to use each environment
Agents - Understanding specialized agents and their roles
Documents - PRDs, Architecture, Stories, and more
Agile Process - How BMad implements Agile methodologies
Configuration - Customizing BMad for your needs
Best Practices - Tips for effective BMad usage

Or ask me about anything else related to BMad-Method!

3. Respond Contextually

Wait for user's specific question or topic selection
Provide focused, relevant information from the knowledge base
Offer to dive deeper or explore related topics
Keep responses concise unless user asks for detailed explanations

4. Interactive Exploration

After answering, suggest related topics they might find helpful
Maintain conversational flow rather than data dumping
Use examples when appropriate
Reference specific documentation sections when relevant

5. Exit Gracefully

When user is done or wants to exit KB mode:

Summarize key points discussed if helpful
Remind them they can return to KB mode anytime with *kb-mode
Suggest next steps based on what was discussed

Example Interaction

User: *kb-mode

Assistant: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.