# 24 — Primary references

The implementation must re-check current documentation before pinning behavior because Codex and Gitea evolve. This source list was reviewed on 2026-07-27.

## OpenAI Codex

- Codex documentation hub: https://developers.openai.com/codex
- Best practices: https://developers.openai.com/codex/learn/best-practices
- Custom instructions with AGENTS.md: https://developers.openai.com/codex/agent-configuration/agents-md
- Build skills: https://developers.openai.com/codex/build-skills
- Skills and plugins: https://developers.openai.com/codex/skills-and-plugins
- Codex CLI: https://developers.openai.com/codex/cli
- Model Context Protocol: https://developers.openai.com/codex/mcp
- Codex SDK: https://developers.openai.com/codex/codex-sdk
- Codex as MCP server / Agents SDK: https://developers.openai.com/codex/mcp-server
- Codex configuration reference: https://developers.openai.com/codex/config-reference

- Codex changelog: https://developers.openai.com/codex/changelog
- Customization overview, including Skills + MCP and subagents: https://developers.openai.com/codex/concepts/customization
- Codex app announcement and worktrees/automations overview: https://openai.com/index/introducing-the-codex-app/

The architecture relies on documented concepts: layered repository instruction discovery through AGENTS.md, reusable Skills containing instructions/resources/scripts, plugins for distribution, MCP connections, subagents and optional future orchestration through Codex CLI/SDK/MCP. The MVP remains copy/export-first so these integrations can evolve independently.

## Gitea

- Current API documentation: https://docs.gitea.com/api/
- Protected branches: https://docs.gitea.com/usage/access-control/protected-branches
- Permissions: https://docs.gitea.com/usage/access-control/permissions
- Pull requests: https://docs.gitea.com/usage/pull-request
- Configuration reference: https://docs.gitea.com/administration/config-cheat-sheet

The adapter must detect the connected Gitea version and derive supported endpoints from its documented API. It must not assume that every self-hosted installation exposes the same feature set.


## Authentication reference

- Better Auth documentation: https://www.better-auth.com/docs
- Email and password: https://www.better-auth.com/docs/authentication/email-password
- Next.js integration: https://www.better-auth.com/docs/integrations/next

Better Auth is the preferred implementation default, but product-owned authorization and first-run behavior remain governed by documents 26 and 31.