docs: update readthedocs.io URLs to docs.ansible.com equivalents

🤖 Generated with Claude Code
https://claude.ai/code

Co-Authored-By: Claude <[email protected]>

Author: gundalow

.github/CODE_OF_CONDUCT.md

@@ -1,3 +1,3 @@
 # Community Code of Conduct
 
-Please see the official [Ansible Community Code of Conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
+Please see the official [Ansible Community Code of Conduct](https://docs.ansible.com/projects/ansible/latest/community/code_of_conduct.html).

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -10,7 +10,7 @@ body:
         **Thank you for reporting a bug in Ansible Runner.**
 
         If this is a question about using `ansible-runner`, please do not use a new issue for your question.
-        New issues should be used only for submitting a new bug report. Please consult the [Community guide](https://ansible.readthedocs.io/projects/runner/en/latest/community/)
+        New issues should be used only for submitting a new bug report. Please consult the [Community guide](https://docs.ansible.com/projects/runner/en/latest/community/)
         for information on how to submit your question to the [Ansible Forum](https://forum.ansible.com/).
 
   - type: input

.github/ISSUE_TEMPLATE/documentation_report.yml

@@ -10,7 +10,7 @@ body:
       value: |
         **Thank you reporting an issue with Ansible Runner documentation.**
 
-        If you are looking for community support, please visit the [Community guide](https://ansible.readthedocs.io/projects/runner/en/latest/community/)
+        If you are looking for community support, please visit the [Community guide](https://docs.ansible.com/projects/runner/en/latest/community/)
         for information on how to get in touch.
 
   - type: textarea

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -10,7 +10,7 @@ body:
       value: |
         **Thank you for suggesting a new feature for Ansible Runner.**
 
-        If you are looking for community support, please visit the [Community guide](https://ansible.readthedocs.io/projects/runner/en/latest/community/)
+        If you are looking for community support, please visit the [Community guide](https://docs.ansible.com/projects/runner/en/latest/community/)
         for information on how to get in touch.
 
   - type: textarea

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 Hi there! We're excited to have you as a contributor.
 
 If you have questions about this document or anything not covered here?
-See the [Community section](https://ansible.readthedocs.io/projects/runner/en/latest/community/) of the docs for information about getting in touch.
+See the [Community section](https://docs.ansible.com/projects/runner/en/latest/community/) of the docs for information about getting in touch.
 
 ## Things to know prior to submitting code
 
@@ -42,5 +42,5 @@ To reactivate the virtual environment:
 ```
 
 
-[Ansible code of conduct]: http://docs.ansible.com/ansible/latest/community/code_of_conduct.html
+[Ansible code of conduct]: https://docs.ansible.com/projects/ansible/latest/community/code_of_conduct.html
 [[email protected]]: mailto:[email protected]

README.md

@@ -2,8 +2,8 @@ Ansible Runner
 ==============
 
 [![PyPi](https://img.shields.io/pypi/v/ansible-runner.svg?logo=Python)](https://pypi.org/project/ansible-runner/)
-[![Documentation](https://readthedocs.org/projects/ansible-runner/badge/?version=stable)](https://ansible-runner.readthedocs.io/en/latest/)
-[![Code of Conduct](https://img.shields.io/badge/Code%20of%20Conduct-Ansible-silver.svg)](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html)
+[![Documentation](https://readthedocs.org/projects/ansible-runner/badge/?version=stable)](https://docs.ansible.com/projects/runner/en/latest/)
+[![Code of Conduct](https://img.shields.io/badge/Code%20of%20Conduct-Ansible-silver.svg)](https://docs.ansible.com/projects/ansible/latest/community/code_of_conduct.html)
 [![codecov](https://codecov.io/gh/ansible/ansible-runner/branch/devel/graph/badge.svg?token=CmCcjBz0pQ)](https://codecov.io/gh/ansible/ansible-runner)
 
 Ansible Runner is a tool and Python library that helps when interfacing with Ansible directly or as part of another system. Ansible Runner works as a standalone tool, a container image interface, or a Python module that can be imported. The goal is to provide a stable and consistent interface abstraction to Ansible.
@@ -22,6 +22,6 @@ Get Involved
 [GitHub issues]: https://github.com/ansible/ansible-runner/issues
 [GitHub Milestones]: https://github.com/ansible/ansible-runner/milestones
 [contributing guide]: https://github.com/ansible/ansible-runner/blob/devel/CONTRIBUTING.md
-[Community]: https://ansible.readthedocs.io/projects/runner/en/latest/community/
-[Ansible communication guide]: https://docs.ansible.com/ansible/devel/community/communication.html
-[latest documentation]: https://ansible.readthedocs.io/projects/runner/en/latest/
+[Community]: https://docs.ansible.com/projects/runner/en/latest/community/
+[Ansible communication guide]: https://docs.ansible.com/projects/ansible/devel/community/communication.html
+[latest documentation]: https://docs.ansible.com/projects/runner/en/latest/

docs/community.rst

@@ -9,7 +9,7 @@ Here's how to reach the community.
 Code of Conduct
 ---------------
 
-All communication and interactions in the Ansible community are governed by the `Ansible code of conduct <https://docs.ansible.com/ansible/devel/community/code_of_conduct.html>`_.
+All communication and interactions in the Ansible community are governed by the `Ansible code of conduct <https://docs.ansible.com/projects/ansible/devel/community/code_of_conduct.html>`_.
 Please read and abide by it!
 Reach out to our community team at `[email protected] <mailto:[email protected]>`_ if you have any questions or need assistance.
 
@@ -22,7 +22,7 @@ Search by categories and tags to find interesting topics or start a new one; sub
 
 * `Get Help <https://forum.ansible.com/c/help/6>`_: get help or help others. Please add appropriate tags if you start new discussions, for example ``ansible-runner``, ``playbook``, and  ``awx``.
 * `Posts tagged with 'ansible-runner' <https://forum.ansible.com/tag/ansible-runner>`_: subscribe to participate in project-related conversations.
-* `Bullhorn newsletter <https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn>`_: used to announce releases and important changes.
+* `Bullhorn newsletter <https://docs.ansible.com/projects/ansible/devel/community/communication.html>`_: used to announce releases and important changes.
 * `Social Spaces <https://forum.ansible.com/c/chat/4>`_: gather and interact with fellow enthusiasts.
 * `News & Announcements <https://forum.ansible.com/c/news/5>`_: track project-wide announcements including social events.
 

docs/conf.py

@@ -93,7 +93,7 @@ def _get_version():
 html_theme_options = {
     'display_version': False,
     'titles_only': False,
-    'documentation_home_url': 'https://ansible-runner.readthedocs.io/en/stable/',
+    'documentation_home_url': 'https://docs.ansible.com/projects/runner/en/stable/',
 }
 
 # Add any paths that contain custom static files (such as style sheets) here,

docs/execution_environments.rst

@@ -5,7 +5,7 @@ Using Runner with Execution Environments
 
 .. note::
 
-  For an Execution Environments general technology overview and to learn how get started using it in a few easy steps, see the `Getting started with Execution Environments guide <https://docs.ansible.com/ansible/devel/getting_started_ee/index.html>`_.
+  For an Execution Environments general technology overview and to learn how get started using it in a few easy steps, see the `Getting started with Execution Environments guide <https://docs.ansible.com/projects/ansible/devel/getting_started_ee/index.html>`_.
 
 **Execution Environments** are meant to be a consistent, reproducible, portable,
 and shareable method to run Ansible Automation jobs in the exact same way on

docs/intro.rst

@@ -95,8 +95,8 @@ the environment variables that will be added to the environment at run-time::
    have to worry about the format of certain prompts emitted from **Ansible** itself. In particular, vault passwords need to become more flexible.
 
 **Ansible** itself is set up to emit passwords to certain prompts, these prompts can be requested (``-k`` for example to prompt for the connection password).
-Likewise, prompts can be emitted via `vars_prompt <https://docs.ansible.com/ansible/latest/user_guide/playbooks_prompts.html>`_ and also
-`Ansible Vault <https://docs.ansible.com/ansible/2.5/user_guide/vault.html#vault-ids-and-multiple-vault-passwords>`_.
+Likewise, prompts can be emitted via `vars_prompt <https://docs.ansible.com/projects/ansible/latest/user_guide/playbooks_prompts.html>`_ and also
+`Ansible Vault <https://docs.ansible.com/projects/ansible/latest/index.html>`_.
 
 In order for **Runner** to respond with the correct password, it needs to be able to match the prompt and provide the correct password. This is currently supported
 by providing a yaml or json formatted file with a regular expression and a value to emit, for example::
@@ -157,7 +157,7 @@ The process isolation settings are meant to control the process isolation featur
 * ``process_isolation_ro_paths``: ``None`` Path or list of paths on the system that should be exposed to the playbook run as read-only.
 
 These settings instruct **Runner** to execute **Ansible** tasks inside a container environment.
-For information about building execution environments, see `ansible-builder <https://ansible-builder.readthedocs.io/>`_.
+For information about building execution environments, see `ansible-builder <https://docs.ansible.com/projects/builder/en/latest/>`_.
 
 To execute **Runner** with an execution environment:
 
@@ -189,7 +189,7 @@ Modules
 Roles
 -----
 
-**Runner** has the ability to execute `Roles <https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html>`_ directly without first needing
+**Runner** has the ability to execute `Roles <https://docs.ansible.com/projects/ansible/latest/user_guide/playbooks_reuse_roles.html>`_ directly without first needing
 a playbook to reference them. This directory holds roles used for that. Behind the scenes, **Runner** will generate a playbook and invoke the ``Role``.
 
 .. _artifactdir: