Rebrand GPTZero-V to GPTZero-o: expand scope to media content authenticity

[Copilot]

Rebrands the repository from GPTZero-V (image-focused) to GPTZero-o (media content authenticity toolkit for imagery, audio, and video). Updates all package names, imports, configuration, and documentation to reflect the expanded scope.

Package Structure Changes

• Workspace: GPTZero-V → gptzero-o
• Core SDK: packages/gptzero → packages/gptzero-o-core
  • Python module: gptzero → gptzero_o
• API Server: packages/gptzero-api → packages/gptzero-o-server
  • Python module: gptzero_api → gptzero_o_server
  • CLI: gptzero-api → gptzero-o-server
• Python Client: packages/gptzero-sdk → packages/gptzero-o-client-py
  • Python module: gptzero_sdk → gptzero_o_client
• Streamlit UI: packages/gptzero-service → packages/gptzero-o-web

Code Updates

• Updated all import statements across packages and tests
• Fixed test mocks (@patch decorators) to reference new module paths
• Updated workspace dependencies in pyproject.toml files
• Updated Dockerfile package paths and startup script
• Updated GitHub Actions workflow job names and package references

Documentation & Scope

• Changed positioning from "image authenticity verification" to "media content authenticity toolkit"
• Updated scope to explicitly include imagery (current), audio and video (planned)
• Updated main README, package READMEs, and technical docs
• Fixed all dash/underscore inconsistencies in documentation
• Moved summary documents to docs/ folder with timestamps:
  • docs/2025-12-29-rebranding-summary.md
  • docs/2025-12-29-github-about-proposal.md

Example Usage Change

# Before
from gptzero import ImageVerifier, ImageInput
from gptzero_sdk import GPTZeroClient

# After
from gptzero_o import ImageVerifier, ImageInput
from gptzero_o_client import GPTZeroClient

Breaking Changes

This is a breaking change for external consumers. Import paths must be updated from gptzero* to gptzero_o* modules.

Testing

• Integration tests moved to packages/gptzero-o-client-py/tests/test_integration.py
• Added integration test job to CI/CD workflow
• All existing unit tests updated and passing (36 tests, 96% coverage)
• Linting passes across all packages

Note: GitHub repository URL remains DiTo97/GPTZero-V to preserve existing links and references.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>GPTZero-o rebranding</issue_title>
<issue_description>The whole repository must be rebranded from GPTZero-V to GPTZero-o. I want it to be a media content authenticity toolkit and platform expanding to audio and video, outside of imagery.

This means that every reference of GPTZero-V in the code base, docs, management should become GPTZero-o.

The workspace should take the following naming convention:

• gptzero-o is the workspace at the root level
• gptzero to gptzero-o-core
• gptzero-api to gptzero-o-api
• gptzero-sdk to gptzero-o-sdk
• gptzero-service to gptzero-o-service

The packages should also follow the convention in code, i.e., gptzero to gptzero_o.

make sure the READMEs and other docs reflect the different scope of the toolkit.

make sure everything runs correctly, unit tests pass and add some integration tests from the SDK / API.

When done, propose a short description and tags for the GitHub About section of the repository. At current, they are:

A simple attempt at a heuristic GPTZero algorithm for image authenticity verification through metadata analysis

with tags metadata, image-generation, heuristic-algorithm, content-authenticity</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes GPTZero-o rebranding #16

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[DiTo97]

@copilot some things must be fixed:

• change package names again: workspace gptzero-o, the core library gptzero-o-core, the API server gptzero-o-server, the Python API client gptzero-o-client-py and the Streamlit UI as gptzero-o-web; make sure docs, tests, and package names are consistent. Sorry, I had double thoughts.
• I see a lot of inconsistencies in the docs / Markdown files. There are many mistakes on package names, usage instructions with Docker, confusing dashes with underscores. I've seen such issues in many of those files
• make sure every summary-like or docs you produce are still scoped to the docs/ folder not the repository root. Potentially, prefixing each MD file with a timestamp to keep temporal order.
• the integration tests you wrote shouldn't be in the root repository; rather must be moved to either the server or client packages depending on what kind of integration tests they are and added to the test job in the CI/CD workflow

[Copilot]

@copilot some things must be fixed:

• change package names again: workspace gptzero-o, the core library gptzero-o-core, the API server gptzero-o-server, the Python API client `gptzero-o-client-...

All changes completed! Here's what was fixed:

1. Package names updated to final convention:

• Core library: gptzero-o-core (Python: gptzero_o)
• API server: gptzero-o-server (Python: gptzero_o_server, CLI: gptzero-o-server)
• Python client: gptzero-o-client-py (Python: gptzero_o_client)
• Streamlit UI: gptzero-o-web

2. Documentation inconsistencies fixed:

• All READMEs updated with correct package names
• Fixed dash/underscore confusion throughout docs
• Docker commands now use correct package names
• All import examples consistent (e.g., from gptzero_o_client import)

3. Summary docs moved to docs/ with timestamps:

• docs/2025-12-29-rebranding-summary.md
• docs/2025-12-29-github-about-proposal.md

4. Integration tests reorganized:

• Moved from root to packages/gptzero-o-client-py/tests/
• Added integration test job to CI/CD workflow
• Tests verify client can import and work with server

All changes verified:

• ✅ 36 unit tests passing (96% coverage)
• ✅ Integration test passing
• ✅ Linting clean across all packages

Commits: e3f1098, 36ac00f