Update docs command

Signed-off-by: Felipe Sayão Lobato Abreu <github@mentordosnerds.com>

Author: coisa

.github/workflows/wiki.yml

@@ -48,32 +48,22 @@ jobs:
         uses: php-actions/composer@v6
         with:
           php_version: '8.3'
-          command: 'dev-tools docs'
+          command: 'dev-tools'
+          args: 'wiki -- --target=.wiki'
 
       - name: Prepare wiki submodule branch
         id: wiki_branch
-        working-directory: docs/wiki
+        working-directory: .wiki
         run: |
           git fetch origin
-          wiki_branch="$(git remote show origin | sed -n '/HEAD branch/s/.*: //p')"
-
-          if [ -z "$wiki_branch" ]; then
-            wiki_branch="$(git branch -r | sed 's/^[[:space:]]*origin\///' | grep -v '^HEAD$' | head -n 1)"
-          fi
-
-          if [ -z "$wiki_branch" ]; then
-            echo "Could not determine wiki branch" >&2
-            exit 1
-          fi
-
-          echo "branch=$wiki_branch" >> "$GITHUB_OUTPUT"
-          git checkout -B "$wiki_branch" "origin/$wiki_branch"
+          git checkout master || git checkout -b master
+          echo "branch=master" >> "$GITHUB_OUTPUT"
 
       - name: Commit & push wiki submodule
         id: wiki_commit
         uses: EndBug/add-and-commit@v10
         with:
-          cwd: docs/wiki
+          cwd: .wiki
           add: .
           message: "Update wiki docs"
           default_author: github_actions
@@ -85,7 +75,7 @@ jobs:
         id: parent_commit
         uses: EndBug/add-and-commit@v10
         with:
-          add: docs/wiki
+          add: .wiki
           message: "Update wiki submodule pointer"
           default_author: github_actions
           pull: "--rebase"

.gitmodules

@@ -1,3 +1,3 @@
 [submodule "docs/wiki"]
-	path = docs/wiki
+	path = .wiki
 	url = https://github.com/php-fast-forward/dev-tools.wiki.git

docs/configuration/index.rst

@@ -0,0 +1,14 @@
+Configuration
+=============
+
+FastForward DevTools is strictly built on the philosophy of **Convention over Configuration**. This section explains how configurations are supplied by default and how they can be modified.
+
+By default, the plugin aims to provide zero-configuration setups for all underlying QA tools. However, identifying that advanced scenarios may require specific rulesets or paths, the architecture supports granular overrides locally within your project context.
+
+In this Section
+---------------
+
+.. toctree::
+   :maxdepth: 1
+
+   overriding-defaults

docs/configuration/overriding-defaults.rst

@@ -0,0 +1,25 @@
+Overriding Defaults
+===================
+
+When invoked, the internal toolkit instances dramatically minimize setup times by dynamically reverting to sensible, strict configuration defaults securely bundled within the ``fast-forward/dev-tools`` package itself.
+
+However, recognizing that specific projects may have edge-cases or expanded scopes, DevTools allows you to effortlessly override these settings locally.
+
+How to Override
+---------------
+
+To override a default setup, simply create the corresponding configuration file mapped firmly onto your generic root application path:
+
+- ``ecs.php`` (for Code Style specifications)
+- ``rector.php`` (for Application Refactoring targets)
+- ``phpunit.xml`` (for managing Testing suites)
+
+Resolution Logic
+----------------
+
+The internal execution engine (housed in ``AbstractCommand``) invokes ``getConfigFile()``. This method specifically verifies the presence of the configuration file inside your project’s working directory:
+
+1. If the mapped configuration file *exists*, tools utilize the custom instructions provided within your project.
+2. If the configuration file is *absent*, the ``dev-tools`` process securely abstracts the instruction and dynamically relays it to the standard template preserved within the Composer installation path.
+
+This guarantees robust predictability while maintaining advanced customization capabilities reliably.

docs/getting-started/index.rst

@@ -0,0 +1,20 @@
+Getting Started
+===============
+
+Welcome to the FastForward DevTools getting started guide. This section provides an introduction to the ``fast-forward/dev-tools`` package, explaining its purpose and guiding you through the environment preparation.
+
+What is FastForward DevTools?
+-----------------------------
+
+Configuring tools like PHPUnit, Rector, PHP-CS-Fixer, EasyCodingStandard (ECS), and phpDocumentor in every new project leads to excessive boilerplate. FastForward DevTools eliminates this configuration fatigue by providing sensible defaults and a unified execution interface (``composer dev-tools``) out of the box.
+
+When you add this package as a development dependency, your project automatically inherits a unified command-line toolchain designed to ensure that all your projects adhere to the same rigorous standards without manual bootstrapping.
+
+In this Section
+---------------
+
+.. toctree::
+   :maxdepth: 1
+
+   installation
+   supported-php-versions

docs/getting-started/installation.rst

@@ -0,0 +1,26 @@
+Installation
+============
+
+Because FastForward DevTools operates as a Composer plugin, the installation process seamlessly integrates its commands directly into your project environment automatically.
+
+Requirements
+------------
+
+Ensure you meet the basic requirements described in `Supported PHP Versions <supported-php-versions>`_.
+
+Using Composer
+--------------
+
+Require the package as a development dependency using Composer:
+
+.. code-block:: bash
+
+   composer require --dev fast-forward/dev-tools
+
+What happens during installation?
+---------------------------------
+
+1. Composer installs the package alongside its underlying tool dependencies (``symplify/easy-coding-standard``, ``rector/rector``, ``phpunit/phpunit``, ``phpdocumentor/shim``, etc.).
+2. The internal ``Plugin`` provider securely audits your ``composer.json`` file.
+3. The plugin natively injects the ``composer-command-provider`` instructions containing ``DevToolsCommandProvider::class`` into your ``extra`` configuration block.
+4. Finally, it initializes the ``dev-tools`` executable script shortcut globally within your project, making commands accessible via ``composer dev-tools``.

docs/getting-started/supported-php-versions.rst

@@ -0,0 +1,12 @@
+Supported PHP Versions
+======================
+
+This library explicitly utilizes modern PHP typed properties, union types, strict definitions, and ``match`` expressions internally. As such, the supported engine versions are strictly managed.
+
+Minimum Requirements
+--------------------
+
+- **Minimum PHP Version:** ``^8.3``
+- **Recommended PHP Version:** 8.3 or greater
+
+Please ensure your local environment and Continuous Integration (CI) pipelines satisfy the PHP 8.3 minimum constraints prior to installation. Execution against older versions is officially unsupported and may result in parsing failures.

docs/index.rst

@@ -0,0 +1,50 @@
+.. toctree::
+   :hidden:
+   :titlesonly:
+
+   getting-started/index
+   configuration/index
+   running/index
+   internals/index
+
+FastForward DevTools Guide
+=========================
+
+Welcome to the documentation for FastForward DevTools.
+
+FastForward DevTools is a modern orchestration toolkit for PHP projects, providing a unified interface for quality assurance and static analysis tools. With this toolkit, you can automate code style checks, refactoring, testing, and documentation generation across your PHP codebase.
+
+This documentation is organized into the following sections:
+
+- **Getting Started** — Quick tutorials to get you up and running in minutes. See :doc:`getting-started/index`.
+- **Configuration** — Learn how to customize and override default behaviors. See :doc:`configuration/index`.
+- **Running the Tools** — Discover how to run the unified and specialized commands. See :doc:`running/index`.
+- **Internals** — Dive into the architecture and design of the toolkit. See :doc:`internals/index`.
+
+What does it do?
+----------------
+
+By analyzing your PHP source code and configuration, FastForward DevTools automates the execution of QA tools, making it indispensable for teams seeking consistent, high-quality codebases.
+
+In addition to orchestrating standard tools, FastForward DevTools provides:
+
+- Unified command-line interface for all QA operations
+- Automatic configuration and sensible defaults
+- Support for custom project overrides
+- Seamless integration with Composer
+
+Inspired by best practices and modern PHP standards, FastForward DevTools helps you maintain, refactor, and document your projects efficiently.
+
+Where to start?
+---------------
+
+We have divided the documentation into 4 sections:
+
+1. :doc:`getting-started/index` — concise tutorials to help you get started quickly.
+2. :doc:`configuration/index` — in-depth guides on customizing and configuring the toolkit.
+3. :doc:`running/index` — reference for all available commands and features.
+4. :doc:`internals/index` — for contributors and those interested in the internal architecture.
+
+.. hint::
+
+   The documentation pages you are currently reading are generated using FastForward DevTools and serve as a real-world example of its capabilities.

docs/internals/architecture.rst

@@ -0,0 +1,25 @@
+Architecture and Command Lifecycle
+==================================
+
+Understanding the structural execution behavior naturally highlights the toolkit's strict stability expectations.
+
+1. Plugin Initialization
+------------------------
+
+Upon invoking composer context triggers, the overarching ``Plugin`` class initializes. Acting in isolation, it intercepts generic triggers dynamically providing seamless integration without modifying your ``composer.json`` destructively beyond safe metadata insertions. It relies meticulously on the ``Composer\Plugin\Capable`` interface implementation natively.
+
+2. Dynamic Command Provider
+---------------------------
+
+A dedicated constraint definition mapped to ``DevToolsCommandProvider`` statically compiles specific functional dependencies securely. This system registers commands directly into Composer’s known operational boundaries cleanly, allowing generic shell commands (e.g. ``composer dev-tools``) to act natively like binary scripts correctly.
+
+3. Abstract Execution Layer
+---------------------------
+
+Functional execution contexts actively inherit orchestrated, inherently isolated structures directly via ``AbstractCommand``. Features abstracted inside this definition include:
+
+* **Path Resolution:** Computing absolute execution binaries securely via ``getAbsolutePath()``.
+* **Metadata Integration:** Deriving target properties intelligently relying natively on ``getPsr4Namespaces()``.
+* **Operational Execution:** Governing generic isolated context processing triggering fully operational and robust ``Symfony\Component\Process\Process`` structures successfully executing targeted binaries recursively cleanly.
+
+By preserving logical domains explicitly, developers ensure dependencies evaluate natively mitigating unwanted conflicts transparently openly natively.

docs/internals/index.rst

@@ -0,0 +1,14 @@
+Internals
+=========
+
+This section dictates a technical examination of the core operational architectures establishing ``fast-forward/dev-tools`` functionally. Understanding how the dev-tools plugin natively injects execution pathways helps guarantee a pristine CI/CD experience and serves as a guide for contributors mapping out the codebase.
+
+The system relies heavily on Composer Plugin capabilities, utilizing native API hooks to inject scripts and Command Providers gracefully.
+
+In this Section
+---------------
+
+.. toctree::
+   :maxdepth: 1
+
+   architecture