Fold the review of 2026-09-30 into the decisions and open items, and delete the plan

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-30 16:11:27 +02:00
1 parent a63eed2e56
commit a211cf7414
4 files changed
+29 -86

No files matched your search

+18
View File
@@ -138,6 +138,22 @@ What was decided for roledesk and the one reason for each. The longer reasoning
**`pull` is a job that starts the cascade, on a default schedule of every 6h.** A schedule enqueues a job kind and a cascade is started by one, so the `pull` job only asks for the chain; declared beside it in `app/jobs/cascade.py`, the schedule is a starting point that an edit under Runs overrides for good. `pull` is not also a task, which would draw two buttons under Runs.
**Every whole read is guarded.** The 10% guard held only filtered, narrowed and `empty="suspect"` reads, so 206 of 309 boards, holding two thirds of the open board roles, could close every role on one answer that parsed to nothing: a Greenhouse or Lever body whose shape changed is HTTP 200 and zero rows, and the settle took it for a complete read. Now `_runner.read` raises `Suspect` on any read that is not a sweep and lists under `SUSPECT_SHARE` of what the same read listed last time, once that count is at least `SUSPECT_MIN` (10) for a plain read; filtered, narrowed and suspect reads keep their floor of one. The board is then failing with that reason, its roles stay open, and the Companies row says so. A board that really shrank costs a Recheck, which resets the count through `keep_size`, or `STALE_DAYS` of the same answer, after which the read is accepted and the count reset, since by then its roles have closed anyway.
**A read that could not ask remote keeps the remote roles it has.** `ask_for` keeps only the dimensions a reader declares, so on SmartRecruiters, Phenom, SuccessFactors and Eightfold the reach "DK, SE, remote" went out as "DK, SE", the read counted as filtered, and the settle closed every remote role outside those countries: 72 on 2026-09-29 and 30 (Philips, Bosch, Coolblue, Delivery Hero), with the line saying "follows agents: DK, SE". Now the listing records `remote_unasked` (`ats:remote_unasked:<target>`), `_close_unlisted` and `_close_swept` spare roles whose `remote` is `remote`, those close when the board has not listed them for `STALE_DAYS`, and the line says "remote not asked on SmartRecruiters". New remote roles on such a board are still not read; reading it whole instead is the owner's call (`open.md`).
**A read that asks nothing is not a read.** When an `ids` dimension maps to no host id, `series` used to return nothing, the listing was complete and empty, and the settle closed the board while the line read "site lists none of DK, SE: nothing asked", a fact about the site. The listing is incomplete now, logged at warning, and the line ends "not closing".
**Every target is guarded in its batch, and the failing record goes after the stamp.** `ats._board` dropped `ats:failing` before the rows were stored, and a row that failed in `item_of` or `upsert_role` failed the whole `pull_batch` job: that board had neither a stamp nor a record, and the boards after it in the batch, the same ones every pull since batches are ordered, were not read, never closed and never aged. `run_batch` now wraps each target, records the failure under the source's failing key and moves on; a Kill still propagates. The failing key is removed after `stamp`.
**Searches share the runner's bookkeeping.** `search.py` logged a failure and moved on, wrote its own `search:ok/complete/ids`, and read through `read_listing` rather than `read`, so it had no guard: a Platsbanken answer with `hits` renamed read as complete and empty and closed the search at once. It now reads through `_runner.read` (no sweep), records `search:failing:<target>` through `record_failure`, stamps through `stamp`, and the search row shows "not answering since" as a board row does; `failing_boards` reads both prefixes and a search failing for `STALE_DAYS` closes its roles. A removed search forgets its record.
**The settle speaks.** Its counts went into the job result, which nothing renders: the settle of 2026-09-30 10:06 closed 12,588 roles with one target unanswered and one incomplete, and the Problems log stayed empty. `close_boards` now raises one `pull.settled` notice when something needs a look: every target unanswered (with its failing reason) or read incomplete (boards only, and not one mid-sweep, or the notice would fire every pull), every board that closed more than `CLOSE_NOTICE` (50) roles or more than half of at least `CLOSE_SHARE_MIN` (10) open ones, and the totals. Its result key `failed` is `unanswered`. `run_pull` and `_boards` release the run claim when building the chain raises, so a finder that fails no longer refuses every pull for an hour with "a pull is already running".
**Narrowed boards close by age.** A read by fetch terms closed nothing, so a role that left such a board stayed open for good. A complete narrowed read now closes the board's roles it did not list and that were last seen more than `STALE_DAYS` ago, the rule searches have; no agent has terms yet, so this is latent.
**Declarations are checked against fixtures.** Of the `READS` traits only `posted`, `filters`, `complete`, `ceiling`, `empty`, `key` and `scope` were read at run time; `pay`, `remote`, `country`, `seniority`, `employment`, `teaser`, `places` and `text` were checked by nothing, so Platsbanken declared `remote="none"` while its rows set it and HR Manager declared `places="one"` and returned none. `tests/test_readers_contract.py` now parses each reader's listing and detail fixtures and asserts every declared field, a missing fixture fails instead of skipping, `places` has `none`, a search module needs `PARAMS` and `clean_params` and its rows `company`, every prep table names a reader and every reader stating words has a table, and `robots` must carry a date and name the paths the reader requests: seven records named a page the reader never asked for. Every host's robots.txt was read again on 2026-09-30; `api.smartrecruiters.com` disallows `/` for every agent but LinkedInBot, which is with the owner. The paths for modules without `READS`, `robots_page` and `ROBOTS_ANY_CASE` are gone, and `discover._UNREADABLE` lost the ten hosts that have modules.
## Ranking
**Scoring is per search agent.** A role is scored as `(uid, agent) -> score`, because a role is only good for a given search. Each gate has a mode: `require` becomes a SQL `WHERE`, `prefer` becomes a weighted term in the score. Gated roles keep their row with a reason. `companies.affinity = 2` skips the `any` group, `-1` mutes.
@@ -210,6 +226,8 @@ What was decided for roledesk and the one reason for each. The longer reasoning
**`GET /api/roles` serves a row, not a role.** It used to answer `roles.*`, the whole `Role` (`description`, `feed_text`, `raw` and `article_text` included, about 5.5 KB a role on average) for a feed that only ever shows a title, a few badges and an excerpt; a 1000-row restore was several megabytes of text a phone never renders. `Store.roles_page` selects only the fields a row draws (`RoleRow`), with `excerpt` built by `app.models.excerpt` off a `SUBSTR` of `summary` or `description`, never the column whole. Measured on a copy of the live database: a 60-row page went from 392 KiB to 39 KiB and a 1000-row restore from 6.6 MB to 631 KiB, both about a tenth. The reader is unaffected: it already fetched the whole role by uid when it opened one (`GET /api/roles/{uid}`, still the full `Role`); what changed is that the list row it painted from first, before that fetch lands, no longer carries a body to paint with, so the reader now waits on the fetch for the posting text and the original link the same way it always waited for the summary.
**A board's limits are words on its row, and a filter.** The readers declare what they cannot deliver and the runner records how a board was read, and none of it reached the Companies list beyond the reach line and "not answering since". `app/jobs/limits.py` turns both into words per board, in a fixed order: `failing`, `read incomplete`, `swept`, `filtered by reach`, `remote not asked`, `narrowed by terms`, `nothing asked`, `size 0`, `over the ceiling`, `text per role` or `no text` or `excerpt only`, `no pay`, `date not trusted`, `without text: N`, `text failed: M`, `read whole`. The row shows them after the size, the Companies filter offers each as an option under Limits, and `board_open` beside the company's count says how many open roles the board itself has, since the company's count includes search roles. The readers list on Sources shows every trait a reader declares.
## The phone
**Two tabs and a cog.** `TABS` in `app/web/pages.py` becomes Roles and Applications; the other seven pages (Agents, Companies, Sources, Jobs, Schedules, Messages, Account) move behind a settings cog at `/settings/<name>`, because nine tabs wrapped to three rows on a phone and six of them were setup or system pages. The Watchlist became a third tab and the settings pages became three sub-tabs, both below.
+2 -1
View File
@@ -38,7 +38,8 @@ What is known and not yet fixed, checked against the code on 2026-09-30. What la
## From the review of 2026-09-30
- **Remote roles are not read from hosts that cannot filter on remote.** On SmartRecruiters, Phenom, SuccessFactors and Eightfold the reach "DK, SE, remote" is asked as "DK, SE", and the filtered read closes remote roles outside them: 72 on 2026-09-29 and 30 (Philips 34, Bosch 25, Coolblue 10, Delivery Hero 3). Reading such boards whole is the owner's call; Bosch is about 70 requests a pull.
- **Remote roles are not read from hosts that cannot filter on remote.** On SmartRecruiters, Phenom, SuccessFactors and Eightfold the reach "DK, SE, remote" is asked as "DK, SE"; since 2026-09-30 the filtered read keeps the remote roles it has and the line says "remote not asked", but new remote roles on those 21 boards are never fetched, and the 72 closed on 2026-09-29 and 30 (Philips 34, Bosch 25, Coolblue 10, Delivery Hero 3) reopen only if a read lists them. Reading such boards whole is the owner's call; Bosch is about 70 requests a pull.
- **SmartRecruiters' API host disallows `/` for every agent but LinkedInBot** (read 2026-09-30), which covers the listing and the detail requests; `READS.robots` says "owner to decide" and the eleven boards are read meanwhile. Jobylon allows `*` but disallows named job crawlers (JobrapidoBot, JoobleBot, AdzunaBot); ours is not one of them. HR Manager's record says the owner decided on 2026-09-29 to read the API host; confirm it.
- **Provider names are hard-coded in nine places** (`cli.py`, `dupes.py`, `sources.py`, `pages.py`, `sources.html`, `sources.js`, `api.py`, `posting.py`) instead of `readers.PROVIDERS`, and `has_key` re-implements `resolve_key`.
- **`ats.py` keeps compatibility names that only tests reach for:** `_PARSERS`, `_parse_dt`, `_greenhouse_salary`, `_parse_teamtailor`, `_Refused` and `DETAIL_FIELDS`.
- **`title="provisional"` cannot work while `DETAIL_FIELDS` has no `title`.** Wave 2's WP9 must own `_runner.py` (`plan-hosts-wave-2.md`).
-77
View File
@@ -1,77 +0,0 @@
# Plan: the review of 2026-09-30, before new features
Written 2026-09-30 against main at `d47f4f5`, from five read-only reviews of the code, the docs and the live database: silent failures in ingestion, the reader contract, docs against code, settings against the pages, and a bug hunt. What is built here is folded into `decisions.md`, the rest goes to `open.md`, and this file is deleted.
`docs/plan-remote.md` is being built at the same time in `../jobboard-wt-remote-a` and `-b`, and its packages own `app/jobs/`, `app/storage/`, `app/web/api.py`, `plugins/` and `app/static/`. The packages below own single files inside those directories and keep their hunks small; the planner merges whichever lands second and resolves. The shared checkout also carries uncommitted edits to `score.py`, `models.py`, `store.py`, `agents.js`, `app.css`, `agents.html` and `test_score.py`; no package here touches those.
## What the reviews found
The test suite passes (2,923 tests, 20 skipped for missing fixtures), ruff is clean, mypy reports 15 typing errors, git is clean of stray branches. The pipeline as designed holds: a reader that raises is recorded per board and shown on its row from day one, a crashed batch closes only the boards it stamped, one pull runs at a time, two strikes protect swept boards, the reach is never empty. The problems are at the edges of that design.
**Roles are lost without a trace in four ways.**
1. **A host that cannot filter on remote drops the remote dimension silently.** `ask_for` keeps only the dimensions the reader declares (`_runner.py:374`), so on SmartRecruiters, Phenom, SuccessFactors and Eightfold the agents' reach "DK, SE, remote" becomes "DK, SE", the read counts as filtered, and `_close_unlisted` closes every remote role outside DK and SE. The Companies line says "follows agents: DK, SE" and nothing about remote. On 2026-09-29 and 30 this closed 72 remote roles inside the agent's Europe rule (Philips 34, Bosch 25, Coolblue 10, Delivery Hero 3), and new remote roles on those 21 boards are never fetched.
2. **206 of 309 boards have no guard against an empty answer.** The 10% guard runs only for filtered, narrowed or `empty="suspect"` reads (`_runner.py:674`). A Greenhouse or Lever answer whose shape changed parses to zero rows with HTTP 200, is stamped complete, and the settle closes the whole board: 15,635 open roles sit on unguarded boards.
3. **A crash after the read starves the rest of the batch, every pull.** `ats._board` removes the failing key before the rows are stored (`ats.py:410`), and `item_of`, `upsert_role` and `stamp` run outside the try, with no per-target guard in `run_batch` (`pull.py:198`). A bad row fails the whole batch job: that board has neither a stamp nor a failing record, the boards after it in the batch are not read, and batches are stable, so the same neighbours are skipped on every pull, never close, never age, never show "not answering".
4. **A search that fails leaves no trace, and searches have no guard.** `search.py:140` logs and continues; there is no `search:failing` key and the search row has no failure field. Searches call `read_listing`, not `read`, so a Platsbanken answer with `hits` renamed reads as complete and empty and closes every role of the search at once.
**What the pull does is not shown.** The settle's counts (boards, unanswered, incomplete, closed) go into the job result, which nothing renders; the Problems log is `/api/notices` only. The settle of 2026-09-30 10:06 closed 12,588 roles with one target unanswered and one incomplete, and the notices table stayed empty. Detail reads that fail, a 429 that stops them, `ats:complete` empty, `ats:swept`, `ats:narrowed` and the ceiling are state only. A board's size is set once and never again, so a size of 0 (a mistyped SmartRecruiters, Gem or Ashby slug) means "read whole" for good, and `set_board` keeps a board that lists nothing with a toast. A filtered read whose facets know none of the wanted values asks nothing and closes the whole board (`_runner.py:452`), and the line reads "site lists none of DK, SE: nothing asked" as if it were a fact about the site.
**The reader contract is declared but not enforced.** Of the `READS` traits only `posted`, `filters`, `complete`, `ceiling`, `empty`, `key` and `scope` are read at run time; `pay`, `remote`, `country`, `seniority`, `employment`, `title`, `teaser`, `page_size`, `places` and `text` are read by nothing and checked by nothing, so Platsbanken declares `remote="none"` while its rows set it, HR Manager declares `places="one"` and returns none, and seven readers record a robots.txt path they do not request (Oracle, Workday, Eightfold, Gem, Jibe, Phenom, Jobylon). Eight readers record "no robots.txt check needed". `config.py:171` still lists `jobindex` and `adzuna` as the only providers, so a Platsbanken starter search in config.yaml fails validation. A search provider does not plug in by existing: `PARAMS`, `clean_params` and the row key `company` are needed and not in the contract, and provider names are hard-coded in nine places. `discover._UNREADABLE` holds ten hosts that have modules. `undeclared()` returns nothing and its code paths are dead, as are `robots_page` and `ROBOTS_ANY_CASE`.
**The docs lag the code by a day of 224 commits.** `plugins/README.md` says SmartRecruiters and Workable have no text, that the pull reads 200 role pages per board (the enrich stage reads them, ranked roles first, under its own budgets), that Lever, Ashby, Greenhouse and Recruitee read one place, that a board over 100 pages is never complete, and its counts are of 2026-09-29. README.md says 175 readable boards (286 in the seed, 310 live) and that `config.example.yaml` documents every key: 21 keys it reads are missing, the whole `enrich:` block among them. `decisions.md` contradicts itself on the cascade (L175 lacks prep and enrich), Jobindex completeness (L73 against `complete="never"`), HR Manager (L109 says none attached; `hrmanager:teknologisk` has 7 open roles) and Novonesis, Darktrace and Criteo (L109 says Watchlist; all three are Workday boards). `open.md` is right on every item but the boilerplate one: `pipeline/` equals boilerplate HEAD, `auth/` lacks the phone commit, `deploy/` lacks the WSL scripts.
**Settings.** What a person changes while using the app is on the pages: agents, gates, weights, limits, fetch terms, stage switches, boards, reach, overrides, searches, the schedule, the account. What is config only is wiring (server, database, auth, workers, models, keys) plus the enrich depth, which the Runs page wrongly says is per agent. The model badge on Runs shows `extract.model` even when `agent.model` overrides it. Constants that decide coverage stay in code: `SMALL` 300, `STALE_DAYS` 21, the guard's 10%, `DETAIL_CAP` 200; the pages hard-code 300 in tooltips.
**Bugs outside ingestion, confirmed.** A board's own reach stores "UK" or "Germany" as a country code and, on a host that filters by ids, reads nothing and closes the board. A seniority range with no level in it (`level_from=senior&level_to=junior`) lists every level. Fetch the posting returns the role without the agent, so the reader's vote goes blank, and the row's excerpt goes blank for teaser-only roles. The toast's "all messages" link is a 404. Replace board always warns that roles will close. `_sync_copy_places` rewrites every copy-place row on every prep. A refused application status change leaves the refused status showing.
## Decisions taken for this plan
1. **Every whole read is guarded.** A read that lists under 10% of what the same read listed last time raises `Suspect` on every host, not only the suspect ones, when the last count was at least `SUSPECT_MIN` (10). The board is then failing with that reason, its roles stay open, and after `STALE_DAYS` of the same answer the read is accepted and the count reset, as Recheck resets it at once. A board that really shrank costs one Recheck or three weeks.
2. **A filtered read that could not ask remote does not close remote roles.** When the reach wants remote and the reader declares no remote filter, `stamp` records `remote_unasked`, `_close_unlisted` leaves `remote = 'remote'` roles open, and those close when the board has not listed them for `STALE_DAYS`. The line says "remote not asked on SmartRecruiters". Reading such boards whole instead is the owner's call (Bosch is about 70 requests a pull) and stays open in `open.md`; the 72 roles already closed reopen only if such a read lists them.
3. **A read that asks nothing is not a read.** When an `ids` dimension maps to no host id, the listing is incomplete and closes nothing, logged at warning, and the line says "nothing asked: not closing".
4. **Every target is guarded in the batch.** `run_batch` wraps each target: an exception after the read records the board as failing with its reason and moves on to the next target. The failing key is removed after `stamp`, not before the rows.
5. **Searches share the runner's bookkeeping.** `search.py` reads through `_runner.read` (guard included), records `search:failing:<target>` through `record_failure`, and the search row shows "not answering since" as the board row does. The settle reads failures for both sources.
6. **The settle speaks.** It raises one notice per pull naming what needs a look: every board or search unanswered or incomplete, every board that closed more than `CLOSE_NOTICE` (50) roles or more than half its open roles, and the totals. Its result key `failed` becomes `unanswered`. A finder that raises releases the pull claim.
7. **Narrowed boards close by age.** A role of a board read with terms closes when the board has not listed it for `STALE_DAYS`, the rule searches already have.
8. **A board's limits are words on its row, and a filter.** Each company row carries `limits`, computed from the reader's declaration and the board's state, and the Companies filter offers them: not readable yet (exists), failing, read incomplete, filtered by reach, remote not asked, narrowed by terms, size 0, text per role, no text, no pay, date not trusted, without text. The reader list on Sources shows every trait.
9. **Declarations are checked against fixtures.** The conformance test parses each reader's listing and detail fixtures and asserts every declared field; a missing fixture fails instead of skipping. `places` gains `none`. The search contract gains `PARAMS`, `clean_params` and the row key `company`. Each robots record names the paths the reader requests. Dead paths for undeclared modules and `robots_page` go.
10. **Docs say what the code does, once.** The shared limits live in `_runner.py`'s constants and the README table points at them; `READS` is the source for what a reader does and the per-host sections keep observations, quirks and examples; the cascade is `CASCADES`. The counts in `plugins/README.md` are refreshed and dated.
## Work packages
Each owns the files it names and nothing else; tests for a package live in the test files it names. Builders do not edit `docs/` or `plugins/README.md`: the planner folds the landed behaviour into the docs after the merges. `uv run pytest` and `uv run ruff check app plugins tests` must pass in the worktree before a package is done, and no package starts, stops or kills a server.
| WP | Model | Owns | Builds |
|---|---|---|---|
| R1 Losses | Opus | `plugins/readers/_runner.py`, `plugins/ats.py`, `plugins/search.py`, `app/jobs/pull.py`, `app/jobs/cascade.py`, `tests/test_ats.py`, `tests/test_readers.py`, `tests/test_pull.py` (new), `tests/test_search.py` (new or existing) | decisions 1 to 7, plus the mypy fixes in those files (`published_at` may be None, the `rows` redefinition, unused ignores) and the removal of the `declared()` branches now that every reader declares |
| R3 Bugs | Sonnet | `app/web/api.py`, `app/config.py`, `app/cli.py`, `app/jobs/stages.py`, `app/static/roles.js`, `app/static/toasts.js`, `app/static/companies.js`, `app/static/applications.js`, `app/static/jobs.js`, `config.example.yaml`, `tests/test_pages.py`, `tests/test_api_reach.py` (new) | the confirmed bugs: reach countries stored as ISO codes through `places.parse`, an empty seniority range answers 422, Fetch returns the role with the agent and `excerptOf` falls back to the teaser, the messages link, the Replace board compare, the refused status restored; `SearchSeed.provider` validated against `readers.PROVIDERS`; the Runs page's enrich sentence and model badge (`agent.model` wins); the cli and stages docstrings; `config.example.yaml` gains every key `app/config.py` and `desk/config.py` read. `_sync_copy_places` waits: `store.py` is being edited in the shared checkout |
| R4 Contract | Opus | `plugins/readers/__init__.py`, `plugins/readers/_contract.py`, `plugins/readers/<host>.py` (declarations and docstrings only), `app/jobs/discover.py`, `tests/test_readers_contract.py`, `tests/test_ats_<host>.py`, `tests/test_discover.py`, `tests/test_architecture.py`, `tests/fixtures/ats/` | decision 9: the fixture checks per declared field, `places="none"`, Platsbanken `remote="stated"`, HR Manager `places="none"`, the search contract, robots records naming the requested paths after reading each host's robots.txt again (the decision and date stay the owner's), the `_UNREADABLE` entries with modules deleted, `robots_page` and `ROBOTS_ANY_CASE` deleted with their test lines, the architecture test extended to `plugins/readers/*.py` with `._countries` allowed, a test that every `app/prep/hosts/<name>.py` names a reader and every reader stating words has a table, and the contract docstring corrected (Detail is read by `enrich`; the example `READS` matches `workday.py`; the touch points for a new reader listed: the module, the prep table, fixtures and tests, the README section, the `_UNREADABLE` entry to delete) |
| R2 Limits | Sonnet, after R3 merges | `app/jobs/limits.py` (new), `app/web/api.py` (`CompanyOut`, `ReaderOut`, `_company_outs` only), `app/static/companies.js`, `app/static/sources.js`, `app/templates/settings/sources.html`, `tests/test_limits.py` (new), `tests/test_pages.py` | decision 8: `limits.for_board(module, state, target, sub)` returns the words; `CompanyOut.limits` and `CompanyOut.board_open` (the board's own open count, beside the company's); the row shows the words after the reach line; the filter select gains one option per word; `ReaderOut` gains `complete`, `page_size`, `ceiling`, `teaser`, `fields`, `empty`; `sources.js` renders them |
| R5 Docs | Sonnet, now | `README.md`, `plugins/README.md`, `docs/open.md`, `docs/decisions.md`, `docs/filter-survey.md`, `docs/plan-hosts-wave-2.md` | decision 10 against main as it is: every correction the docs review listed, the counts of 2026-09-30, the boilerplate drift stated as it is, the contradictions in `decisions.md` resolved by marking the later decision, `open.md` gaining what this plan does not build (below) |
R1, R3, R4 and R5 start at once in worktrees made from main (`git worktree add ../jobboard-wt-<name> -b wp-<name> main`, then `uv sync --all-extras` there). R2 starts from main after R3 is merged, since both edit `api.py`.
## Not built here, to `open.md`
- Reading remote from the hosts that cannot filter on it (decision 2), and the 72 closed roles.
- Provider names hard-coded in nine places (`cli.py`, `dupes.py`, `sources.py`, `pages.py`, `sources.html`, `sources.js`, `api.py`, `posting.py`) instead of `readers.PROVIDERS`; `has_key` re-implements `resolve_key`.
- The compatibility names on `ats.py` (`_PARSERS`, `_parse_dt`, `_greenhouse_salary`, `_parse_teamtailor`, `_Refused`, `DETAIL_FIELDS`) that only tests reach for.
- `title="provisional"` cannot work while `DETAIL_FIELDS` has no `title`; wave 2's WP9 must own `_runner.py`.
- Some `posted="trusted"` declarations rest on the detail read (Workday, BambooHR, Rippling) or on a fallback the host moves (Greenhouse `updated_at`, Phenom `postedDate`).
- Dupes fold same-host roles with the same title and town without comparing text: 99 open copies share under 30% of their words with the kept role.
- Enrich never reads a role below the bar, so 349 textless roles are ranked on their title for good.
- A board's size is never re-measured by a pull; Recheck is the only way.
- Fetch terms are configured on no agent, so decision 7 is latent.
- A starred company on a big filtered board is scored on roles the fetch closes; All countries is the workaround.
- `SMALL`, `STALE_DAYS`, the guard share and `DETAIL_CAP` are code constants and the pages hard-code 300.
- `auth/` and `deploy/` lag the boilerplate; `desk/` lags news by four commits.
- The Jobindex robots record names `sort=` too, which `decisions.md` does not.
- `The todo list.md` holds items the code has done (Jobindex robots, Eightfold cap, places, aliases, teaser, ladder, hybrid on Ashby); the owner prunes it.
## Planner, after the merges
- Merge R1, R3, R4, R5, then start R2 and merge it; merge main into each branch first when the remote packages landed in between.
- Fold decisions 1 to 9 into `decisions.md` (Ingestion, The pages) and the limits words into `plugins/README.md`.
- Run one pull on the deployed server, read its settle notice, and check the Companies filter against the live boards.
- Delete this file.