Skip to content

Extract Code Standards: formatting, PHPDoc and explicit refactoring #1

Open

Description

@coisa

Extraction epic and first increment

Canonical destination for php-fast-forward/dev-tools#379.
This migration transfers ownership and preserves unfinished requirements; it does not mark extraction complete. PR #7 delivers only the initial runnable slice and must not close this epic.

Domain roadmap

  • Verify fork PR automation and fresh Composer distribution #2 owns fresh distribution/fork/runtime compatibility; Decide and prototype the bounded static-analysis profile #3 evaluates a bounded static-analysis profile, without silently migrating undecided DevTools analysis issues.
  • Extract PHPDoc policy and opt-in semantic refactoring #4 owns source PHPDoc and explicit opt-in semantic refactoring, including local config imports/public APIs and one canonical consumer procedure. LLM Skills owns discovery/install/update; no new installer or sync command.
  • Compare resolved ECS and CoiSA policies with golden fixtures #5 owns resolved rule-by-rule comparison: headers, Finder scope, risky policies, PHP minimum/target, precedence, custom Rector PHPDoc, golden/idempotence fixtures and selection of one canonical fixer policy.
  • Verify reviewed 0.x Changelog lifecycle and release gates #6 owns real current-head Codex and CodeRabbit release reviews, supported no-tag bootstrap and 0.x-only automation publication.
  • Optional phpmnd and Twig evaluations have separate linked destinations; neither blocks 0.1.0.
  • Preserve existing public configuration, local imports, deterministic exits/JSON contracts, CWD/cache/color controls and consumer PHP compatibility. Full scan on rules/config/dependency changes; never silently upgrade dependencies or mutate in check.
  • Keep rendered docs, application tests, coverage/reports, Composer metadata normalization, orchestration and repository governance outside this runtime. Coordinate normalization with its one writer rather than copy it.
  • Do not migrate consumers until release/ref/skill compatibility and archive/installed-runtime evidence are established, and a pilot is separately authorized.

First increment outcome

Build the first runnable standalone fast-forward/code-standards library/CLI and reviewable repository structure. Reference: php-fast-forward/dev-tools#379. No production dependency on DevTools.

Scope and acceptance

  • Non-risky ECS PSR12 preset with consumer callback overrides, PHP runtime >=8.3, explicit check/fix separation. Resolved ECS 13.3.8 deprecates the old dynamic Symfony preset API as a no-op, so the initial slice uses the supported prepared PSR12 set and records the policy delta; complete parity remains Compare resolved ECS and CoiSA policies with golden fixtures #5.
  • Static quality is initially PHP syntax parsing; no claim of type analysis or semantic migration parity.
  • Tracked full scans and exact PR base/head merge-base selection, NUL-delimited paths, rename destinations/deletions, bounded argument arrays, exit propagation, no source writes in check.
  • Canonical consumer skill, small Action/reusable workflow and inactive pinned consumer wrapper; own CI on hosted runners only.
  • Regression fixtures for violations/no-write/fix/idempotence, malformed options/history/paths and branch divergence.
  • Document policy differences and keep existing consumer integrations untouched.
  • Prepare Changelog automation for initial 0.1.0 using supported fragment impact from baseline 0.0.0; no manual tags.

Dependencies and gates

No implementation prerequisite. This is the initial slice; later issues deepen analysis, compatibility and distribution. Create all initial issues before publishing its implementation PR. Every PR including version PR requires successful current-head checks and actual Codex AND CodeRabbit reviews with no pending findings before normal merge. If either integration is unavailable, report and stop merge; no OAuth/permission changes or substitute self-review.

No application tests/coverage/reports orchestration, consumer migration, global Changelog engine changes, security-setting changes or 1.x publication.

Activity

  1. changed the title [-]Bootstrap standalone style and syntax checks with explicit fixes[/-] [+]Extract Code Standards: formatting, PHPDoc and explicit refactoring[/+] on Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions