Project Rename to Zyra

[Hackshaven]

This pull request completes the renaming and migration of the project from "DataVizHub" to "Zyra" across documentation, configuration, environment variables, and CI/CD workflows. It introduces backward compatibility for legacy names, updates install and usage instructions, and adds a new release automation workflow. The changes ensure a smooth transition for existing users and contributors while establishing Zyra as the new canonical namespace.

Project Renaming and Documentation Updates:

• All references to "DataVizHub" in documentation (README.md, CONTRIBUTING.md, AGENTS.md) and install instructions have been updated to "Zyra", including import namespaces, CLI commands, and example usage. Migration notes and transition guidance are provided to help users update their code. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

• A new CITATION.cff file is added to support formal citation of Zyra, with updated metadata and project links.

Environment Variables and Configuration:

• Environment variables and configuration files now prefer the ZYRA_* prefix, with legacy DATAVIZHUB_* names supported for backward compatibility. Logic is added in .devcontainer/entrypoint.sh and Dockerfile to map new variables to old ones if needed. [1] [2] [3]

• Devcontainer and Docker Compose service names, workspace folders, and startup commands are migrated from datavizhub to zyra.

CI/CD and Release Automation:

• All workflow and configuration files for publishing and code scanning are updated to use the zyra namespace. [1] [2]

• A new GitHub Actions workflow (.github/workflows/release.yml) is added to automate releases when merging from staging to main, including version checks, tagging, and release creation.

Backwards Compatibility and Transition Support:

• Legacy CLI commands, import namespaces, and configuration variables remain available and redirect to Zyra under the hood for a transition period, as documented in the migration notice in README.md.

---

These changes complete the rebranding and prepare the project for future development under the Zyra name, while minimizing disruption for existing users.

[Copilot]

Pull Request Overview

This PR completes the renaming and migration of the project from "DataVizHub" to "Zyra" across the entire test suite and source code. It introduces backward compatibility for legacy names while establishing Zyra as the new canonical namespace for all modules, imports, CLI commands, and configuration.

• Updates all test imports from datavizhub.* to zyra.*
• Migrates module imports across all source files to use zyra namespace
• Introduces environment variable compatibility layer with ZYRA_* preference and DATAVIZHUB_* fallback

Reviewed Changes

Copilot reviewed 212 out of 232 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tests/	Updates all test imports and CLI invocations from datavizhub to zyra
src/zyra/wizard/	Migrates wizard module imports and adds backward compatibility for CLI commands
src/zyra/visualization/	Updates all visualization module imports to use zyra namespace
src/zyra/utils/	Adds new env.py utility and updates imports across utility modules
src/zyra/processing/	Migrates processing module imports and error messages
src/zyra/connectors/	Updates connector backend imports to use zyra namespace
src/zyra/api/	Migrates API server and worker imports with backward compatibility
src/zyra/cli.py	New main CLI entrypoint replacing datavizhub namespace

Comments suppressed due to low confidence (2)

src/zyra/wizard/resolver.py:129

• This mock response still uses the old 'datavizhub' command name instead of 'zyra'. While backward compatibility is maintained, test mocks should demonstrate the preferred new command format.

        """

src/zyra/wizard/zyra_capabilities.json:132

• The capabilities JSON file still contains 'datavizhub' references in command descriptions. These should be updated to 'zyra' to reflect the new canonical namespace.

        "default": "-"

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}