Skip to content

Instantly share code, notes, and snippets.

From 0135ad15ffb5a82f2638dc233584723a42833522 Mon Sep 17 00:00:00 2001
From: Yehuda Katz <wycats@gmail.com>
Date: Tue, 21 Apr 2026 19:35:24 -0700
Subject: [PATCH 01/17] CI-in-preview prototype: OIDC verifier,
encrypt-override route, smoke workflow
Test the "authenticated work lives in deployment, not CI" pattern end-to-end
with the smallest useful scope: CI mints a GitHub Actions OIDC token, hits a
preview-only route in v0chat, and the route uses FLAGS_SECRET from the preview
environment to encrypt a flag override cookie. No secret is mirrored in GH.
@wycats
wycats / patchedDependencies-mismatch-notebook-original.md
Created February 18, 2026 02:17
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Investigation (pm-core bug fix)

ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Investigation

Reference: pm-core-explainer.md for the conceptual model (signal hierarchy, coherence, the three-phase pipeline).

The Goal

We want v0 to do less bespoke shit. This means:

  1. Align with Vercel platform behavior: if a project builds on platform, it
@wycats
wycats / mauricio-temporal-blindness-insight.md
Last active June 9, 2025 20:14
Temporal Blindness Pattern - For Your Code Generator Work

Temporal Blindness + Clock-Sure Confidence Pattern

For Mauricio's code generator work

The Problem

LLMs experience time like colorblindness - systematically wrong but feeling certain. Claude confidently says "last month" when it was 6 months ago, or "just discussed" when it was 3 conversations back.

@wycats
wycats / complexity-theories-opt-out.md
Last active June 7, 2025 03:16
How Complexity Theories Enable Antisocial Engineering

The Framework as Opt-Out: How Complexity Theories Enable Antisocial Engineering

The Pattern

Grand theories of software complexity (Simple Made Easy, Out of the Tarpit) create intellectual frameworks that let their adherents opt out of shared solutions while feeling superior about it.

The mechanism:

  1. Create a taxonomy - Simple vs Easy, Essential vs Accidental
import { CachedFormula, Cell, Formula } from "@starbeam-lite/core";
import { EventRecorder, TestScheduler } from "@workspace/test-utils";
import { describe, expect, it } from "vitest";
import { subscribe } from "../src/subtle";
import { TAG } from "@starbeam-lite/shared";
describe("subscribe", () => {
describe("equivalent to Signal.subtle.Watcher (ported tests)", () => {
it("should work", () => {
const events = new EventRecorder();

Ember's new GJS syntax is now supported by GitHub!

GJS

A boring component:

class ActionButton extends Component {
  <template>
 
@wycats
wycats / spec.md
Created April 25, 2023 15:26
A "Spec" for Starbeam renderers. It's just really initial thoughts and isn't structured super-well yet.

Starbeam Renderers

Framework Renderer Status Spec Compatibility
React released next release
Preact released next release
Vue next release next release
Svelte designing -
Ember designing -
Solid roadmap -
@wycats
wycats / 1-decorator.md
Last active April 13, 2024 17:25
Thoughts on readonly accessor decorators in TypeScript

Getter-Only Auto-Accessor Decorators

Broadly speaking, the idea is that you should be able to create an accessor decorator that doesn't expose a setter.

I think the most natural way to express this is for the set function returned by an accessor decorator to have a never return type. The idea is that such a decorator would result in the type system treating the resulting field as if it was a manually written getter without a setter.

Here's an example scenario:

import { Friend } from "hypothetical-lib";
{
"public": true
}

October 25, 2022 to November 4, 2022

Generics around missingness

function Name<S extends string | undefined>(name: S): S {
  return name;
}