Prepare a local TabTin development environment

You are preparing my computer for local TabTin development. I intend to build my own product on TabTin, not contribute a change upstream. Treat this repository as the source of truth instead of guessing versions or commands from experience.

Before you begin

Read AGENTS.md, docs/agent/setup.md, docs/agent/commands.md, and the root package.json. Use read-only checks to record the current branch and worktree, operating system, CPU architecture, and the installed versions of Node, pnpm, Python, Docker, Git, and platform build tools. Preserve every uncommitted change. Never run reset, clean, stash drop, or overwrite an environment file.

Work to complete

1. Derive the required dependencies, recommended versions, and platform-only tools from the repository documentation.
2. Check whether each dependency is installed and compatible, and confirm that the Docker engine can be reached.
3. When a tool is missing, use the platform’s customary reversible installation path. Explain the impact before any system-level change.
4. Install the root workspace and Django dependencies using the repository’s supported commands. Do not create competing environment files.
5. Stop after environment preparation: do not start the full product or modify business code.

Verification

Repeat the version checks and run the lightest dependency-resolution checks. Prove that the package manager can read the workspace, Python can import Django, and Docker can talk to its service. If anything remains blocked, identify the exact tool, permission, or network condition rather than reporting a vague environment problem.

Final report

Provide a table of dependencies, detected versions, status, and actions taken. List any local configuration you changed, permissions that still require my decision, and the exact next command for starting TabTin. Do not commit or push unless I explicitly ask.