2 Commits

Include renames

Author	SHA1	Message	Date
pastilhasandClaude Opus 5	f0d29c8000	the site sections open, because there is finally something behind them ... `ready` was hardcoded false for as long as the sections proxied to an address nobody could set — the connection form was removed and nothing replaced it, so nine doors led to the same "not connected" message. Both halves exist now and neither is typed by a person: the development server runs on a port this plugin chose, holding a FOFOS_API_TOKEN this plugin generated and handed it at start. So the credentials are DERIVED rather than stored. Asking somebody to copy a value out of one part of this plugin into another was never a setting, it was a chore. Development and not production, and that is not a preference. Production is a directory of files behind nginx — no API, no database, nothing listening — so editing against it is impossible rather than merely wrong. Sections read and write dev; Build is what publishes. An edit is visible immediately and public only when somebody decides it should be. The gate asks whether the server ANSWERS, not whether pm2 says online. `bun --hot` survives a crash at startup: the process stays up, pm2 reports online, and nothing is listening. Opening nine sections onto that would make one failed boot look like nine broken screens. And when /status itself cannot be reached, `configured` stays true while `ready` goes false. Telling somebody they have set nothing up is alarming and wrong; opening nine sections onto a server we could not confirm is answering is nine screens that each fail separately. Cannot-tell keeps them shut and lets the next poll open them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-29 20:00:18 +01:00
PastilhasandClaude Opus 5	6b87956e44	Everything needed to be a plugin ... manifest, one table, a router and two panels. Discovery is by convention, so this is the point at which the directory stops being a directory and becomes something Officer can install. The manifest holds only what a listing cannot say. One permission, grantable, with ownerOnly on /_config — reading and editing the site is exactly what a member might be brought in for, but the token is unrestricted write authority over everything the public sees, so handing it over is the owner's. db/schema.ts is ONE table and should stay that way. fofos owns its own Postgres and its own media store; this holds a URL and a token. That is what makes the strongest thing about this plugin true: no operation on it can destroy the client's work, checkbox ticked or not, because none of it was ever here. A cache would be the thin end of that. The router mostly forwards. fofos's /api/admin already answers in the shape a panel wants, so re-wrapping it would be a second place for the contract to drift. Two things in it are load-bearing rather than style: registerProxiedPrefix('/api/fofos-admin/media'). bodyParser calls parseBody on multipart across the whole protected router, and Hono then caches the parsed FormData — so asking for the bytes afterwards re-serialises them under a NEW boundary while the ORIGINAL content-type header is what gets forwarded. Header and body disagree and every upload fails with "Unexpected end of form". Narrow to the one route: everything else is JSON that is fine to parse. The catch-all is LAST in the file. Hono runs matching handlers in registration order, so /* above /_config would swallow it and the settings form would forward itself to fofos, which has no such endpoint — a 404 from a plugin that is working perfectly. Panels are a nav and a detail pane that never speak to each other: the nav writes ?section=, the detail pane reads it. Real <Link>s rather than the buttons proxy-manager uses — AGENTS.md says nav items are links, and the file documenting that pattern says not to copy the older one. <Link> and not <NavLink> because active state here is a query parameter and NavLink compares paths, which would light every row at once. Which component renders which section is a MAP, not a conditional on `built`. The first version read `built ? <MessagesPanel/> : <Planned/>`, which is correct only while exactly one section exists — the second one finished would have rendered Messages under its own name. Messages is the only section built, chosen because it is one read-only route: it proves the path from an Officer panel through this proxy to fofos and back with nothing else able to be wrong at the same time. The other eight are in the nav, dimmed and labelled, saying what they will do and that the old admin still edits them. A nav that hides what is unfinished gives no sense of what the thing is for. Typechecked against the platform — and the typechecker was verified to actually cover plugins/ by planting an error and watching it fail, because a clean run that does not include your files is worse than no run. NOT yet: installed, or run against a live fofos. Nothing here has been through the permission gate or a real request. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-28 23:05:34 +01:00