@bragi-ai/eslint-config

Shared ESLint flat-config preset for the Bragi monorepo workspace.

Status: placeholder

Currently exports [] — no shared rules yet. The package exists so Portal, Bragi-AppKit, and Bragi-AudioApp can wire the workspace dependency now. Rules land here as each repo's ESLint migration completes.

Candidates queued for upstreaming (both earned from real incidents — see the source comments for context):

• no-navigate-in-index-route — blocks declarative <Navigate> inside react-router index: true routes. Came out of AppKit's 2026-04-18 bootstrap-loop autopsy.
• no-system-literal-in-audit — AST equivalent of Portal's apps/portal/scripts/check-audit-gates.sh (gates 2/4/5). Formalizes the Phase 11 "no 'system' literal" invariant as a lint rule instead of a grep run.

Why a placeholder?

The package exists before the rules do because three repos want to agree on where shared rules live before anyone writes the migration PR. With the shell published, each repo can:

1. Add @bragi-ai/eslint-config as a dev-dep in its own timeline.
2. Import and spread the preset in its eslint.config.js.
3. No-op today (empty array); automatically inherit rules when they land here.

That avoids a cascade-merge where "Portal lands @bragi-ai/eslint-config, then AppKit lands it, then AudioApp lands it" has to happen in order.

Adoption

// <repo>/eslint.config.js
import bragiConfig from '@bragi-ai/eslint-config';
import tsEslint from 'typescript-eslint';

export default [
  ...bragiConfig,
  ...tsEslint.configs.recommended,
  // repo-specific overrides below
];

Consumers

• Portal — not yet wired (ESLint flat-config migration is on the roadmap backlog).
• Bragi-AppKit — ready to consume.
• Bragi-AudioApp — ready to consume.

Adding a rule

1. Write the rule (usually under rules/<name>.js).
2. Add to the exported array in index.js.
3. Bump version per the breaking-change policy below.
4. Tag eslint-config-v<version> and push — the publish-eslint-config.yml workflow publishes to npm.
5. Binform the other repos via the Bragi vault so they can pull + re-lint.
6. Consider adding to each repo's CI as an enforcement gate.

Breaking-change policy

Matches AudioApp's spec-versioning convention (Bragi-AudioApp docs/specs/README.md).

| Change | Semver bump | Examples | |--------|-------------|----------| | Rule removed or renamed | major (1.0.0 → 2.0.0) | Consumer lint will pass where it previously failed — behavior change | | Existing rule tightened (more code newly fails lint) | major | Can break CI in downstream repos | | New rule added | minor (0.1.0 → 0.2.0) | Additive | | Existing rule loosened or rule config changed without new failures | minor | | | Docs / README / source comments only | patch | | | First real rule added to the placeholder | minor → 0.1.0 | |

Publishing to npm

Triggered by a tag push matching eslint-config-v*:

# Bump version in package.json, commit.
# Then:
git tag eslint-config-v0.1.0
git push origin eslint-config-v0.1.0

GitHub Actions workflow publish-eslint-config.yml runs pnpm --filter @bragi-ai/eslint-config publish --no-git-checks --access public using NPM_TOKEN from repo secrets.

Cross-repo consumers (AppKit, AudioApp) add "@bragi-ai/eslint-config": "^0.1.0" as a dev-dep once published.

Why not workspace:* for other repos?

AudioApp and AppKit live in separate git repos and pnpm workspaces. workspace:* resolution is monorepo-local — it only sees packages declared in the same pnpm-workspace.yaml. Cross-repo sharing goes through npm (or a file: path, but that's brittle). Hence the publish pipeline above.

Portal itself can consume via workspace:* once its ESLint flat-config migration lands — faster iteration, zero publish latency for in-house rules.

License

Internal — Bragi monorepo only. Published to npm for cross-repo consumption; do not redistribute.