@mushi-mushi/inventory-auth-runner

A small Playwright runner that executes the auth.scripted block of your inventory.yaml, captures the resulting cookies, and stores them in project_settings so the v2 crawler and synthetic monitor can reach pages behind a login wall.

When you need it

If your inventory.yaml describes any path that requires a session (/dashboard, /settings/*), the crawler and synthetic monitor will get redirected to /login until they have valid auth. This package gives you the bootstrap step that hands them a session.

Install

pnpm add -D @mushi-mushi/inventory-auth-runner

Usage

Add an auth.scripted block to inventory.yaml:

auth:
  scripted:
    steps:
      - navigate: /login
      - type: { selector: '[data-testid=email]',    value: '$E2E_EMAIL' }
      - type: { selector: '[data-testid=password]', value: '$E2E_PASSWORD' }
      - click:    { selector: '[data-testid=login]' }
      - waitFor:  { url: /\/dashboard$/ }

Then run:

E2E_EMAIL=user@acme.test \
E2E_PASSWORD=… \
MUSHI_API_KEY=mushi_… \
MUSHI_PROJECT_ID=proj_… \
npx mushi-mushi-auth refresh

The runner walks the steps headlessly, captures every cookie set by the target origin, and POSTs them to /v1/admin/projects/:id/settings. The crawler and synthetic monitor read from the same row on every run.

In CI

Cookies expire. Rebake them on a schedule (e.g. nightly) so the synthetic monitor never falls back to an unauthenticated walk:

name: Mushi auth bootstrap
on:
  schedule:
    - cron: '0 6 * * *'
  workflow_dispatch:
jobs:
  refresh:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: kensaurus/mushi-mushi/packages/mcp-ci@master
        with:
          api-key:    ${{ secrets.MUSHI_API_KEY }}
          project-id: ${{ secrets.MUSHI_PROJECT_ID }}
          command:    auth-bootstrap

The auth-bootstrap command in @mushi-mushi/mcp-ci is a convenience wrapper that calls this runner — use it from CI.