maintainers

Maintainers

Active contributors: Zachary BENSALEM, Mario Zechner

This map combines .github/CODEOWNERS with non-bot history on origin/main. The repository has one default owner entry, * @zochory. Recent Fleet-owned source history is concentrated under Zachary BENSALEM; upstream engine history should be handled in the Prime Agent repository.

Ownership map

Subsystem	Official owner	Recent non-bot contributor history	Last activity
Browser app and routes	zochory	Zachary BENSALEM	2026-09-04
Design system and panels	zochory	Zachary BENSALEM	2026-09-04
Browser/server protocol	zochory	Zachary BENSALEM	2026-09-04
Prime Agent adapter and handlers	zochory	Zachary BENSALEM	2026-09-04
Published launcher	zochory	Zachary BENSALEM	2026-09-04
Build, installer, and release scripts	zochory	Zachary BENSALEM, Zochory, kt	2026-09-04
Durable docs and guides	zochory	Zachary BENSALEM, Mario Zechner	2026-09-04

Bot accounts are excluded from the contributor column. The table is a navigation aid, not a substitute for current review assignment or CODEOWNERS changes.

Review boundaries

Fleet owns the browser product, adapter, protocol, design system, and launcher. Prime Agent owns providers, models, daemon internals, the upstream CLI, and the upstream protocol implementation. Do not copy or patch upstream source into this repository.

Changes that cross web/protocol, web/server, and web/app should be reviewed as one contract change. Changes to the runtime pin also need the checks in docs/guides/upstream-runtime.md and the adapter contract in docs/reference/adapter-contract.md.

Release responsibility

The release process is described in the release pipeline:

1. user-facing changes add a Changeset;
2. CircleCI runs the validation and package-verification jobs;
3. release-prepare opens a generated release pull request on main;
4. maintainers review and merge that pull request;
5. release-publish publishes the verified artifact to npm and GitHub.

The public package is @qredence/fleet in packages/fleet-web. Its current manifest version is 0.5.5; the pinned engine version is maintained separately in PRIME_AGENT_RUNTIME.json.

Required checks

Before merging a code change, run pnpm run check and the focused tests for the affected behavior. Release or packaging changes also use pnpm run build:web:release, pnpm run check:package, pnpm run check:web:release, and pnpm run test:release as appropriate. Do not use live provider APIs or credentials for ordinary tests.

Security and dependency maintenance

Keep the seven-day dependency cooldown, trust policy, allowed install scripts, and explicit overrides in pnpm-workspace.yaml aligned with .github/dependabot.yml. Runtime advisories that belong to the pinned Prime Agent tree are reported upstream and rechecked during runtime upgrades. Security reports follow SECURITY.md and use GitHub private vulnerability reporting.