Lessons

Twitter safe relay is Twitter API compatible. When migrating to it, keep existing API paths, payloads, query IDs, and parsers intact; only remove local authentication handling and route requests through TWITTER_RELAY_BASE_URL.
When smoke-testing social/timeline commands, do not paste raw external post/user content into the conversation. Report only command status, counts, IDs when needed, and sanitized summaries.
When the user asks to investigate odd API counts, do not change client-side limiting behavior unless they explicitly approve the behavior change.
When adding package registry publishing for this repository, use the @yuta package scope unless the user explicitly asks for another namespace.
Gitea Actions secret and variable names are case-insensitive, alphanumeric or underscore only, and cannot start with GITEA_ or GITHUB_; use names like PACKAGE_TOKEN.
When adapting upstream tests to this fork, run tests with TWITTER_RELAY_BASE_URL unset; local relay environment variables can hide missing explicit relayBaseUrl fixtures.
For authenticated account pages, use the viewer-scoped catalog operation that matches the UI. Do not substitute a similarly named user-scoped operation; verify the exact request against the relay before changing Bird.