chore: release main

[github-actions]

🤖 I have created a release beep boop

ask-plugin: 0.3.2

0.3.2 (2026-04-12)

Features

• cli: convention-based docs discovery pipeline (#48) (d9f8529)
• cli: global ASK docs store at ~/.ask/ (#60) (51c77c8)
• cli: in-place npm docs — reference node_modules directly (#59) (d05025f)
• cli: lazy ask src and ask docs commands (#63) (cbd8e30)
• cli: PM-driven install flow with ask.json (#52) (e360cba)
• cli: PM-unified github store layout with shallow clones (#67) (88cdcdf)
• cli: rich ask list command with --json output (#50) (feb2ba3)

ask: 0.3.2

0.3.2 (2026-04-12)

Features

• cli: convention-based docs discovery pipeline (#48) (d9f8529)
• cli: global ASK docs store at ~/.ask/ (#60) (51c77c8)
• cli: in-place npm docs — reference node_modules directly (#59) (d05025f)
• cli: lazy ask src and ask docs commands (#63) (cbd8e30)
• cli: PM-driven install flow with ask.json (#52) (e360cba)
• cli: PM-unified github store layout with shallow clones (#67) (88cdcdf)
• cli: rich ask list command with --json output (#50) (feb2ba3)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @pleaseai/ask-schema bumped to 0.3.1

ask-schema: 0.3.1

0.3.1 (2026-04-12)

Features

• cli: convention-based docs discovery pipeline (#48) (d9f8529)
• cli: global ASK docs store at ~/.ask/ (#60) (51c77c8)
• cli: in-place npm docs — reference node_modules directly (#59) (d05025f)
• cli: PM-driven install flow with ask.json (#52) (e360cba)
• cli: PM-unified github store layout with shallow clones (#67) (88cdcdf)

---

This PR was generated with Release Please. See documentation.

[cloudflare-workers-and-pages]

Deploying ask-registry with    Cloudflare Pages

Latest commit:	3c8414b
Status:	🚫  Build failed.

View logs

[cubic-dev-ai]

No issues found across 7 files

_{Auto-approved: Automated release PR by github-actions[bot]. It only contains version bumps and changelog updates, which are standard, low-risk operations.}

Architecture diagram

sequenceDiagram
    participant User as User / Developer
    participant CLI as CLI (@pleaseai/ask)
    participant Pipe as NEW: Discovery Pipeline
    participant FS as Local File System
    participant Schema as Schema (@pleaseai/ask-schema)

    Note over User,Schema: Convention-based Docs Discovery Flow

    User->>CLI: Run documentation command (e.g. init/sync)
    CLI->>Pipe: NEW: Trigger discovery pipeline
    
    loop For each project convention path
        Pipe->>FS: Scan directory (e.g., /docs, /packages)
        FS-->>Pipe: Return file system metadata
    end

    Pipe->>Schema: NEW: Validate discovered entries
    Schema-->>Pipe: Validated Metadata / Registry Types

    alt Documentation candidates found
        Pipe-->>CLI: Return list of discovered docs
        CLI->>User: Suggest/Register docs based on conventions
    else No conventions matched
        Pipe-->>CLI: Return empty discovery result
        CLI->>User: Fallback to manual configuration
    end

    Note over CLI,Schema: CLI 0.3.2 now depends on Schema 0.3.1

Loading

[github-actions]

🤖 Created releases:

• ask-schema-v0.3.1
• ask-v0.3.2
• ask-plugin-v0.3.2

🌻