Dev Handbook

The maintainer handbook explains repository-health work that should not be rediscovered from CI logs, shell history, or one-off commands. It covers the maintainer package itself, the shared make surface, and the GitHub workflow entrypoints that enforce release and documentation policy.

This handbook should make repository automation inspectable without pretending that maintainer tooling is part of the end-user product surface.

Open the bijux-dev package Open operations Open makes

Visual Summary

flowchart TB
    handbook["Maintainer handbook"]
    handbook --> package["bijux-dev package"]
    handbook --> operations["operations section"]
    handbook --> makes["makes section"]
    handbook --> workflows["gh-workflows section"]
    operations --> evidence["evidence and diagnostics workflows"]
    makes --> commands["root command surfaces"]
    workflows --> policy["verification and release entrypoints"]

Package Destination

• bijux-dev owns the repository control plane, maintainer automation, diagnostics, and release verification flows

Sections In This Handbook

• Dev Operations
• Dev Governance
• makes
• gh-workflows

Maintainer Workflow Map

If you need to...	Start page
set up or validate local maintainer tooling	Toolchain Setup
run repository gates before merge	Repository Gates
investigate failing verification outputs	Diagnostics and Reporting
handle release or pipeline incidents	Incident Response
adjust policy for tests, contracts, or dependencies	Dev Governance

Use This Handbook For

• maintainer command workflows and repository gates
• evidence collection and reporting operations
• policy decisions around contracts, dependencies, and security
• shared make entrypoints and GitHub workflow triggers

Program Handbooks

• Repository Handbook
• CLI Handbook
• DAG Handbook

Decision Boundary

When a question affects runtime behavior seen by end users, switch to the program handbook (bijux-cli or bijux-dag) and return here only for maintainer-specific verification and release workflows.

Purpose

This page routes readers into the repository-health sections that actually exist, instead of leaving make files and workflows as undocumented support glue.

Stability

Keep this page aligned with the real maintainer sections under docs/bijux-dev/ and the automation surfaces used by this repository today.