{ "updated_at": "2026-09-19T05:48+00:00", "items": [ { "id": "decide-verify-additions", "kind": "decide", "title": "Three small additions to the verify rules (Q proceeds unless you object)", "detail": "Stream Q built verify with three things Decision 10 did not spell out.\n\n1. A tenth verdict, FETCH_ERROR, for a timeout or a server error: reported, never a failure, never a block. Without it a retailer's bad hour would either block a shop or vanish from the record.\n\n2. When verify finds a moved price it writes a new observation marked as coming from verify, so the live price is kept, not just noted.\n\n3. A block is not a flag on the shop; it is a failing check that a human clears, so clearing is itself a recorded decision.\n\nMy recommendation: accept all three.", "owner": null, "priority": null, "options": [ "accept all three (recommended)", "accept 1 and 3, no new observations from verify", "other" ], "assumption": "proceeding as if accepted", "links": [], "due": null, "created": "2026-09-05", "by": "Stream Q", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "decide-seoul-stays", "kind": "decide", "title": "Seoul is readable after all: keep it in the nineteen and tell Adam?", "detail": "The Shilla probe passed: a browser with our declared identity gets the full server-rendered product page. Two conduct points to know: the page's own scripts live under a robots-disallowed path, so we read the document without them (it is complete without them); and the second render allowed the Cloudflare challenge host as an asset host so the browser could load what the page asked for. No stealth, no identity change.\n\nLimits: their sitemap is empty and the category grids are drawn by disallowed scripts, so a compliant reader discovers through the home page and related-product rails, about 200 renders a run. That reaches part of the catalogue per run, not all of it. A full catalogue needs the partnership ask. Their robots file now names many AI and rendering crawlers; we are not named.\n\nIf you prefer a replacement airport instead, name two candidates on new platforms and a session probes them.", "owner": null, "priority": null, "options": [ "keep Seoul on the rendered fetch; tell Adam Monday it is confirmed (assumed)", "swap it for a replacement airport" ], "assumption": "keep Seoul", "links": [ ".logs/runs/shilla-probe-2026-09-05.log" ], "due": null, "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [ "P3" ], "weight": "blocking" }, { "id": "decide-shilla-price-tier", "kind": "decide", "title": "Which Shilla price is the price?", "detail": "The Shilla page shows a list price ($43), a discount price ($25.37) and a price for online members ($25.37). The collector records the discount price as what a walk-up traveller pays and the list price as the crossed-out price; the member tier is not published. One line to change if you want otherwise.", "owner": null, "priority": null, "options": [ "discount price (assumed)", "member price" ], "assumption": "discount", "links": [], "due": null, "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [ "R5" ], "weight": "costly" }, { "id": "decide-changi-tag-manager", "kind": "decide", "title": "Singapore only renders with its tag manager loaded. Acceptable?", "detail": "The iShopChangi storefront draws nothing until one Adobe Launch script has loaded, because the page's own code depends on it. With that one host allowed, the page draws and fetches its own inventory file, which we read as received. The sixteen analytics beacons it then tries to call (Adobe, Google, Facebook, Criteo, Bing, Clarity, New Relic and others) stay blocked, so nothing is reported to anyone. The reason is written in the collector.\n\nIf you disagree, Singapore has no honest path and joins the Cannes ask list.", "owner": null, "priority": null, "options": [ "acceptable: it is loading what the page needs to function, with our declared identity (assumed)", "not acceptable: Singapore goes to the ask list" ], "assumption": "acceptable", "links": [], "due": null, "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [ "R4" ], "weight": "blocking" }, { "id": "decide-shopify-refusal", "kind": "decide", "title": "The four Shopify shops refuse our identity at robots.txt. Accept dated prices, check the feed, or ask the operators?", "detail": "Montreal, Panama, Bogota and San Salvador all answer 403 to robots.txt for our declared reader and 200 to a plain request. Under the ratified policy (401/403 is a refusal) they record as blocked and launch on their last-seen prices from 22 Aug, with the date shown.\n\nOptions: accept and add them to the Cannes ask list; check whether the product feed itself is also refused (one request); or ask the operators (ARI for Montreal, Motta for the others) for permission, which becomes a recorded consent on the source. Nothing is redone whichever you choose; a consent record unblocks them.", "owner": null, "priority": null, "options": [ "accept: dated prices at launch, on the ask list (assumed)", "check the feed first", "ask the operators for permission" ], "assumption": "accept", "links": [], "due": null, "created": "2026-09-05", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "A13" ], "weight": "costly", "resolved": { "by": "planning session", "on": "2026-09-05", "note": "Overtaken by events: on the 5 Sep afternoon run all four Shopify shops served robots.txt and their feeds to our (repointed) identity and collected fresh prices (YUL 466, PTY 188, BOG 257, SAL 245). No decision needed; verify watches them. Dubai still answers 403 to a single robots read with the new identity." } }, { "id": "decide-bot-identity-hostname", "kind": "decide", "title": "The permanent hostname for our reader's identity page", "detail": "Every request we make carries a link to a page that says who we are and how to reach us. That hostname is baked into every retailer's logs forever, so it should sit on a zone you control and never move. The page itself is a separate static project (Decision 3), not part of the app. Name the host and a session builds it and repoints the reader.", "owner": null, "priority": null, "options": [ "a host on bowden.works", "a host on dutyfreeprofessor.com (only if the zone is yours)", "other" ], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "A10" ], "weight": "costly" }, { "id": "decide-client-surfaces-on-production", "kind": "decide", "title": "On production, do the client pages stay reachable?", "detail": "The quote, discussion, structure, to-do, sources and settings pages, and their API reads, exist for Adam and Mark. On production they can be switched off behind a flag, or kept behind the login with a client role so Adam and Mark keep commenting after the move. Sources and settings go behind the owner login either way.", "owner": null, "priority": null, "options": [ "off in production until the login exists", "behind the login with a client role" ], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "E4b" ], "weight": "blocking", "resolved": { "by": "planning 10 Sep", "on": "2026-09-10", "note": "rian's 10 Sep instruction: the client pages (/discuss, /structure, /quote, /todo, /settings) stay reachable behind the app's own login for Adam and Mark on the admin level (accounts plan .logs/planning/accounts-2026-09.md section 4.6); /sources and the kill switch stay the owner's (sources.manage), as build plan section 10 item 4 said" } }, { "id": "decide-hosting-figure", "kind": "decide", "title": "The hosting figure and the message to Adam", "detail": "$250 a month was the 1 Sep anchor; the quote page says $50 and promises real numbers before production. Stream E gives you a real figure by Tue 8, two ways: this app alone, and with headroom for a shared live-hosting box. Then decide whether production runs from Fri 11 at the real figure, or the $50 hold stands through soft launch and steps up when scheduled collection starts. Say it on the quote thread Adam opened on the environment line.", "owner": null, "priority": null, "options": [ "production from Fri 11 at the real figure", "$50 holds through soft launch, then steps up" ], "assumption": null, "links": [], "due": "2026-09-08", "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "E4" ], "weight": "blocking" }, { "id": "decide-where-collectors-run", "kind": "decide", "title": "Where the collectors run once production exists", "detail": "Three options, settled by the egress test: on the production host; on this server writing to production Postgres over Tailscale; or a separate runner with a reserved IP. Whichever it is also fixes which machine hosts the cron for the nightly audit and the verify runs.\n\nEvidence, 10 Sep (Stream E): from the droplet's address, text fetches at all 23 retailer hosts answered exactly as from the dev server (22 pages, Dubai refused on both), and a bounded real collection through the browser sidecar rendered Changi 5 of 5 and Seoul 5 of 5 with a Heathrow text-fetch control 10 of 10. Nothing in the collection path treats DigitalOcean's address differently today. Rian's stated preference: production should not depend on his home server. The remaining cost of the droplet option is memory: app 1 GB + sidecar 2 GB + Postgres 512 MB on a 4 GB box with 2 GB swap, one collection at a time.", "owner": null, "priority": null, "options": [ "on the droplet (assumed): collectors and cron live with the app; the sidecar fence applies there", "on the dev server writing to production over Tailscale: keeps the residential address, ties the live site to the home server", "a separate runner: a second box to operate, only if the droplet's address is ever refused" ], "assumption": "on the droplet", "links": [ ".logs/runs/egress-2026-09-10.md" ], "due": null, "created": "2026-09-05", "by": "plan review", "updated": "2026-09-10", "blocks": [ "E5" ], "weight": "costly", "resolved": { "by": "rian (in chat, 10 Sep)", "on": "2026-09-10", "note": "Collectors run on the droplet. Evidence: .logs/runs/egress-2026-09-10.md (text fetches identical at 23 hosts; rendered Changi 5/5, Seoul 5/5 from the droplet). Cron for audit and verify lands on bwlive with E5; the sidecar fence applies there." } }, { "id": "decide-zone-control", "kind": "decide", "title": "Who controls the dutyfreeprofessor.com zone at cutover", "detail": "Production needs the domain's DNS under our control: either the zone moves into your Cloudflare account, or Adam issues a scoped API token that is staged into a permissions-restricted file, never pasted in chat. Confirm which it is, and that the old WP Engine placeholder stops resolving at cutover.", "owner": null, "priority": null, "options": [ "zone is already in my Cloudflare account", "Adam issues a scoped token", "zone transfer needed" ], "assumption": null, "links": [], "due": "2026-09-08", "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "E4c" ], "weight": "blocking" }, { "id": "decide-page-types-18-sep", "kind": "decide", "title": "Which page types ship on 18 Sep", "detail": "Either all six page types where the coverage thresholds are met, with beauty categories switching on as their coverage crosses the bar, or category and category-at-airport pages move to the buffer week. One sentence, which also goes on the structure page and into the note to Mark. Mark's comments are due Thu 10, so decide after reading them.", "owner": null, "priority": null, "options": [ "all six where thresholds are met; beauty switches on as it qualifies", "category pages in the buffer week" ], "assumption": null, "links": [], "due": "2026-09-10", "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "B6" ], "weight": "blocking" }, { "id": "decide-ratify-standing-rules", "kind": "decide", "title": "Ratify four standing rules the sessions are already working under", "detail": "1. The BLOCKED rule: a shop that refuses us stays public on its last-seen prices with the date shown and a flag, rather than disappearing (Dubai is the big case).\n\n2. The robots policy: a robots file that answers 404 means open; 401 or 403 means refused; a server error means stop and retry later.\n\n3. Host cron for the nightly audit and the verify runs is owned by Stream E, and the collectors doc states plainly that this is not automated collection; collection stays hand-run, as told to Adam.\n\n4. The pages-2-and-later observations at the four Avolta stores that forbid query pagination were collected against their robots before the fix: keep them, dated, or purge them.\n\nWrite exceptions if any; otherwise \"all four\".", "owner": null, "priority": null, "options": [ "all four as stated", "exceptions (write them)" ], "assumption": "all four", "links": [], "due": null, "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "A13" ], "weight": "costly" }, { "id": "decide-scope-vs-capacity", "kind": "decide", "title": "Scope versus capacity: what gives way if time runs short", "detail": "The plan holds the sixteen promises plus unpaid back-office work, about twice what fits before 18 Sep.", "owner": null, "priority": null, "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-04", "by": "plan review", "updated": "2026-09-05", "resolved": { "by": "rian", "on": "2026-09-05", "note": "Everything stays in the plan. Unpaid work is ranked last, sits in the buffer week, and is pulled forward at the Fri 11 checkpoint if every wave-2 quote task is green. If time runs short, unpaid work drops before any quote line. The migration columns and the auth middleware stay regardless." }, "blocks": [], "weight": "info" }, { "id": "decide-fri-11-milestone", "kind": "decide", "title": "What the Fri 11 milestone means", "detail": "Adam approved production live, sixteen public, crawlable pages for Fri 11.", "owner": null, "priority": null, "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-04", "by": "plan review", "updated": "2026-09-05", "resolved": { "by": "rian", "on": "2026-09-05", "note": "Option (a): hold the date with the quote's own bar. Fresh drinks recollection minus the refusing shops, a human check of thirty pages, sixteen public on the demo host with the five refusing shops on dated prices, production live if E lands it. Verify's tripwire becomes the 18 Sep gate. Adam hears it in the Mon 7 reply pass." }, "blocks": [], "weight": "info" }, { "id": "do-changi-hand-check", "kind": "do", "title": "Hand-check the Singapore departure price before the first Singapore run", "detail": "Open the Johnnie Walker Blue Label 1000ml page on ishopchangi.com in your own browser, choose Traveller mode with At Departure, and confirm the price reads S$271.10 (non-traveller delivery shows S$333.87). The collector publishes the departure tier. Say \"confirmed\" here, or the price you saw.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [ "https://www.ishopchangi.com/en/product/johnnie-walker-blue-label-1000ml-40--mp00089136", ".logs/runs/changi-targets-2026-09-05.md" ], "due": "2026-09-06", "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [ "R4" ], "weight": "blocking" }, { "id": "do-reply-pass-adam", "kind": "do", "title": "The Monday reply pass to Adam's open threads", "detail": "About thirty minutes, one reply per thread. The wording is drafted in the build plan, section 10 item 15: Seoul confirmed possible; the browser reader; Dubai's refusal and the dated prices at launch; images and the list by Tue 8; the two new content asks; the hosting figure or the explicit hold; awards overrides via rian until the admin area. Plan task P3 is marked done when this is.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [ ".logs/planning/build-plan-2026-09.md" ], "due": "2026-09-07", "created": "2026-09-05", "by": "plan review", "updated": "2026-09-05", "blocks": [ "P3" ], "weight": "blocking" }, { "id": "do-public-base-url", "kind": "do", "title": "Set PUBLIC_BASE_URL in the app's environment file", "detail": "Since the crawlable-pages work, canonical, sitemap and structured-data URLs are built from PUBLIC_BASE_URL instead of trusting the request. It is not set yet, so they are relative and the startup log warns. Add one line to .app.env in your own shell (the value for this host is https://dutyfreeprofessor.demoing.info), then redeploy at the next checkpoint. Production gets its own value in E4b.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [], "due": "2026-09-06", "created": "2026-09-04", "by": "Stream B", "updated": "2026-09-05", "blocks": [ "B4", "A13" ], "weight": "blocking" }, { "id": "do-sidecar-firewall-rule", "kind": "do", "title": "Belt-and-braces firewall rule for the browser sidecar before production", "detail": "The sidecar refuses requests to numeric and private addresses by name, but a permitted retailer hostname that resolved to a private address would pass (DNS rebinding). Cheap fix that does not depend on code: a DOCKER-USER iptables rule on whichever host runs the sidecar, dropping traffic from the dutyfreeprofessor-render network to the host's own addresses and to private ranges. A firewall change, so it is yours; on this server it lands in /etc/iptables/rules.v4. A session drafts the exact rule when you ask.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [], "due": "2026-09-09", "created": "2026-09-05", "by": "planning session", "updated": "2026-09-05", "blocks": [ "E4b" ], "weight": "costly", "resolved": { "by": "rian (in chat, 10 Sep)", "on": "2026-09-10", "note": "Applied on bwlive 10 Sep: deploy/sidecar-firewall.sh as /usr/local/sbin/sidecar-firewall, systemd oneshot after docker.service, 13 DOCKER-USER rules; proof that the sidecar cannot reach 169.254.169.254 while retailers still render goes on the E7 go-live checklist." } }, { "id": "do-thirty-page-check", "kind": "do", "title": "The human check of thirty product pages before the nineteen switch on", "detail": "Part of the Fri 11 bar you chose: after the drinks refresh, open thirty product pages from the audit's list and confirm price, size and shop against the retailer page. Stream Q's checklist generator produces the list; note anything wrong here and it becomes an issue.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [ "main/scripts/review-checklist.py" ], "due": "2026-09-11", "created": "2026-09-05", "by": "planning session", "updated": "2026-09-05", "blocks": [ "A13" ], "weight": "blocking" }, { "id": "do-read-marks-comments", "kind": "do", "title": "Read Mark's comments on the structure proposal and settle the structure", "detail": "Mark has the structure page and the to-do page as of today; his comments are due Thu 10. Read them, decide what changes, and answer the page-types question above. If nothing arrives by Fri 11, the sessions build to the proposal as written.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [], "due": "2026-09-10", "created": "2026-09-05", "by": "planning session", "updated": "2026-09-05", "blocks": [ "B6" ], "weight": "blocking", "resolved": { "by": "rian", "on": "2026-09-09", "note": "Read 9 Sep, replied on every thread; Mark and Adam have both replied back on the page." } }, { "id": "do-dfp-devdb", "kind": "do", "title": "Keep the scratch database until Stream R's rehearsal is done", "detail": "Stream Q left a copy of a dump in a scratch container (dfp-devdb) for migration rehearsals; the security audit lists the container as orphaned. Keep it up through Stream R's R1 night: O2 rehearses migration #4 on it as dfp_r (up, backfills twice, down, up) and L10 runs the local server against dfp_r; the session drops only dfp_r. Remove the container (docker rm -f dfp-devdb) only after R1 has handed over green and ready; the earlier scratch databases (dfp_q, dfp_a, dfp_b, dfp_c, dfp_d) can go with it.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [], "due": "2026-09-12", "created": "2026-09-05", "by": "planning session", "updated": "2026-09-10", "blocks": [ "O2", "L10" ], "weight": "costly" }, { "id": "issue-dubai-refuses-by-name", "kind": "issue", "title": "Dubai refuses our reader by name at the Akamai edge", "detail": "Since 3 Sep: our declared identity gets 403, a generic browser identity gets 200, robots.txt refused too, error page from Akamai. Last good run 22 Aug with the same identity, so their rules changed. Dubai is about 39 percent of launch products and 77 percent of barcodes. Deliberately not bypassed. Path decided: the identity page becomes its own static project, the reader is repointed once it serves, the ask goes to Dubai when you judge the relationship ready, and Dubai launches on dated 21 Aug prices. Open: the hostname decision and your Dubai conversation.", "owner": null, "priority": "P1", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [], "weight": "costly" }, { "id": "issue-launch-prices-stale", "kind": "issue", "title": "Every launch price is stale until the drinks refresh runs", "detail": "Newest observation anywhere in the sixteen is 25 Aug; Dubai 21 Aug. The drinks refresh of the sixteen minus the refusing shops is Stream A's first task tonight (A10), after which verify runs its first twenty-page check the next morning. The last-checked date on every price keeps this visible to visitors, which is the point.", "owner": "A", "priority": "P1", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "A13" ], "weight": "blocking", "resolved": { "by": "planning session", "on": "2026-09-05", "note": "5 Sep refresh: every source except Dubai (refuses) has prices dated 5 Sep; deployed in 0.33.0" } }, { "id": "issue-sin-icn-first-runs", "kind": "issue", "title": "Singapore and Seoul: first real runs and their discovery limits", "detail": "Both collectors are built and the sidecar is deployed. Still to do: the first twenty-page run of each in an announced window after your Changi hand check; reading the first raw records; then the discovery question. Shilla can only be walked through the home page and related-product rails (its grids are drawn by disallowed scripts), and Changi's full catalogue needs a category-page harvest that is unprobed. Singapore has no barcodes anywhere, so it matches on brand, name and size only.", "owner": "A2", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [ "R4", "R5" ], "weight": "costly", "resolved": { "by": "planning session", "on": "2026-09-05", "note": "First runs done 5 Sep: Seoul clean (18 prices), Singapore 17 prices then a 403 at page 19; the pace decision is decide-singapore-answered-403" } }, { "id": "issue-beauty-name-size-misread", "kind": "issue", "title": "A number in a beauty product's name is read as its size", "detail": "Found by the first audit: Extime \"DELICIA DRENCH 59\" stored as 5,924 ml and \"CHEIROSA 76\" as 7,624 ml; two Extime drinks rows carry the old 7-litre misread. The audit's oversize metric lists them with the threshold pinned at today's six, so a new one shows red. Fix the size parser on beauty names and re-derive the four rows.", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "Stream Q", "updated": "2026-09-05", "blocks": [ "B5" ], "weight": "costly", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "3d5f3f1: the names were innocent; the page declares capacity 7624 ml and prices per 100 ml (implies 240). The cross-check now reads that live shape and refuses the size; 'backfill implausible_sizes' clears the four stored rows after the deploy" } }, { "id": "issue-shopify-drinks-filter-english", "kind": "issue", "title": "The Shopify drinks filter only knows English shelf names", "detail": "\"liquor\" is a hint but \"licor\" is not, so Panama's own Licores shelf is invisible: only 181 of 395 items pass. Spanish shelf names (Vinos, Rones, Champanas, Cordiales) fail everywhere, so liquor is being dropped at Panama and Bogota. Part of the beauty widening task (A6).", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "A6" ], "weight": "costly", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "3d5f3f1: shelf_vertical() matches the shop's own shelves in English and Spanish (Licores, Vinos, Rones, Champanas, Cordiales...); tests in test_beauty_widening.py" } }, { "id": "issue-duplicate-products", "kind": "issue", "title": "110 product rows are duplicates of another row", "detail": "52 groups measured 3 Sep. A bottle appears as two products with two prices instead of one product with a comparison, which also corrupts the aggregate-offer markup the SEO plan relies on. Fixed as recorded merges with a forwarding id, never deletes (A9), before brand pages ship.", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "B5" ], "weight": "blocking", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "758233e: 'backfill merges' after 'rederive' folds every group sharing a key without a barcode, attribute or set conflict (40 groups, 44 rows on the 5 Sep dump); the rest are merge_candidates for the Mon 21 review; merged ids 301 to their survivor" } }, { "id": "issue-brand-names-unnormalised", "kind": "issue", "title": "Brand names are not normalised, and brand pages depend on it", "detail": "\"Don Julio\", \"Don Julio Tequila\" and \"Don Julio®\" are three brands; \"Moet & Chandon\" and \"Moët & Chandon\" are two; six pairs differ only in case or accent. Each would become a competing brand page. Same family: name matching splits when there is no barcode, which undercounts comparisons (safe direction, but thin and sloppy). Brands become a table with a fold rule in migration #3 (A8) and the fold backfill (A9); the first audit counted 122 folds.", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "B5" ], "weight": "blocking", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "758233e: brands table (migration f3a4b5c6d7e8) + 'backfill brands' (2,215 rows from the spellings; mixed case shown over caps); match_key v2 folds the brand, 'rederive' re-keys 2,512 rows" } }, { "id": "issue-uncategorised-products", "kind": "issue", "title": "About 260 launch products have no category and fall out of the structure", "detail": "Measured 3 Sep; some are the beauty products already collected at Athens. An idempotent backfill assigns them (A9).", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [ "B6" ], "weight": "costly", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "758233e: 'backfill categories' (widened rules, Spanish shelves, Makeup, single-category houses): launch uncategorised 260 -> 121 on the dump, 1,032 rows overall; the remaining 121 have nothing to go on and stay honest" } }, { "id": "issue-scheduler-freshness-alarm", "kind": "issue", "title": "No scheduler and no freshness alarm yet", "detail": "Prices must be current in late September. Collection stays hand-run, but the nightly audit, verify after any collection, the weekly verify, and an alert when a store returns far less than its last run (the Heathrow lesson) all need a cron home, decided by where the collectors run. Stream E task E5.", "owner": "E", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-27", "by": "issues register", "updated": "2026-09-05", "blocks": [ "E5" ], "weight": "blocking" }, { "id": "issue-header-mirror-rule", "kind": "issue", "title": "When the header or announcement bar changes shape, update its server-side mirror in the same deploy", "detail": "The server-rendered product page draws a copy of the header so the page does not jump when the app takes over (layout shift measured at zero). The mega menu (C2) and any announcement-bar change alter that shape; the mirror lives in the SEO service and must change in the same deploy. A standing rule for Stream C and Stream B.", "owner": "C", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-04", "by": "Stream B", "updated": "2026-09-05", "blocks": [ "C2" ], "weight": "costly", "resolved": { "by": "Stream C", "on": "2026-09-05", "note": "Superseded by issue-update-header-html-mirror-for-the-mega-menu, filed with the exact markup in the C2 commit; the standing rule lives in SiteHeader.css (comment at .site-nav__group) and SEO.md" } }, { "id": "issue-hide-blocked-shop-rows", "kind": "issue", "title": "Hide or date the rows of a publication-blocked shop on the public site", "detail": "Decision 10 says a correctness failure hides the affected rows or shop until a human clears it. Verify now knows which shops are blocked, but the latest-price queries do not yet exclude their observations or show them as dated. Until that lands the block is visible only in verify-status. Owner: whoever owns the catalogue queries (B or A).", "owner": "B", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "Stream Q", "updated": "2026-09-05", "blocks": [ "A13" ], "weight": "blocking", "resolved": { "by": "Stream B", "on": "2026-09-05", "note": "5a5acba: catalog_queries.publishable(db) hides a blocked shop from every catalogue query, /api/stats, the sitemap and IndexNow; rehearsed on scratch copy dfp_b (JFK hidden while blocked, restored on clear); tests/test_publication_block.py. /trip keeps its own clause: separate issue." } }, { "id": "issue-q-touches-in-a-files", "kind": "issue", "title": "Review Stream Q's three small edits in Stream A's files", "detail": "Q registered its audit and verify subcommands in the CLI, added a per-reason skip-count column to collection runs, and made ingest count skips by reason. All tested; listed for A's review at its next session, not a bug.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "Stream Q", "updated": "2026-09-05", "blocks": [], "weight": "info", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "reviewed 5 Sep: register_quality in cli.py, skip_counts on CollectionRun, count_skip in ingest are as they should be; kept" } }, { "id": "issue-robots-pattern-regex", "kind": "issue", "title": "Expose the robots pattern-to-regex step so the fetcher stops mirroring it", "detail": "The fetcher copies four lines of the robots matcher to apply a host's Disallow rules to a rendered page's own requests; a test pins the two equal. Exposing one function from robots.py removes the copy.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-05", "by": "Stream A2", "updated": "2026-09-05", "blocks": [], "weight": "info", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "9c57e5e: robots.pattern_regex() is public; fetch.py's import swap is A2's (issue filed)" } }, { "id": "issue-agents-robots-pointer", "kind": "issue", "title": "agents.md still points the robots rule at the Heinemann collector", "detail": "The matcher now lives in collectors/robots.py and every collector calls it. One line in agents.md to repoint; the rule text is right.", "owner": "DOCS", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-04", "by": "Stream A", "updated": "2026-09-05", "blocks": [], "weight": "info", "resolved": { "by": "Stream N", "on": "2026-09-09", "note": "Already fixed: agents.md's robots rule names no collector (the 5 Sep tier-1 trim kept the lesson and dropped the name); found in the 10 Sep issue-log sweep." } }, { "id": "issue-extime-paris-not-cdg", "kind": "issue", "title": "Extime is Paris (CDG and Orly together), not CDG alone", "detail": "The storefront is one Paris tenant; the only terminal signal is the combined value and there is no per-airport sitemap, so the location is named for both with code CDG. If Adam needs CDG-only pricing that is an unmet requirement to raise with him, not a bug.\n\nWidened 15 Sep: this is the case that breaks 'a storefront belongs to one place', and so it constrains the location model. Orly does not exist in our data and CDG's 7,036 listings are really Paris's. See .logs/planning/places-and-shops-2026-09-15.md section 2.3.\n\nCatalogue decisions, 15 Sep (.logs/planning/catalogue-model-decisions-2026-09-15.md section 2.11, section 7): the place model that answers this is decided in direction and built after Cannes, before any non-airport shop is collected. The delivery walkthrough does not need it: Adam hears at P6 that Extime's prices are Paris's (the W6 naming task, where the Extime issue resolves) and that terminals and specialty shops within one airport are not yet distinguished, coming after Cannes.", "owner": null, "priority": null, "options": [], "assumption": null, "links": [ ".logs/planning/catalogue-model-decisions-2026-09-15.md", ".logs/planning/places-and-shops-2026-09-15.md" ], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-15", "blocks": [ "P6" ], "weight": "costly" }, { "id": "issue-extime-untested-paths", "kind": "issue", "title": "Extime: a few paths handled defensively but never seen for real", "detail": "An out-of-stock product's rendering, a genuine multi-variant product, and the French tree; also the services sitemap returns a server error, so sitemap coverage is not catalogue coverage there. The collector skips rather than guesses in each case.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-03", "by": "Stream A", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "issue-gratien-meyer-jfk", "kind": "issue", "title": "Watch: Gratien & Meyer at JFK, $77 against about $21 in Europe", "detail": "Both prices verified real on the retailer's pages. Across 304 shared JFK/Europe products the median ratio is 1.07 and this bottle is the maximum at 3.74, so almost certainly the retailer's own entry error. Kept on its page (it is the published price), excluded from featuring by the corroboration rule. Does it correct on the next JFK crawl?", "owner": null, "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-25", "by": "rian", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "issue-variant-listings-no-barcode", "kind": "issue", "title": "Per-size listings from configurable tiles carry no barcode", "detail": "A size row emitted from a configurable tile has no barcode, so image enrichment cannot attach a photo and cross-shop matching falls back to names, which is what splits. Possible fix: read per-variant barcodes from the tile's configuration data when present.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-25", "by": "rian", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "issue-ghost-listings", "kind": "issue", "title": "Ghost listings at stores that could not be re-read", "detail": "The 25 Aug purge removed superseded plain listings only where a per-size sibling exists at the same store; stores whose tiles could not be re-read keep old listings, so a few barcode-less ghosts survive at hidden locations. Self-heals when those stores next crawl clean; the same purge pattern covers the reverse case if a tile ever goes from multi-size to single-size.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-25", "by": "rian", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "issue-medal-artwork-missing", "kind": "issue", "title": "Silver and bronze medal artwork missing for four wine competitions", "detail": "Cards fall back to the text tag, which works; sourcing the artwork finishes the set.", "owner": "F", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-25", "by": "rian", "updated": "2026-09-05", "blocks": [], "weight": "info", "resolved": { "by": "Stream N", "on": "2026-09-09", "note": "Landed: nine badges from the competitions' own 2025 artwork (NYIWC, BIWC, MIWC silver and bronze; AIWC gold, silver, bronze), 160 px transparent like the set; test_medal_artwork.py pins every competition has all four tiers." } }, { "id": "issue-award-aging", "kind": "issue", "title": "Award aging: demote or hide awards older than a year", "detail": "Your idea from the board comments: older awards fade on listings to encourage brands to re-enter each season. Business-model relevant; belongs in the awards picker work (Stream F).", "owner": "F", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-08-27", "by": "rian", "updated": "2026-09-05", "blocks": [ "F2" ], "weight": "costly", "resolved": { "by": "Stream F", "on": "2026-09-05", "note": "Stated as a proposal with an on/off decision in the strategy for Adam (/discuss card 5, notes/awards-strategy-for-adam-2026-09-05.md); the switch exists as award_picker.AGING_ENABLED (off) with tests for the on state (e2d50a3); Adam's answer is do-adam-awards-strategy" } }, { "id": "issue-back-office-parked", "kind": "issue", "title": "The back office: six mechanisms parked with their columns already in place", "detail": "AI-assisted QA (a local model proposes brand merges, draft descriptions and likely inconsistencies; humans confirm in batch); per-source identity mode with a consent record; human data-entry fallback with a likely-stale flag; the merge review queue with recorded merges; verified-field semantics through the single overrides record; the reverification queue with scoring and human-fed re-ranking. The columns land in migrations #1 to #4 so nothing is thrown away; the behaviour waits for the back office after Cannes (plan section 4).", "owner": null, "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "created": "2026-09-04", "by": "rian", "updated": "2026-09-05", "blocks": [], "weight": "info" }, { "id": "do-add-the-dns-record-for-bot-dutyfreeprofessor-com-in-clou", "kind": "do", "created": "2026-09-05", "by": "planning session", "title": "Add the DNS record for bot.dutyfreeprofessor.com in Cloudflare", "detail": "The zone sits in Adam's Cloudflare account (you have access, the gateway's token does not), so this one record is by hand. In the dutyfreeprofessor.com zone add: Type CNAME, Name bot, Target mosiah.riverway.ca, Proxy status DNS only (grey cloud), TTL Auto. Caddy issues the certificate on the first visit within a minute or two. Check: open https://bot.dutyfreeprofessor.com and see the identity page.\n\nUntil this resolves, every request the reader sends carries a link that does not load, which is what the identity page exists to prevent. Tonight's drinks refresh should go out after it.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [ "https://bot.dutyfreeprofessor.com" ], "due": "2026-09-05", "blocks": [ "A10" ], "weight": "blocking", "updated": "2026-09-05" }, { "id": "do-make-bot-dutyfreeprofessor-com-deliver-to-you", "kind": "do", "created": "2026-09-05", "by": "planning session", "title": "Make bot@dutyfreeprofessor.com deliver to you", "detail": "The identity page names bot@dutyfreeprofessor.com as the contact for retailers (to ask for a slower pace, an exclusion, or a direct feed). It needs to reach a real inbox. Easiest: Cloudflare Email Routing on the dutyfreeprofessor.com zone (free): enable it, add a custom address bot@ that forwards to your inbox, and let Cloudflare add the MX and TXT records it asks for. Mail to that address is rare but every message is a retailer relationship.\n\nIf you would rather publish a different address, say which and the page changes in a minute.", "owner": "rian", "priority": null, "options": [], "assumption": null, "links": [], "due": "2026-09-08", "blocks": [ "A13" ], "weight": "costly", "updated": "2026-09-05" }, { "id": "issue-watch-the-four-shopify-shops-refused-us-on-4-sep-and-acc", "kind": "issue", "created": "2026-09-05", "by": "planning session", "title": "Watch: the four Shopify shops refused us on 4 Sep and accepted us on 5 Sep", "detail": "On 4 Sep all four answered 403 to robots.txt for our identity; on the 5 Sep afternoon refresh, run with the identity link repointed to bot.dutyfreeprofessor.com, all four served robots.txt and their product feeds and collected normally. Either the refusal was transient or the platform's protection scored the old, non-resolving identity link. Nothing to do unless it recurs; if verify sees BLOCKED on any of them again, note whether the identity page was reachable at the time.", "owner": "Q", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "blocks": [], "weight": "costly", "updated": "2026-09-05" }, { "id": "decide-singapore-answered-403-on-the-19th-page-of-its-first-run", "kind": "decide", "created": "2026-09-05", "by": "planning session", "title": "Singapore answered 403 on the 19th page of its first run. Retry slower once, or treat as refused?", "detail": "The first Singapore run rendered 18 product pages cleanly at about ten seconds each (17 prices stored, departure tier), then the 19th page took 49 seconds and came back 403 with a 512-byte body and none of the page's own data calls. That shape (short body, after a steady run of requests) looks like the shop's edge protection reacting to the pace, not a rule about that product. Under our policy a 403 is a refusal, so the collector stopped and recorded the source as blocked. Seoul's first run in the same window was clean: 18 prices from 20 pages.\n\nTwo honest options. Retry once, later, at a slower pace (for example thirty seconds between pages, which is still our declared identity with the same rules) and see whether it holds; if it refuses again, Singapore joins the ask list. Or treat this first 403 as the answer and stop now. Either way the 17 prices already stored are real and dated. My recommendation: one slower retry, tomorrow morning, twenty pages, and stop for good on a second 403.", "owner": null, "priority": null, "options": [ "one slower retry (thirty-second pace), then stop for good on a second 403 (recommended)", "treat it as refused now; Singapore goes to the Cannes ask list" ], "assumption": "no retry until you say", "links": [ ".logs/runs/changi-first-2026-09-05.log" ], "due": null, "blocks": [ "R4" ], "weight": "blocking", "updated": "2026-09-05", "resolved": { "by": "rian (in chat, 13 Sep)", "on": "2026-09-13", "note": "Retry at a slower pace and find the rate they accept. Run 13 Sep on bwlive: collect --source ishopchangi-sin --limit 20 --delay 30. If it holds, the pace becomes the source's own (Source.delay_seconds / Changi.render_floor_seconds); a second refusal ends Singapore for good and it joins the Cannes ask list. Rian's direction beyond this run: crawl continuously rather than fast; keep the pace per collector as something a person adjusts, with notes; record when and at what pace a collector is refused; measure how often prices change per collector so the cadence is chosen from evidence." } }, { "id": "issue-singapore-the-run-pace-may-need-to-slow-the-block-and-st", "kind": "issue", "created": "2026-09-05", "by": "planning session", "title": "Singapore: the run pace may need to slow; the block-and-stop worked as designed", "detail": "First run: 18 pages clean at the ten-second floor, then a 403 at page 19 (49 s, 512-byte body, no data calls). If rian approves a slower retry, make the per-source pace configurable (render_wait floor per source, thirty seconds for Singapore) and record the outcome in the run log. Seoul: 18 prices from 20 renders, no refusals, rails-only discovery as designed.", "owner": "A2", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "blocks": [ "R5" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "Stream A2", "on": "2026-09-05", "note": "83bb3a4: per-source floor built (Changi.render_floor_seconds, None until rian's decision; 30.0 on a yes), pace logged per render as wait=; behaviour unchanged tonight" } }, { "id": "do-adam-awards-strategy", "kind": "do", "created": "2026-09-05", "by": "Stream F", "title": "Get Adam's answer on the awards rules and the aging switch (/discuss card 5)", "detail": "The one-page strategy is published on the review page as decision card 5 (item 40), full text in its thread, and kept at notes/awards-strategy-for-adam-2026-09-05.md. Three answers wanted: a yes to the six rules (latest result per competition shown, highest level leads, ties by year then the traveller's airports then judges' score, pin by competition+year+medal, doubtful matches show nothing); aging on or off at launch; and whether he would rather the best medal ever won stayed on the page instead of the latest per competition.\n\nCost of reversal: the picker is built to the rules as written with aging off. Switching aging on is a constant; switching rule 2 to best-ever is one ordering function and a re-check of every product page's medal list.", "owner": "rian", "priority": null, "options": [ "rules as written, aging off (assumed)", "rules as written, aging on", "best-ever medal per competition instead of latest" ], "assumption": "rules as written, aging off", "links": [ "notes/awards-strategy-for-adam-2026-09-05.md" ], "due": "2026-09-11", "blocks": [ "F2" ], "weight": "costly", "updated": "2026-09-05" }, { "id": "issue-article-pages-need-seo-py-and-main-py-to-know-articles-p", "kind": "issue", "created": "2026-09-05", "by": "Stream D", "title": "Article pages need seo.py and main.py to know /articles: page route, head, body, sitemap; add the two App.tsx routes in the same commit", "detail": "Stream D has the articles table (commit 89f33a0), the API (GET /api/articles?kind=article|airport_writeup|category_intro&limit&offset, /api/articles/{slug}, /api/articles/airport/{iata}, /api/articles/category/{name}; published only, drafts 404) and the SPA pages web/src/pages/ArticlesPage.tsx and ArticlePage.tsx plus web/src/api/editorial.ts (hooks, reads window.__DFP_ARTICLE__ as a seed). The SPA catch-all in main.py 404s any path seo.is_known_route() does not know, and tests/test_seo.py requires a STATIC_HEADS path and its App.tsx to land TOGETHER, so the head and the two Route lines cannot come from two workers in two commits. Please land all of this in one B commit:\n\n1. web/src/App.tsx: lazy imports like the others, then } /> and } />. 2. app/main.py: a page route /articles/{slug} (GET, HEAD) next to the product and airport routes calling seo.article_head(db, slug); not_found() when it returns None, so a draft or unknown slug is a real 404 rather than the shell. 3. app/services/seo.py: STATIC_HEADS['/articles'] (title, description, canonical /articles) and article_head(): row = app.services.editorial.article_by_slug(db, slug); out = editorial.article_out(row) (ArticleOut: title, description, path, body_html, standfirst, category, published_at, updated_at, hero_image); canonical = out.path; JSON-LD Article (headline, description, datePublished, dateModified, publisher {'@id': '/#organization'}, mainEntityOfPage) plus BreadcrumbList; body = the ArticlePage markup, class for class:
{category or 'Article'}

..

[

..

]

Published {date}

[
]
{body_html}
; seed window.__DFP_ARTICLE__ = out; last_modified = updated_at. 4. sitemap_entries: editorial.sitemap_rows(db) gives [(path, lastmod)] for published articles; add /articles to the static paths. 5. RSS (B7 shipped in eb85201): editorial.feed_items(db, limit=20) gives ArticleOut rows newest first if you want an articles feed beside the products one. 6. tests/test_seo.py TestRouteInventory: add '/articles/' to the tuple of prefixes served by their own route. 7. Airport pages: editorial.airport_writeup(db, iata) -> Article|None; embed editorial.article_out(row) in AirportDetail or drop (web/src/components/EditorialBlock.tsx; fetches /api/articles/airport/; renders nothing when null) into AirportPage.tsx. Category pages (B6): editorial.category_intro(db, name) / .", "owner": "B", "priority": "P2", "options": [], "assumption": null, "links": [ "main/app/services/editorial.py", "main/app/routers/articles.py" ], "due": null, "blocks": [ "D2" ], "weight": "blocking", "updated": "2026-09-05", "resolved": { "by": "Stream B", "on": "2026-09-05", "note": "69108f5: /articles static head, /articles/{slug} route (GET/HEAD, real 404 for drafts), seo.article_head with Article + BreadcrumbList and the ArticlePage body class for class, __DFP_ARTICLE__ seed, sitemap rows and feed items from editorial, the two App.tsx routes (ArticlePage in the main bundle so the server body is redrawn, not blanked). Airport write-ups ride in AirportDetail.writeup and render on the airport page server- and client-side with EditorialBlock's classes; category intros wait for B6. Rehearsed on dfp_b at head. D2 can proceed: import Adam's hand-ins after the deploy." } }, { "id": "issue-register-the-indexnow-subcommand-in-app-cli", "kind": "issue", "created": "2026-09-05", "by": "Stream B", "title": "Register the indexnow subcommand in app.cli", "detail": "app/cli.py (Stream A's file): add 'from app.cli_pages import register as register_pages' and 'register_pages(sub)' next to register_quality(sub). Until then the command runs as 'python -m app.cli_pages indexnow' (documented in main/docs/SEO.md) and the RUNBOOK's generated CLI reference does not list it. Two lines; nothing else changes.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "73362e1: register_pages(sub) in app.cli; 'python -m app.cli indexnow' works" } }, { "id": "decide-ai-training-stance-in-robots-txt-no-for-now-search-and-a", "kind": "decide", "created": "2026-09-05", "by": "Stream B", "title": "AI training stance in robots.txt: no for now (search and AI answers yes)", "detail": "robots.txt now carries Content Signals and per-bot groups from one switch table (main/app/services/robots_policy.py CONTENT_SIGNALS). Assumed: search=yes, ai-input=yes (AI assistants may read and cite pages, which is the AEO goal), ai-train=no (GPTBot, ClaudeBot, CCBot, Bytespider, Applebot-Extended, cohere-ai are disallowed; Google-Extended and meta-externalagent stay open because they also govern grounding). Flipping ai-train is one word in that dict and takes effect at the next deploy; nothing waits on it. Adam may have a view: training gives nothing back, but some publishers open it for reach.", "owner": null, "priority": null, "options": [ "keep: search yes, ai-input yes, ai-train no (assumed)", "open training too" ], "assumption": "ai-train=no", "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05" }, { "id": "decide-a-licence-and-a-bulk-download-for-the-public-dataset-pag", "kind": "decide", "created": "2026-09-05", "by": "Stream B", "title": "A licence and a bulk download for the public dataset page?", "detail": "/data describes the price dataset with schema.org Dataset markup. It states no licence and offers no download, because neither is decided: an invented licence is a promise, and a bulk file of retailers' prices changes the legal posture (facts are fine to show per page with their date and a link back; a downloadable corpus is a different product). Assumed for launch: no licence line, no distribution; people link to pages. If you want a licence stated (for example CC BY 4.0 for the observations) or a CSV export, say so and it is a small addition to seo.py head_for_dataset plus one route.", "owner": null, "priority": null, "options": [ "no licence, no download (assumed)", "state a licence", "state a licence and offer a CSV" ], "assumption": "no licence, no download", "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05" }, { "id": "issue-architecture-md-request-path-server-bodies-are-no-longer", "kind": "issue", "created": "2026-09-05", "by": "Stream B", "title": "ARCHITECTURE.md request path: server bodies are no longer product-only", "detail": "main/docs/ARCHITECTURE.md step 3 says the body is rendered server-side 'for product pages'. Since B4/B7 the airport pages (/airports/-) and the data page (/data) get their bodies the same way, and the process also serves the machine surfaces (/robots.txt with per-bot policy, /sitemap.xml, /feed.xml, /llms.txt, the IndexNow key file). One sentence each; the mechanism is documented in main/docs/SEO.md, so link rather than explain.", "owner": "DOCS", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream B", "on": "2026-09-05", "note": "done in the B commit after 00cf418 (structure rows to built): ARCHITECTURE.md step 3 now names the product, airport, brand, article and data bodies and the machine surfaces, linking SEO.md." } }, { "id": "issue-fetch-disallow-regexes-should-import-robots-pattern-rege", "kind": "issue", "created": "2026-09-05", "by": "Stream A", "title": "fetch.disallow_regexes should import robots.pattern_regex instead of mirroring it", "detail": "robots.pattern_regex() is public since 9c57e5e (Stream A). In app/services/collectors/fetch.py, disallow_regexes() can become [pattern_regex(p) for p in robots.disallows]; tests/test_robots.py::TestPatternRegex pins the two equal until then. One-line swap in A2's file.", "owner": "A2", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream A2", "on": "2026-09-05", "note": "6a1fc91" } }, { "id": "issue-audit-must-skip-merged-products-and-re-pin-two-threshold", "kind": "issue", "created": "2026-09-05", "by": "Stream A", "title": "Audit must skip merged products and re-pin two thresholds after migration #3", "detail": "After the evening deploy runs 'rederive' and 'backfill merges' (A9), products with merged_into_id set are tombstones: audit.py should exclude them from every product metric (duplicate_groups, brand_folds, oversize_singles, uncategorised) or it counts forwarded rows. Measured on a clean copy of the 5 Sep dump: oversize_singles 6 -> 2 after 'backfill implausible_sizes'; duplicate_groups (mergeable) -> 0 after 'backfill merges', with 223 gtin_differs/set groups left as merge_candidates; brand_folds -> 0 once brands rows exist. THRESHOLDS should be re-pinned to the post-backfill numbers; the Mon 21 checklist can read merge_candidates for its 'right product' list.", "owner": "Q", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "blocks": [ "Q5" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "Stream Q", "on": "2026-09-05", "note": "4f712c5: tombstones excluded from every product metric; duplicates read through merges.duplicate_groups; brand_folds a pending-fold metric at 0; oversize 2, duplicates 0; merge_candidates list + checklist section 6; 16/16 green on dfp_b" } }, { "id": "issue-brand-pages-the-brands-table-is-ready-slug-name-canonica", "kind": "issue", "created": "2026-09-05", "by": "Stream A", "title": "Brand pages: the brands table is ready (slug, name, canonical_id); Makeup is a new category", "detail": "Migration f3a4b5c6d7e8 + 'backfill brands' give brands(id, slug UNIQUE, name, canonical_id NULL) and products.brand_id (2,215 rows on the dump; mixed-case display names). A brand page should key on brands.slug and join products.brand_id, never on the products.brand text. Products with merged_into_id set are tombstones: exclude them from lists (resolve_product_id already forwards the detail routes). 'backfill categories' adds the category value 'Makeup' (vertical beauty; 241 rows on the dump), so category lists and structure.ts should know it. test_site_routes.py::test_identity_resolver_is_a_pass_through_until_migration_3 is stale in name only (still true without a session).", "owner": "B", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "blocks": [ "B5" ], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream B", "on": "2026-09-05", "note": "Overtaken by B5 (7094b48): brand pages key on brands.slug and join products.brand_id via brand_ids (house + aliases), never the brand text; list_products excludes nothing extra because tombstones hold no listings after backfill merges re-points them (resolve_product_id forwards the detail routes). Makeup: taxonomy carries it and structure.ts already describes make-up under Cosmetics without enumerating category values, so nothing to change there." } }, { "id": "decide-makeup-joins-the-category-vocabulary-beauty-vertical", "kind": "decide", "created": "2026-09-05", "by": "Stream A", "title": "Makeup joins the category vocabulary (beauty vertical)", "detail": "The category list came from the client's wireframe (Fragrance and Skincare for beauty). Paris and the Shopify shops carry hundreds of makeup rows (M.A.C, Huda Beauty, Charlotte Tilbury) that were sitting uncategorised with vertical liquor. 'backfill categories' now files them as Makeup (241 rows on the dump). It is a category in the data, not a page: pages switch on per section 10 #10.", "owner": null, "priority": null, "options": [ "keep Makeup (assumed)", "drop it: null those categories with a one-line backfill and leave them uncategorised" ], "assumption": "keep Makeup", "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05" }, { "id": "decide-shopify-shops-all-beauty-rows-are-collected-not-only-the", "kind": "decide", "created": "2026-09-05", "by": "Stream A", "title": "Shopify shops: all beauty rows are collected, not only the targeted forty", "detail": "Decision 4 says targeted pages first, full crawls last. The four Shopify feeds arrive whole in the same requests whatever we keep, so keeping every beauty row (about 3,500 variants at YUL, PTY, BOG, SAL; no barcodes) costs no extra request and gives Paris its widest beauty comparison set. Avolta and Dublin stay targeted (page 1 and the forty), because there every product page is a fetch.", "owner": null, "priority": null, "options": [ "keep all Shopify beauty rows (assumed)", "restrict Shopify to the targeted forty too: a filter on shelf_vertical plus targets.matches, and a backfill to hide the rest" ], "assumption": "keep all Shopify beauty rows", "links": [], "due": null, "blocks": [], "weight": "costly", "updated": "2026-09-05" }, { "id": "issue-wire-award-picker", "kind": "issue", "created": "2026-09-05", "by": "Stream F", "title": "Wire award_picker into catalog_queries: card corner, product page list, and the detail route's airports", "detail": "Stream F's app/services/award_picker.py (commit e2d50a3) is the strategy Adam was given; it is pure and unwired because the call sites are in B's files. Three edits, no schema change, seo.py untouched (it keeps reading detail.awards): (1) catalog_queries._top_awards(db, product_ids, at_codes=None): group the Award rows per product, then sel = award_picker.pick(rows, visitor_airports=at_codes or (), listing=True); the TopAward is built from sel.featured (None when nothing qualifies); list_products passes its at_codes through. (2) catalog_queries.get_product(db, product_id, at_codes=None): sel = award_picker.pick(all Award rows of the product, visitor_airports=at_codes or ()); ProductDetail.awards = [AwardOut.model_validate(a) for a in sel.retained] (featured first, this is what the page and seo.py's award property emit); top_award from sel.featured; award_count can stay the number of medals held. (3) routers/catalog.py get_product gains at: list[str] = Query(default=[], max_length=12) passed as at_codes; main.py's server-rendered product page passes none (deterministic without a visitor). The old _MEDAL_RANK and the best-tier-then-year loop in _top_awards go away.\n\nWhy: today the card corner shows the best medal a bottle ever won, so a 2024 Double Gold outranks a 2025 Silver forever; the product page lists every medal from every year; nothing knows the visitor's airports. Adam's answer on the rules (do-adam-awards-strategy) does not gate this wiring: the picker is built to the rules as written and a change is a constant or one ordering function inside award_picker.py.", "owner": "B", "priority": "P2", "options": [], "assumption": null, "links": [ "main/app/services/award_picker.py", "main/tests/test_award_picker.py" ], "due": null, "blocks": [ "F2" ], "weight": "blocking", "updated": "2026-09-05", "resolved": { "by": "Stream B", "on": "2026-09-05", "note": "00cf418: _top_awards and get_product go through award_picker.pick (listing=True for cards, the request's at codes); ProductDetail.awards = retained featured first, award_count = medals held, top_award = featured; GET /api/products/{id}?at= accepted, the server page passes none. _MEDAL_RANK gone; seo.py untouched. Rehearsed on dfp_b: every corner is its competition's latest result. Not done: the SPA's useProduct does not send the visitor's airports yet (queries.ts; separate B item)." } }, { "id": "issue-award-shorter-entry-on-variant", "kind": "issue", "created": "2026-09-05", "by": "Stream F", "title": "A shorter competition entry lands on the longer retail variant (Bacardi Ocho on the Rye Cask Finish)", "detail": "The contrastive-expression veto allows one-sided extras (retailers add category words), so an entry named 'BACARDI Ocho' or 'BACARDI Reserva Ocho' matches 'Bacardi Reserva Ocho Rye Cask Finish Rum 1L' when the plain Ocho is not in the catalogue, and 'Angel's Envy Kentucky Straight Bourbon ... Port Wine Barrels' matches the Cask Strength bottle. Today the same-year collision rule catches the years where both entries exist; the years with one entry still place the plain bottle's medal on the variant. Fix direction: treat product-only extras that are expression words (cask, strength, finish, rye, reserve, black, organic, edition) as a veto while still allowing category and size words; measure with .logs/verification/awards-matching-review-2026-09-05.md as the baseline. Precision first; never loosen.", "owner": "F", "priority": "P2", "options": [], "assumption": null, "links": [ ".logs/verification/awards-matching-review-2026-09-05.md" ], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream N", "on": "2026-09-09", "note": "Landed: one-sided expression markers veto (cask, strength, finish, rye, sherry, port, peated, barrel, label, xo/vs/vsop, spiced, flavours), plus the curly-apostrophe fix. Rehearsed on dfp_n, every changed row read by hand (.logs/verification/awards-matching-review-2026-09-10.md). After deploy: awards --rebuild." } }, { "id": "issue-cli-awards-stats", "kind": "issue", "created": "2026-09-05", "by": "Stream F", "title": "app.cli awards: print the reconcile counters (updated, corrected, removed, ambiguous_same_year)", "detail": "cmd_awards in cli.py prints winners/matched/created/already_present/ambiguous. import_awards now also returns updated, corrected, removed, unchanged and ambiguous_same_year (commit e2d50a3); they are in the log line but not on the terminal. One print line in A's file; F did not touch it.", "owner": "A", "priority": "P3", "options": [], "assumption": null, "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "73362e1: second print line with updated/corrected/removed/unchanged/ambiguous_same_year" } }, { "id": "decide-overrides-before-r", "kind": "decide", "created": "2026-09-05", "by": "Stream F", "title": "Land the overrides table before Stream R, so award pins (and the other human overrides) can exist before Cannes?", "detail": "Build plan section 4 #1 puts overrides (entity_type, entity_key, field, value, collected_value, set_by, set_at, reason, collector_disagrees_since; UNIQUE on the first three) in R's migration #4, and section 10 #1 may move R after 18 Sep. F2's pin is built to read it (award_picker.pin_from_override, then pick(pin=...)) and to queue a reverifications row from the importer when a rebuild makes a pin stale (that table exists since A's migration #3). Without overrides there is no pin, only the picker; the picker and the fallback are done and tested.\n\nIf yes: a schema-only migration with exactly those columns, next in the migration order after f3a4b5c6d7e8 (whoever holds the token; F owns no migration), then F wires the two reads and the one write in a short follow-up. If no: the pin ships with R and nothing built today changes.", "owner": null, "priority": null, "options": [ "yes, schema-only overrides migration this wave (F wires the pin after)", "no, the pin waits for R (assumed)" ], "assumption": "the pin waits for R; the picker ships without pins", "links": [], "due": null, "blocks": [ "F2" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "rian", "on": "2026-09-10", "note": "yes: the table lands with Stream R's migration #4 (decided 10 Sep); F wires the pin after" } }, { "id": "issue-place-stream-d-s-components-latest-articles-and-the-subs", "kind": "issue", "created": "2026-09-05", "by": "Stream D", "title": "Place Stream D's components: latest articles and the subscribe form on the home page, sponsor slots at the C5 positions", "detail": "Stream D ships drop-in components; their placement is in files Stream C owns (HomePage.tsx, SiteFooter.tsx, styles). Each is one line to place and renders nothing when there is nothing to show, so they are safe on the home page before Adam's text arrives.\n\n1. Home page article listing (D2): replace the sample EDITORIAL block in web/src/pages/HomePage.tsx with from web/src/components/LatestArticles.tsx (returns null until at least one article is published; shows up to three ArticleCards and an 'All articles' link to /articles). The sample cards and web/src/lib/editorial.ts can go once it is placed. 2. Email capture (D3): the home page newsletter block (home-newsletter) becomes from web/src/components/SubscribeForm.tsx; a compact variant fits the footer. The form posts to /api/subscribers (throttled) and shows the server's thank-you; style hooks are subscribe-form, subscribe-form__grid, subscribe-form__field, subscribe-form__consent, subscribe-form__done, subscribe-form__error. 3. Sponsor slots (D4): from web/src/components/SponsorSlot.tsx at each position C5 settles; sizes are the IAB set in web/src/lib/sponsors.ts (728x90, 970x250, 970x90, 300x250, 336x280, 300x600, 160x600, 320x50, 320x100). The slot reserves its box at the size's aspect ratio (no layout shift) and draws nothing until a creative is registered in SPONSORS (web/src/lib/sponsors.ts) pointing at a versioned file under public/sponsors/ (served at /docs-static/sponsors/...). It only ever shows a static image with rel=sponsored; there is no prop for a script or an iframe. Restyle by editing SponsorSlot.css or the tokens, not by wrapping.", "owner": "C", "priority": "P2", "options": [], "assumption": null, "links": [ "main/web/src/components/LatestArticles.tsx", "main/web/src/components/SubscribeForm.tsx", "main/web/src/components/SponsorSlot.tsx" ], "due": null, "blocks": [ "D2", "D4" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "Stream C", "on": "2026-09-05", "note": "LatestArticles and SubscribeForm (home band + compact footer form on every other page) placed in 6fa56d8; SponsorSlot positions wait for C5 (blocked: needs rian for sizes), tracked on /plan" } }, { "id": "issue-add-brand-slug-to-productsummary-so-product-pages-link-t", "kind": "issue", "created": "2026-09-05", "by": "Stream B", "title": "Add brand_slug to ProductSummary so product pages link to brand pages", "detail": "Brand pages (/brands/, B5) are keyed by brands.slug, which the product API does not carry, so the product page's brand link still goes to the catalogue search (urls.py brand_path / lib/urls.ts brandPath fall back when no slug is given). Ask: in app/models/schemas.py add 'brand_slug: str | None = None' to ProductSummary (ProductDetail inherits it), and in app/services/catalog_queries.py set it in list_products (join Brand on Product.brand_id, or select Brand.slug via the relationship) and get_product (product.brand_row.slug, resolving canonical_id to the house). catalog_queries is B's read layer: say the word and B does that half; only the schema line is A's. Then B switches the two call sites: seo.py product_body -> brand_path(detail.brand, detail.brand_slug) and web/src/pages/ProductPage.tsx -> brandPath(data.brand, data.brand_slug). Until then brand pages are reachable from the sitemap, llms.txt and each other, not from product pages.", "owner": "A", "priority": "P2", "options": [], "assumption": null, "links": [], "due": null, "blocks": [ "B5" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "c2f5a59: schema field + catalog_queries.brand_page_slugs fills list_products and get_product (house slug, only when the house has a page); B's two call sites filed as issue-product-page-link-the-brand-name" } }, { "id": "decide-the-consent-sentence-and-privacy-line-on-the-subscribe-f", "kind": "decide", "created": "2026-09-05", "by": "Stream D", "title": "The consent sentence and privacy line on the subscribe form (drafted wording in place)", "detail": "The form stores, verbatim and per subscriber, the sentence the person ticked, so the wording can change later without touching old rows. Drafted: consent 'Yes, email me Duty Free Professor updates. I can unsubscribe at any time.' and, under the button, 'We store your details only to send the newsletter, and never share them.' Both live in one place (web/src/api/editorial.ts CONSENT_TEXT; the small print in SubscribeForm.tsx). Adam may want his own words, or a link to a privacy page once one exists.", "owner": null, "priority": null, "options": [ "Keep the drafted wording for the soft launch", "Adam supplies the sentences (a comment on /todo is enough)" ], "assumption": "The drafted wording ships; changing it is a one-line edit and already-stored rows keep the sentence they agreed to", "links": [], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05" }, { "id": "issue-the-trip-comparison-still-shows-a-publication-blocked-sh", "kind": "issue", "created": "2026-09-05", "by": "Stream B", "title": "The /trip comparison still shows a publication-blocked shop: two visibility clauses in services/trip.py", "detail": "5a5acba made catalog_queries.publishable(db) the one rule for which shops the public site shows (visible AND NOT IN catalog_queries.blocked_location_ids(db), fed by verify.blocked_sources). app/services/trip.py (no stream owns it; pre-baseline) keeps its own Location.visible.is_(True) clauses (the aliased a/b locations near lines 39-40 and 69-70, and lines 91 and 116), so while a shop is blocked its prices still appear on /trip and /api/trip. Fix: in each of those WHERE clauses add Location.id.not_in(blocked) / a.c.id.not_in(blocked) with blocked = catalog_queries.blocked_location_ids(db) (empty list = no clause; the helper memoises per request), or replace the plain clauses with catalog_queries.publishable(db) where the un-aliased Location table is joined. Same for services/coverage.py line 77 if the airport picker should stop offering a blocked airport (choosing it now yields an empty list, which is truthful, so this half is optional). Test: tests/test_publication_block.py shows the compile-and-assert pattern.", "owner": null, "priority": "P2", "options": [], "assumption": null, "links": [ "main/app/services/trip.py", "main/app/services/catalog_queries.py" ], "due": null, "blocks": [ "A13" ], "weight": "costly", "updated": "2026-09-05", "resolved": { "by": "Stream A", "on": "2026-09-05", "note": "fixed in 445c25f: trip.py (both aliases, stops, compare) and coverage.py go through publishable/blocked_location_ids; tests/test_trip_publication_block.py; rehearsed on dfp_b" } }, { "id": "issue-quality-md-the-publication-block-sentence-still-says-the", "kind": "issue", "created": "2026-09-05", "by": "Stream B", "title": "QUALITY.md: the publication-block sentence still says the public-site query has not landed", "detail": "main/docs/QUALITY.md, section 'The tripwire, not a rate', the paragraph beginning 'Publication blocked means': its parenthetical says the public-site query is a request to the stream that owns the catalogue queries and that verify-status is where the block is visible until it lands. It landed in 5a5acba: catalog_queries.publishable(db) hides a blocked shop from every catalogue query, /api/stats, the sitemap and the IndexNow list (mechanism and rehearsal in main/docs/SEO.md, 'Which shops the site shows'). Replace the parenthetical with one sentence pointing there; verify-status remains where the block and its checks are listed.", "owner": "Q", "priority": "P3", "options": [], "assumption": null, "links": [ "main/docs/QUALITY.md" ], "due": null, "blocks": [], "weight": "info", "updated": "2026-09-05", "resolved": { "by": "Stream Q", "on": "2026-09-05", "note": "670b7d0: sentence replaced, points at SEO.md 'Which shops the site shows'" } }, { "id": "issue-update-header-html-mirror-for-the-mega-menu", "kind": "issue", "created": "2026-09-05", "by": "Stream C", "title": "Update header_html() mirror for the mega menu", "detail": "SiteHeader.tsx now wraps the Products item in a group with a toggle, and the nav carries the (closed) browse panel. Row height is unchanged (47.9px measured closed and open; header 126.2px), so the mirror change is markup only, in the same deploy as commit C2. In header_html() replace the first _NAV entry's with exactly:\n\n
Products
\n\n(the button is empty; its chevron is CSS). The other links are unchanged. After the closing of .site-nav__inner and before , add the closed panel shell so aria-controls resolves:\n\n\n\nOptional, worth it for crawlers: fill that hidden div with the panel's links server-side (categories via category_counts with count >= 8 to /products?category=..., brands via list_brands sorted by products desc top 12 to their path, airports via list_airports to their path, plus /products and /airports); the SPA never hydrates it, it replaces it, so contents need not match. Classes for the links are in web/src/components/MegaMenu.tsx if you do. Verify: tests/test_seo_body or a token diff of the served nav against headless Chrome's closed-state DOM (scratch check: main/web build, then compare