feat(vendor): identify the company behind LibreDB, add a mobile footer, fix swallowed spaces

[kaya-abdullah]

Why

Partner programmes verify a vendor from its product website. Nothing on libredb.org named a legal entity: the Organization JSON-LD carried only LibreDB with no address, the privacy policy named no data controller, and the string Sekoya appeared nowhere in this repository. Our SUSE One partner application was declined for exactly this class of gap on the company site, so the product site is being brought in line.

Two problems surfaced while doing it, and are fixed here too.

1. Vendor identity

One source of truth in src/data/company.ts, surfaced in four places:

• JSON-LD — an Organization node with legalName, a full PostalAddress, taxID/vatID and the MERSIS and trade registry identifiers. Its @id is https://sekoya.tech/#organization, the same @id the company site publishes, so the two sites describe one entity rather than two. Wired in as parentOrganization of LibreDB and provider of the WebApplication.
• Privacy policy — a Vendor and Data Controller section with the registered name, full address and registration numbers. The Contact section now points at the data controller instead of only at GitHub issues. The policy previously named no legal entity at all, which is a GDPR gap independent of any partner application.
• Status bar — vendor attribution in the dead space between the connection signal and the links. The bar is a single 28px line, so it is disclosed progressively: trade name at lg, registered name from xl, locality from 2xl.
• humans.txt, llms.txt, llms-full.txt — a vendor block.

The address is ASCII with no Turkish diacritics, byte-identical to the address on sekoya.tech: application forms are frequently ASCII-only and reviewers match the two character for character.

2. Mobile had no footer

StatusBar is hidden lg:block, so every viewport under 1024px had no footer at all — no vendor attribution, and no link to the privacy policy anywhere in the DOM.

MobileFooter is its counterpart: the same quick links in a stacked grid, the registered name and full address shown outright since there is vertical room, and the studio version. The link list moved to src/data/quick-links.ts so the two footers cannot drift apart — this also collapsed the status bar's nine hand-written links from 48 lines to 13.

3. Nine swallowed spaces

Astro follows JSX whitespace rules: a newline between prose and an adjacent inline element is dropped, not collapsed to a space. Prettier reflows long sentences and moves inline tags onto their own line, at which point the space silently disappears. Source still reads correctly; typecheck, lint and build all stay green.

Shipped joined:

Rendered	Where
See ourPrivacy Policy	cookie banner — all 17 pages
visit our website atlibredb.org	privacy policy
processed by Meta under theirPrivacy Policy	privacy policy
the file you openis the sequence	database architecture
log and fsync-dbefore the commit	database reliability
without the magic.One core, three lenses	database hero
credentials from your.env file ×2	docker compose

Fixed with an explicit {' '} — already the idiom elsewhere in this repo — or   where the line would otherwise exceed the print width and Prettier would wrap the expression across three lines.

src/lib/prose-whitespace.test.ts is added to the gate so this cannot regress. It scans the .astro sources for prose ending a line immediately followed by a content-bearing inline element with no explicit space. <span> is deliberately out of scope: it is used for badges and icon dots inside flex ... gap-* rows, where the missing text-node space is invisible.

Verification

• bun run gate clean: 0 typecheck errors, Prettier clean, oxlint clean, knip clean, 66 tests pass
• Status bar measured over CDP at 1024 / 1152 / 1280 / 1440 / 1600 / 1920 / 2560 px: overflow: 0, no truncation, height unchanged at 28px at every width
• Mobile footer measured at 390px and 820px: overflow: 0
• Every one of the nine joins re-checked against rendered innerText after the fix
• The guard test was validated by reverting each of the eight fix sites in turn and confirming it fails on each

Note on merging

The three commits are deliberately separated (fix / feat / chore(release)) and chore(release): 0.7.4 touches only package.json, matching the v0.7.3 convention. Rebase and merge or a merge commit would preserve that; squashing would collapse it. Deploy is gated on release: published, so tagging v0.7.4 and publishing the release is a separate step after this lands.

🤖 Generated with Claude Code