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

4.4 KiB

Raw Blame History

/advanced-elicitation Task

When this command is used, execute the following task:

Advanced Elicitation Task

Purpose

Provide optional reflective and brainstorming actions to enhance content quality
Enable deeper exploration of ideas through structured elicitation techniques
Support iterative refinement through multiple analytical perspectives
Usable during template-driven document creation or any chat conversation

Usage Scenarios

Scenario 1: Template Document Creation

After outputting a section during document creation:

Section Review: Ask user to review the drafted section
Offer Elicitation: Present 9 carefully selected elicitation methods
Simple Selection: User types a number (0-8) to engage method, or 9 to proceed
Execute & Loop: Apply selected method, then re-offer choices until user proceeds

Scenario 2: General Chat Elicitation

User can request advanced elicitation on any agent output:

User says "do advanced elicitation" or similar
Agent selects 9 relevant methods for the context
Same simple 0-9 selection process

Task Instructions

1. Intelligent Method Selection

Context Analysis: Before presenting options, analyze:

Content Type: Technical specs, user stories, architecture, requirements, etc.
Complexity Level: Simple, moderate, or complex content
Stakeholder Needs: Who will use this information
Risk Level: High-impact decisions vs routine items
Creative Potential: Opportunities for innovation or alternatives

Method Selection Strategy:

Always Include Core Methods (choose 3-4):
- Expand or Contract for Audience
- Critique and Refine
- Identify Potential Risks
- Assess Alignment with Goals
Context-Specific Methods (choose 4-5):
- Technical Content: Tree of Thoughts, ReWOO, Meta-Prompting
- User-Facing Content: Agile Team Perspective, Stakeholder Roundtable
- Creative Content: Innovation Tournament, Escape Room Challenge
- Strategic Content: Red Team vs Blue Team, Hindsight Reflection
Always Include: "Proceed / No Further Actions" as option 9

2. Section Context and Review

When invoked after outputting a section:

Provide Context Summary: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
Explain Visual Elements: If the section contains diagrams, explain them briefly before offering elicitation options
Clarify Scope Options: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
- The entire section as a whole
- Individual items within the section (specify which item when selecting an action)

3. Present Elicitation Options

Review Request Process:

Ask the user to review the drafted section
In the SAME message, inform them they can suggest direct changes OR select an elicitation method
Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
Keep descriptions short - just the method name
Await simple numeric selection

Action List Presentation Format:

**Advanced Elicitation Options**
Choose a number (0-8) or 9 to proceed:

0. [Method Name]
1. [Method Name]
2. [Method Name]
3. [Method Name]
4. [Method Name]
5. [Method Name]
6. [Method Name]
7. [Method Name]
8. [Method Name]
9. Proceed / No Further Actions

Response Handling:

Numbers 0-8: Execute the selected method, then re-offer the choice
Number 9: Proceed to next section or continue conversation
Direct Feedback: Apply user's suggested changes and continue

4. Method Execution Framework

Execution Process:

Retrieve Method: Access the specific elicitation method from the elicitation-methods data file
Apply Context: Execute the method from your current role's perspective
Provide Results: Deliver insights, critiques, or alternatives relevant to the content
Re-offer Choice: Present the same 9 options again until user selects 9 or gives direct feedback

Execution Guidelines:

Be Concise: Focus on actionable insights, not lengthy explanations
Stay Relevant: Tie all elicitation back to the specific content being analyzed
Identify Personas: For multi-persona methods, clearly identify which viewpoint is speaking
Maintain Flow: Keep the process moving efficiently

4.4 KiB Raw Blame History