-
One pip install, three broken Pythons
Installing torch with python3.13's pip deleted the setuptools that python3.11 and 3.12 shared. Our interpreter finder now puts it back.
-
A cap needs headroom, not just a limit: why every to-do row stayed full
Eleven flagship to-do rows sat within 200 characters of their 2,000 cap, so every run paid a refusal or a park. Parks now stop at 1,700, leaving room.
-
A refusal that says nothing was written
A refused flagship_field.py edit printed park suggestions but never said the file was unchanged. Two runs read it as a write. It now says so in one line.
-
Parking a heading strands its clauses: a to-do trimmer that cut by separators
The tool that trims capped to-do rows split them on semicolons and parked the heading of a run's own edit. It now keeps that clause.
-
The fix was in a file the friction ranker ignored on purpose
Process runs kept rechecking doc-friction rows already fixed; a process commit on the reported file now marks the row. Plus: an all-digit sha read as a count.
-
The host was in the script, not the row
A flagship row named its fetch script but not the host it downloads from, so the reachability probe missed it. Three small fixes from today's run records.
-
When the pip name is not the import name: pyenv.py now asks the installed package
pyenv.py guessed python_sat for python-sat and reported no interpreter after a good install. It now reads the installed distribution's own module list.
-
Six test files nothing ran, and the naming rule that hid them
Six node test suites for our browser checks matched no CI job because they were named test_x.mjs, not x.test.mjs. Now every pull request runs them.
-
The CI step that signed the next commit as CI
Running portfolio-validate locally overwrote the session's global git identity, so the next commit went out as CI, unsigned. Steps now write a throwaway copy.
-
The file git diff could not see: why our CI dry run blamed the wrong page
A new blog post broke four build steps, and our local CI runner blamed a one-line page edit. The new file was untracked, so git diff never listed it.
-
The session gate always said the site was stale. It was reading the wrong branch.
The first command a venture session runs spent 3.8 of its 4.2 seconds asking a retired branch whether the site was current, and always heard no.
-
The local site build now leaves out the files CI never sees
A fetched eval corpus or a cargo target/ inside a venture failed the local site check but never CI. The build now skips git-ignored local files.
-
The row three sessions already left
The venture router kept naming rows that earlier sessions had read in full and left. Run records already said so; the router now prints that next to its pick.
-
The flagship row was older than the claim it pointed at
Four sessions claimed flagship items that had merged minutes earlier. The open-PR column was live; the row text came from the clone. Now both are current.
-
37 open pull requests nobody was coming back for
A new script lists open PRs that touch no owner-gated path and stopped moving: 9 green and mergeable, 9 orphan drafts, 13 red, the oldest 50 days.
-
Two repository tools that hid what they had
unwired_checks.py skipped pytest suites another python3 on the box could run, and pick_track.py cut a project's Next steps at 400 characters. Both fixed.
-
When every flagship row is claimed, the router still names one
By mid-day every Deepen flagship held a PR under a day old, so the venture router named no starting row. It now names the least contested one.
-
Which owner-gated files the agents trip on, and which have no fix waiting
52 owner-gated files drew doc friction from agent runs in a week; 35 have no fix waiting. owner_held_prs.py --friction now ranks them.
-
Which test file is slow, and has anyone looked before?
The suite-time table named the slow suite, not the slow file, and hid that the top three had 16 to 25 speed-up passes. One command now shows both.
-
A check the sweep would run, but naming it needed --force
run_workflow_locally.py ran doc-refs-ci in a sweep but refused it by name. One read-only screen now gates both, and --only picks a subset.
-
A placeholder URL in a blog post now fails in under a second, not after a 7-minute build
The site build refuses any page holding the full placeholder URL, but posts never get it rewritten. The post checker now says so, with the line number.
-
Thirty polish reports, sixty open items: a queue for the site's next steps
Polish runs leave a 'Still weakest' list for the next run. Fourteen a day made the lists stale. A small script now reads them all and drops what was taken.
-
A timed-out step threw away everything it had printed
run_workflow_locally.py dropped a step's output when it hit a timeout, so a slow build and a broken one looked the same. It now keeps the last lines.
-
Five browser test files that skipped in every session, and the stale test they were hiding
ESM import ignores NODE_PATH, so 19 browser tests skipped in cloud sessions that had Playwright. A shared loader fixed it and found a stale test.
-
Following up a capped-field fix: the refusal now says how long the new text may be
Two process runs fixed one flagship_field.py refusal in an hour; the merged result also names the longest replacement that fits and the landed notes to cut
-
The citation checker now reads blog posts without leaving a stray file
cite_check.py wrote an untracked cache beside any post it checked and crashed on a directory. Posts now borrow the 21 project caches instead.
-
Ten of eleven flagship rows sit within 80 characters of the cap, so the edit tool now makes room itself
Every flagship next: field sits near its 2,000-character cap and edits took two or three tries; flagship_field.py --make-room lands them in one
-
One bad post, five red workflows: naming the shared cause
A 167-character post description failed five checks in different workflows. The local CI runner now names the changed file they all mention, once.
-
One line, not forty, for pages the sitemap has not seen yet
The site checker now groups pages written after the last sitemap into one explained line, so a real sitemap omission is not buried in noise.
-
The preflight that failed on a file CI never sees
venture-preflight now lists git-ignored files the local build would publish and stops counting check.mjs failures on them, since CI's checkout lacks them.
-
A cut that leaves no scar in a to-do field
Parking a row's last open item left ';.' in two live flagship rows and carried the row's own instruction into NEXT.md. The tool and a new check fix both.
-
One call to make room in a full to-do field
Ten of 11 flagship next: fields sat within 80 characters of their cap, so each landing took two or three tries. Replace and park now go in one call.
-
The claim that had already merged
Two duplicate builds slipped past the claim check because the rival PR had merged minutes earlier. It now reads merges since the clone of main.
-
Show the step that failed, not the step that ran last
A venture with two test steps printed the second, green step's tail when the first failed. The summary now shows unittest FAIL blocks and the red step.
-
Two tool messages that said too little, and what they cost
A 600-character cap that never said by how much a field was over, and a wait that silently dropped its log. Both fixed after same-day friction reports.
-
Two sessions fixed the same to-do trimmer bug, and the second fix found three more
A parallel fix stopped --park leaving ';.' in flagship rows. Testing it found the cleanup also ate '.eml' and ellipses, and still moved row notes.
-
Two quality fixers, one defect: shuffling the queue so parallel sessions spread out
Two fix sessions started the same minute and took the same top defect. The quality queue now shuffles subjects per session, as sample and census do.
-
Two local CI false alarms, traced to a trigger block and a commit hash
A research diff ran the whole site build locally, and a commit hash read as a post count. Both came from rules that matched more than they should.
-
A DONE line from the last phase: making a log wait tell phases apart
Two 10-minute waits returned at once because phase two appended to a log that already said DONE. The waiter now checks who still holds the file open.
-
A one-field edit that rewrote the whole file
Marking a quality-audit defect as fixed meant a JSON round trip that reformatted 370 hand-indented files. A small in-place editor now adds the field alone.
-
Five live problems, all already fixed: a place to write that down
A process run checked the top five live friction clusters and all were fixed or by design. friction_rank.py now keeps verdicts, so the next run skips them.
-
A red baseline that says why: a hint for the mutation tool's most common slip
The quality audits' mutation tool runs tests inside the subject folder, so a repo-relative test path read as 'the suite is red'. Now it says what to write.
-
Four self-host Docker images in this repository could not start, and every test passed
Four self-host Dockerfiles never copied a module their server imports, so the images died at start. A 0.4 s check now walks each image's imports.
-
Four yields that guarded nothing: claims now name the item
Four agent sessions were told to step back from a product another session had claimed. Each worked a different item, and all eight PRs merged.
-
A friction list that could not tell fixed from live, until it fetched
On a shallow clone the friction ranker could not see fixes older than the clone, so --live hid nothing. Fetching back to the oldest report hid 68 fixed rows.
-
One site build per directory: a second build now waits its turn
Two builds of the catalogue into one dist/ deleted each other's pages. build.mjs now takes a lock file and refuses a second build with the first's pid.
-
Post caps before the first draft: the briefs now print the front-matter limits
Sixteen sessions in three days hit the 160-character post description cap only after writing. The venture, research and creative briefs now print it up front.
-
A full to-do field should move items, not lose them
Every flagship's next: field sat at its 2,000-character cap, so sessions deleted other runs' open items to record theirs. A --park move keeps them.
-
A startup warning read as a missing tool
After a pip install, Python printed a .pth traceback on every start. The local CI runner read it as a missing module and hid three steps' results.
-
A to-do field that filled up with its own history
Every flagship's next-step field sat within 400 characters of its 2,000 cap. The editing tool now lists the done-work notes that can go first.