docs: standardize README and community files

.github/CODEOWNERS

@@ -0,0 +1,20 @@
+# CODEOWNERS for testcontainers-floci-python
+#
+# Routes module code to this repository's maintainers (see MAINTAINERS.md) and keeps
+# release-sensitive paths with the Lead, per the org-wide GOVERNANCE.md.
+#
+# Order matters: the LAST matching pattern wins, so the Lead-reserved paths below stay
+# authoritative over the broader area rules above them.
+#
+# Docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# Default: no global owner (unowned files fall through to normal review rules).
+
+# Module code
+/floci/              @hectorvent
+/tests/              @hectorvent
+
+# CI, release automation, workflow hygiene
+/.github/            @hectorvent
+/.releaserc.json     @hectorvent
+/pyproject.toml      @hectorvent

.gitignore

@@ -31,4 +31,4 @@ htmlcov/
 # macOS
 .DS_Store
 
-local/
+/local/

CODE_OF_CONDUCT.md

@@ -0,0 +1,31 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and maintainers pledge to make participation in Floci a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+**Positive behavior includes:**
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+**Unacceptable behavior includes:**
+- The use of sexualized language or imagery
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening a GitHub issue or contacting the maintainers directly. All complaints will be reviewed and investigated promptly and fairly.
+
+Maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned with this Code of Conduct.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

CONTRIBUTING.md

@@ -3,7 +3,8 @@
 Thanks for contributing. Issues, reviews, docs, and pull requests are all welcome, and you
 don't need permission to start. Before you dig in, a quick read of the project
 [GOVERNANCE.md](https://github.com/floci-io/.github/blob/main/GOVERNANCE.md) explains how
-decisions are made and how contributors grow into Maintainers over time.
+decisions are made and how contributors grow into Maintainers over time. Everyone taking part is
+expected to follow the [Code of Conduct](CODE_OF_CONDUCT.md).
 
 ## Developer Certificate of Origin (DCO) sign-off
 
@@ -36,8 +37,9 @@ Why Floci uses the DCO and not a CLA is explained in the
 
 ## Running tests locally
 
-Set up a development environment with [uv](https://docs.astral.sh/uv/) (or
-`pip install -e ".[dev]"`):
+Set up a development environment with [uv](https://docs.astral.sh/uv/). The commands below run the
+tools from the project environment with `uv run`; with pip instead, run `pip install -e ".[dev]"`
+inside an activated virtualenv and drop the `uv run` prefix.
 
 ```bash
 uv sync --extra dev
@@ -46,22 +48,22 @@ uv sync --extra dev
 Lint, format check and type check, as CI runs them:
 
 ```bash
-ruff check .
-ruff format --check .
-mypy floci
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy floci
 ```
 
 Unit tests need no Docker:
 
 ```bash
-pytest -m "not integration" -v
+uv run pytest -m "not integration" -v
 ```
 
 Integration tests start a real Floci container, so they need Docker:
 
 ```bash
 docker pull floci/floci:latest
-pytest -m integration -v
+uv run pytest -m integration -v
 ```
 
 ## Pull Request Limits and Review Bandwidth
@@ -81,4 +83,8 @@ Once your current pull requests are reviewed, merged, or closed, you are welcome
 - 🗣️ **[GitHub Discussions](https://github.com/orgs/floci-io/discussions)**: feature ideas, design tradeoffs, and proposals.
 
 By contributing, you agree to abide by the project
-[Code of Conduct](https://github.com/floci-io/.github/blob/main/CODE_OF_CONDUCT.md).
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Reporting Security Issues
+
+Please do **not** open public issues for security vulnerabilities. See [SECURITY.md](SECURITY.md) for how to report them privately.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Hector Ventura
+Copyright (c) 2026 Floci and its contributors.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal