v1.2.2 — API tokens, via GitHub login

Sign in with your GitHub account at <server>/tokens to create an API token.

That's the whole feature. It exists because GitHub OAuth (1.2.0) needs a browser and a human — CI jobs, cron and server-side agents have neither, so they need a token instead.

Using it

1. Open <server>/tokens and sign in with GitHub — same account, same user_id as OAuth, so memories are shared either way.
2. Create a token. It's shown once and stored only as a hash.
3. Use it like any bearer key:

Authorization: Bearer pmn_…

The same page lists and revokes your tokens. Tokens are browser-only by design — a secret should never travel an LLM channel, so there are no MCP tools for this. The tool surface is unchanged.

If you run a server

• Add a second redirect URI to your GitHub OAuth App: https://<your-host>/tokens/callback. Keep the existing /auth/callback — that one is for MCP clients, and neither path covers the other.
• No OAuth configured → the pages return 404, by design: without GitHub login there's no way in.
• POLYMNEMO_API_KEYS still works. Keep it as your break-glass path — it's the only credential that doesn't need the database.

Full changelog: v1.2.1...v1.2.2