Skip to content

Factory Operations

Jump to bottom
easylogic edited this page Oct 16, 2026 · 7 revisions

Factory Operations

GitHub is the control plane (Issues, Discussions, Wiki). Local git is the execution plane (code only).

Roles and communication

Mentor ↔ Planner only. Planner dispatches to Compute and Review and collects their results. Mentor is the Integrator and handles escalations.

Branches

  • develop (local, integration worktree .claude/worktrees/hub-integration) is the integration branch. main is release-only.
  • Compute branches are cut from local develop as hub/issue-N, one worktree each. Commits are #N: ....
  • After Review PASS, the Integrator runs git merge --no-ff hub/issue-N into develop, then cargo fmt --check && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace on develop, then closes the Issue and removes the task worktree.
  • The Integrator merge gate also runs caffeinate -i env PROPTEST_CASES=512 cargo test -p barocss-hub-cli --lib (~9 min), because the in-crate CLI proptests default to 128 cases for test time (0274b64). The package was hub-cli before #35 (D-033 rename: packages barocss-hub-core / barocss-hub-cli / barocss-hub-bench, binary barocss-hub, crate directories unchanged).
  • Deep proptest job (mandatory since #50): for every Issue that touches session, digest, sync, wire or remote code, Review runs and the Integrator re-runs, before the --no-ff merge commit, caffeinate -i env PROPTEST_CASES=512 HUB_TEST_FULL_PROPTEST=1 cargo test -p barocss-hub-cli --lib (lifts the #46 divergence-proptest cap of d1ab4dd). The Integrator does git merge --no-ff --no-commit, runs all checks, then commits or aborts. Also lint with --features barocss-hub-cli/lthash.
  • Release suite and shipped-binary hook check (since #55/#57): every merge also runs cargo test --workspace --release --no-fail-fast and scripts/check-no-test-hooks.sh (builds the dist binary in target/dist-check without the test-hooks feature and requires 0 HUB_TEST_ strings). Never hand out target/release/barocss-hub after cargo test --release: dev-dependency feature unification puts the hooks in it (fix tracked in #36).
  • Nothing is pushed during routine work. At release, push develop and open a single develop → main PR.
  • No force-push, no rewriting develop or main, no squash or rebase: plain merges only. No checkpoint PRs until CI and branch protection exist.
  • Wiki- or Discussion-only results are closed by the Planner after PASS.

Other

Research Discussions go in the Ideas category. Git identity: easylogic cyberuls@gmail.com. Decisions: see Decisions.

Clone this wiki locally