discovery: map L1 packages vs standalone php-* modules #3

Closed
opened 2026-02-20 01:51:15 +00:00 by Clotho · 0 comments
Member

Objective

The framework has L1 packages embedded in src/Core/ (Activity, Bouncer, Cdn, Config, Front, Lang, Media, Search, Seo). There are also standalone repos: core/php-tenant, core/php-admin, core/php-api, core/php-content, core/php-commerce, core/php-agentic, core/php-mcp, core/php-developer, core/php-devops.

Task

  1. List every directory under src/Core/ and src/Core/Front/ that has a Boot.php
  2. For each, determine if there is a matching standalone core/php-* repo
  3. Check for overlap: does the standalone repo duplicate code from the framework, or does it extend it?
  4. Check composer.json in each standalone repo to see how it depends on the framework

Output

Create issues on forge.lthn.ai for each finding using the API:

FORGE_TOKEN="$FORGE_TOKEN_PROD"
FORGE_API="https://forge.lthn.ai/api/v1"

# Get label IDs
REVIEW_LABEL=41
DISCOVERY_LABEL=42

# Create issue for each finding
curl -sf -X POST -H "Authorization: token $FORGE_TOKEN" -H "Content-Type: application/json" \
  "$FORGE_API/repos/core/php-framework/issues" \
  -d "{\"title\":\"finding: description\",\"body\":\"details\",\"labels\":[$REVIEW_LABEL,$DISCOVERY_LABEL]}"

For each overlap found, create an issue with:

  • Title: finding: {L1 package} overlaps with core/php-{module}
  • Body: what overlaps, what differs, recommendation (extract, merge, or keep separate)
  • Labels: review + discovery

Also create a summary issue listing all L1 packages and their status.

Branch

Work from dev branch. Read-only analysis - do not modify code.

## Objective The framework has L1 packages embedded in src/Core/ (Activity, Bouncer, Cdn, Config, Front, Lang, Media, Search, Seo). There are also standalone repos: core/php-tenant, core/php-admin, core/php-api, core/php-content, core/php-commerce, core/php-agentic, core/php-mcp, core/php-developer, core/php-devops. ## Task 1. List every directory under src/Core/ and src/Core/Front/ that has a Boot.php 2. For each, determine if there is a matching standalone core/php-* repo 3. Check for overlap: does the standalone repo duplicate code from the framework, or does it extend it? 4. Check composer.json in each standalone repo to see how it depends on the framework ## Output Create issues on forge.lthn.ai for each finding using the API: ```bash FORGE_TOKEN="$FORGE_TOKEN_PROD" FORGE_API="https://forge.lthn.ai/api/v1" # Get label IDs REVIEW_LABEL=41 DISCOVERY_LABEL=42 # Create issue for each finding curl -sf -X POST -H "Authorization: token $FORGE_TOKEN" -H "Content-Type: application/json" \ "$FORGE_API/repos/core/php-framework/issues" \ -d "{\"title\":\"finding: description\",\"body\":\"details\",\"labels\":[$REVIEW_LABEL,$DISCOVERY_LABEL]}" ``` For each overlap found, create an issue with: - Title: `finding: {L1 package} overlaps with core/php-{module}` - Body: what overlaps, what differs, recommendation (extract, merge, or keep separate) - Labels: review + discovery Also create a summary issue listing all L1 packages and their status. ## Branch Work from dev branch. Read-only analysis - do not modify code.
Clotho added the
clotho
discovery
labels 2026-02-20 01:51:15 +00:00
Snider added reference main 2026-02-20 01:58:02 +00:00
Charon added
PHP
P3
and removed
clotho
discovery
labels 2026-02-20 12:17:15 +00:00
Sign in to join this conversation.
No description provided.