atjam.at/web/app/lib/ at main · natespilman.at/atjam.at · Tangled

natespilman.at / atjam.at

0

A jam is a shared-deadline creative challenge: one prompt, a roster of participants, a single due date. Submissions point at records that li

0

atjam.at / web / app / lib /

at main 15 files

Nate Spilman web: rank the feed by what's live, and point prod at EPTSS 11d ago

auth-context.tsx

web: rank the feed by what's live, and point prod at EPTSS Prod's home feed was built with VITE_KNOWN_ORGANIZERS set to the nls-testuser1 test account, so atjam.at listed fourteen seeded test rounds and no real ones — EPTSS Round 31 was never in the feed at all. Point it at @eptss.at. Vite bakes this at build time, so it takes a `flyctl deploy` to land. Then rank what's left. Thirty-one archived EPTSS rounds outnumber the one live round 31:1, and an undivided list buries the only round anyone can act on. Split on the existing Round.deriveState — open/in-progress up top under "Active", closed folded into a <details> the browser already knows how to render. Add UNLISTED_ROUNDS for records that are real but not presentable: partial migrations, drafts superseded by a later record. They stay on the network and reachable by direct link, they just don't get featured. A partially migrated duplicate of Round 29 is the first entry — it derives `open`, so it was ranking beside the genuinely active round. Both surfaces that list rounds route through listedRounds(). Also group milestones that share an instant into one transit station. A phase boundary is a point, not a span — EPTSS closes signups and opens voting at the same moment — so drawing two stations put a segment between them and asserted a duration that doesn't exist. Round 31 has two such boundaries and goes from six stations to four. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 week ago

web: design token + theming foundation (DESIGN.md Phase 0) Tailwind v4 two-tier tokens: themed CSS vars (warm paper/ink neutrals, signal red, state hues) registered via @theme inline so utilities emit var(--token) and flip at runtime. Dark is now driven by a [data-theme] attribute (set before paint by a no-FOUC script in root.tsx) via @custom-variant, not prefers-color-scheme — controllable, and components flip through tokens instead of duplicated `dark:` pairs. Adds cn() (clsx + tailwind-merge) and the tailwind-variants dep for typed variants (used from Phase 1). Migrates the two named primitives — Notice and StatePill — onto semantic tokens as the proof; the rest of the app keeps working (residual `dark:` now keys off the attribute). Fonts deferred until the grotesque/mono are licensed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

web: rank the feed by what's live, and point prod at EPTSS Prod's home feed was built with VITE_KNOWN_ORGANIZERS set to the nls-testuser1 test account, so atjam.at listed fourteen seeded test rounds and no real ones — EPTSS Round 31 was never in the feed at all. Point it at @eptss.at. Vite bakes this at build time, so it takes a `flyctl deploy` to land. Then rank what's left. Thirty-one archived EPTSS rounds outnumber the one live round 31:1, and an undivided list buries the only round anyone can act on. Split on the existing Round.deriveState — open/in-progress up top under "Active", closed folded into a <details> the browser already knows how to render. Add UNLISTED_ROUNDS for records that are real but not presentable: partial migrations, drafts superseded by a later record. They stay on the network and reachable by direct link, they just don't get featured. A partially migrated duplicate of Round 29 is the first entry — it derives `open`, so it was ranking beside the genuinely active round. Both surfaces that list rounds route through listedRounds(). Also group milestones that share an instant into one transit station. A phase boundary is a point, not a span — EPTSS closes signups and opens voting at the same moment — so drawing two stations put a segment between them and asserted a duration that doesn't exist. Round 31 has two such boundaries and goes from six stations to four. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 week ago

checkpoint: in-flight TanStack Start → React Router migration Preserves uncommitted refactor work before doing an unrelated NSID rename on a separate branch. Resume from this branch when picking the refactor back up. - Switching web/src/ scaffold (TanStack Start) to web/app/ (React Router) - Adding Fly.io deploy config (Dockerfile, fly.toml, DEPLOY.md) - Vite/tsconfig adjustments for new framework Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

checkpoint: in-flight TanStack Start → React Router migration Preserves uncommitted refactor work before doing an unrelated NSID rename on a separate branch. Resume from this branch when picking the refactor back up. - Switching web/src/ scaffold (TanStack Start) to web/app/ (React Router) - Adding Fly.io deploy config (Dockerfile, fly.toml, DEPLOY.md) - Vite/tsconfig adjustments for new framework Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

oauth: add at.atjam.invitation to scope The invitation lexicon shipped in 6f4abc2 but the OAuth scope still only listed jam/round/signup/submission, so any attempt to write an invitation record would have been rejected by the user's PDS. Adds invitation to ATJAM_COLLECTIONS (which derives the dev scope) and to the static production scope in oauth-client-metadata.json. Existing signed-in users will need to re-consent on next session — scope expansion always requires fresh authorization. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

payload-preview.test.ts

web: submission payload previews Each submission's payload is now resolved into a lightweight preview in the loader: for app.bsky.feed.post payloads we fetch the post and show its text (truncated to 240 chars) as a blockquote; known collections (Bluesky, WhiteWind) get a "view on <app>" link. Unreachable, deleted, or placeholder payloads degrade gracefully to the bare collection + raw at:// URI — no crash. New payload-preview lib with unit-tested pure helpers (truncate, sourceUrlFor). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

payload-preview.ts

lexicon: allow url submissions alongside record payloads A submission's deliverable is now a gradient, not a single shape: payload (preferred — a content-addressed strong-ref to a record on another app) or url (fallback — a plain link, for work not yet on ATProto). Both are optional in the schema since Lexicon can't express "one-of" across fields; the "at least one" rule lives in code as Submission.getDeliverable — the single gate all rendering/validation flows through, keeping payload primary and the record-vs-link difference visible. Read-side (payload-preview + round detail) routes through the gate; url submissions render as a visibly weaker link. Docs + API reference updated; unit tests cover the gate. Submit-form url input and re-publishing the lexicon are follow-ups. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2 months ago

round-visuals.ts

web: transit-line component — round lifecycle as a subway diagram (Phase 2) The signature component. A round's life is drawn as a transit line: milestones are stations (filled = passed, hollow ring = ahead), the current moment is the red "you are here" dot (one-shot pulse, gated by prefers-reduced-motion), and the stretch of track the round is currently in is tinted with its state color — so the lifecycle state IS the colored segment. Station spacing is even (topological, like a real transit map), and the join-mode shows as a geometric glyph at the origin (color is reserved for state). Rendered as a semantic <ol>; the line/dots are decorative, so screen readers get a clean station list. Replaces the round page's flat Milestones list. JOIN_MODE_GLYPHS joins STATE_VISUALS in round-visuals.ts as the shared visual vocabulary. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

subject-credit.test.ts

web: rank the feed by what's live, and point prod at EPTSS Prod's home feed was built with VITE_KNOWN_ORGANIZERS set to the nls-testuser1 test account, so atjam.at listed fourteen seeded test rounds and no real ones — EPTSS Round 31 was never in the feed at all. Point it at @eptss.at. Vite bakes this at build time, so it takes a `flyctl deploy` to land. Then rank what's left. Thirty-one archived EPTSS rounds outnumber the one live round 31:1, and an undivided list buries the only round anyone can act on. Split on the existing Round.deriveState — open/in-progress up top under "Active", closed folded into a <details> the browser already knows how to render. Add UNLISTED_ROUNDS for records that are real but not presentable: partial migrations, drafts superseded by a later record. They stay on the network and reachable by direct link, they just don't get featured. A partially migrated duplicate of Round 29 is the first entry — it derives `open`, so it was ranking beside the genuinely active round. Both surfaces that list rounds route through listedRounds(). Also group milestones that share an instant into one transit station. A phase boundary is a point, not a span — EPTSS closes signups and opens voting at the same moment — so drawing two stations put a segment between them and asserted a duration that doesn't exist. Round 31 has two such boundaries and goes from six stations to four. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 week ago

subject-credit.ts

web: rank the feed by what's live, and point prod at EPTSS Prod's home feed was built with VITE_KNOWN_ORGANIZERS set to the nls-testuser1 test account, so atjam.at listed fourteen seeded test rounds and no real ones — EPTSS Round 31 was never in the feed at all. Point it at @eptss.at. Vite bakes this at build time, so it takes a `flyctl deploy` to land. Then rank what's left. Thirty-one archived EPTSS rounds outnumber the one live round 31:1, and an undivided list buries the only round anyone can act on. Split on the existing Round.deriveState — open/in-progress up top under "Active", closed folded into a <details> the browser already knows how to render. Add UNLISTED_ROUNDS for records that are real but not presentable: partial migrations, drafts superseded by a later record. They stay on the network and reachable by direct link, they just don't get featured. A partially migrated duplicate of Round 29 is the first entry — it derives `open`, so it was ranking beside the genuinely active round. Both surfaces that list rounds route through listedRounds(). Also group milestones that share an instant into one transit station. A phase boundary is a point, not a span — EPTSS closes signups and opens voting at the same moment — so drawing two stations put a segment between them and asserted a duration that doesn't exist. Round 31 has two such boundaries and goes from six stations to four. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 week ago

url-to-at-uri.test.ts

web: submit a plain URL when the link isn't a known record The submit form now resolves a pasted input two ways: a known record (at:// or a recognized app URL) takes the record path — gated to the round's acceptedSubmissionTypes and fetched for its CID — while any other http(s) link becomes a plain `url` deliverable. resolveSubmissionInput keeps known hosts on the record path so a transient resolution failure can't silently downgrade a record to a url. The hint copy names both paths, keeping payload primary and the url an explicit fallback. Tests cover the new branches. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2 months ago

url-to-at-uri.ts

web: submit a plain URL when the link isn't a known record The submit form now resolves a pasted input two ways: a known record (at:// or a recognized app URL) takes the record path — gated to the round's acceptedSubmissionTypes and fetched for its CID — while any other http(s) link becomes a plain `url` deliverable. resolveSubmissionInput keeps known hosts on the record path so a transient resolution failure can't silently downgrade a record to a url. The hint copy names both paths, keeping payload primary and the url an explicit fallback. Tests cover the new branches. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2 months ago

use-record-write.ts

web: extract useRecordWrite hook for PDS write actions The signup, submit, and invite components each hand-rolled the same write lifecycle — signed-in guard, idle/resolving/submitting/success/ error status, createRecord, revalidate-on-success — with submit-form and invite-form carrying a verbatim-identical Status union. That repetition was an unnamed center. useRecordWrite owns the lifecycle; each caller supplies only what differs: an optional resolve step (handle→DID, URL→at-uri, fetch a CID) and the record to build. No behavior change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago

checkpoint: in-flight TanStack Start → React Router migration Preserves uncommitted refactor work before doing an unrelated NSID rename on a separate branch. Resume from this branch when picking the refactor back up. - Switching web/src/ scaffold (TanStack Start) to web/app/ (React Router) - Adding Fly.io deploy config (Dockerfile, fly.toml, DEPLOY.md) - Vite/tsconfig adjustments for new framework Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 months ago