Repository navigation
Factory 0.9.37
Factory 0.9.37
- A re-applied factory:objective counts only from a person who can push; a ready mark beside one starts no review on Actions (#448, #449) (#450)
- A Question re-labelled since it was asked gets no ready-mark review in local mode: the label reruns the worker (#446) (#447)
- A session that ends abnormally while its own background job runs is resumed and told so; instructions match how -p waits (#440) (#445)
- A hand-off does not wait for a sibling a person holds out of the merge queue (#439) (#444)
- run --wait follows a merge on the repository's own bound, not a fixed 120 minutes (#438) (#441)
- A checks_hung queue removal counts toward QUEUE_TRIES only when the step really hung (#437) (#442)
- A sandbox record that cannot be read is no absent record: the dispatcher skips that Objective for the tick (#430) (#443)
- Limits a person owns become settings: relay, usage-limit waits, claim pause, local waits, stalls, sibling wait, part cap (#423) (#436)
- Launch loss, vendor holds, transcript lookup, queue conflicts, the board and key shapes decide on structure (#422) (#435)
- Local mode answers its stand-ins exactly or by decision call (#421) (#434)
- Log windows, rate limits, git transport and wide reds decide on structure (#420) (#433)
- Install runs every ecosystem's lockfile; the sandbox image rebuilds only when what it is made from changed (#419) (#431)
- An unread writer comment holds the merge only when it asks for something (#416) (#432)
- The fix-pass fence asks a decision call before refusing a toolchain file; name guesses become toolchain_paths (#414) (#428)
- Doctor reads token permissions and the CI workflow from structure; Claude model ids are the provider's to refuse (#418) (#427)
- A setup or install that fails while the network is down waits for it and runs again (#415) (#429)
- Acceptance entries and blockers come from exact structure, not heading or line regexes (#417) (#426)
- The same failure is a decision call where signatures cannot tell; the confidence floor is a setting beside the triage model (#413) (#424)
- An Objective's title is vouched for before any stage uses it (#410) (#425)
- An edit after the plan is judged once per new text: wording only keeps the plan (#400) (#409)
- The fix loop goes on while each fix pass makes progress, not for a fixed two passes (#399) (#408)
- Probe and serve tests decide on their own temp directory and the loop's lines, not the host's /tmp or a clock (#411) (#412)
- workflowEnv reads the parsed env block; the setup fence resolves the command by bash's grammar and fails closed (#387) (#397)
- A Question's answer is a decision call, not the first writer comment (#398) (#407)
- Network outages: GitHub's status page decides a persistent 5xx; a pass is cut off only on the harness's own error (#389) (#395)
- Decide a silent harness is hung from its own state, not 30 minutes of silence (#388) (#393)
- Required checks are waited for while they progress, not for a hidden 60 minutes (#401) (#403)
- Every stage call carries the current token; a 401 on an App token is refreshed once (#405) (#406)
- Owner-held limits become settings; triage's rerun waits within the checks' wait (#402) (#404)
- Provider busy, request-only refusals and set-up job failures decided on structure (#390) (#396)
- Automatic account choice prefers the account with the most quota left (#391) (#394)
- Decision calls fall back to the stage's own harness on its subscription (#379) (#385)
- Sibling hold and send-backs decide by trial merge, not file counts (#365, #366) (#384)
- Doctor reads CI triggers from parsed YAML and parses setup and validation with bash -n (#386) (#392)
- The rebase check decides on content, not commit ids (#362) (#375)
- The answer gate asks the decision model, not a 150-line threshold (#367) (#378)
- A reviewer finding counts as answered only when the decision model reads the answer as resolving it (#368) (#382)
- factory hold list / release: lift an account's usage-limit hold without deleting files (#376) (#383)
- Local sandboxes see what the repository's commands run, not a fixed tool list (#371) (#381)
- serve holds new starts on a machine fault instead of Blocking each Objective (#370) (#380)
- triage: only an exact changed path vetoes a rerun; name matches go to the model (#369) (#377)
- setup names the App permissions a personal account needs, without projects (#360 follow-up) (#364)
- Doctor's app permissions row names projects only where an App needs it (#360) (#361)
- A doctor Block names the failing check once and fixes with doctor's step (#357) (#358)
Upgrade notes
-
Who starts an Objective is checked now. Applying
factory:objective, removingfactory:draftor applyingfactory:restartcounts only when it comes from a person who can push, or from a pinned maintainer. An app's own token never counts. A start by anyone else isn't taken: the Objective is held Queued, and one comment says so. Queued Objectives whose latest start came from someone without push access (including a writer who has since lost it) are held at their next pick. A writer re-applyingfactory:objectivereleases them. -
The
*toolchain*file-name andtoolchain/directory guesses are gone from the fix-pass fence. An adopter who relied on them should list those paths in the newtoolchain_pathssetting. -
New settings, all with today's values as defaults:
decision_routetriage_min_confidencerebase_limitthird_party_wait_minutesguess_hourstoolchain_paths- machine.json
pressureandguess_hours - the local wait and outage bounds
INSTALL.md and LOCAL.md list them all.
-
Decision calls work without an AI Gateway key. They run on the stage's own harness subscription. Set
decision_route: offto turn them off; ADAPTERS.md lists what each call costs. -
Re-render the workflow (
factory setup --apply workflow) when you repin. This picks up the new action inputs.