fix(cli): translate output differs in bytes from install output

Offen
#1,312 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
cli, testing

Rechercherichtung

Start with cli/tests/contexts/translate/application/translate-distribution-conformance.integration.test.ts on the refactor/cli-target branch and read its DIVERGENCES and MANIFEST_DIVERGENCES entries. For each entry, remove its allowance and use the failing test to identify the translate and install paths involved. The work is done when both paths produce the same bytes or the difference has a documented decision, and the conformance test passes.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Description

aidd translate output differs in bytes from what an install writes for the same plugins. The differences are currently named, and tolerated, by a conformance test on the refactor/cli-target branch. They are listed here so each can be fixed or accepted on purpose. Path A is the translate output (disk), path B is the install output.

Affected file(s)

cli/tests/contexts/translate/application/translate-distribution-conformance.integration.test.ts on refactor/cli-target (DIVERGENCES, MANIFEST_DIVERGENCES). Not on next yet: next has no conformance test for it.

Expected behaviour

Translate and install write the same bytes for the same content, or each difference is a documented decision.

Observed behaviour

DIVERGENCES:

  1. A rewrites an @relative reference into a markdown link.
  2. A namespaces an agent's name.
  3. A renames a flat skill after its folder (opencode, kilo).
  4. B keeps only a Codex skill's name and description.
  5. A leaves the {{TOOLS}} placeholder, B resolves it to .github/ (copilot).
  6. B copies the source mcp and hooks manifests, A synthesizes them elsewhere.

MANIFEST_DIVERGENCES:
7. B writes the manifest at the plugin root, A in the tool's own manifest directory.
8. A lists the components and drops strict, B copies the source manifest byte for byte.

Markdown is compared as frontmatter data plus body, since B re-serializes the frontmatter, so frontmatter byte differences come on top of this list.

AI tool

All (entries 3 to 5 are tool specific)

aidd-cli version

unreleased, next

OS

Any

Additional context

The test fails when an entry is no longer needed and when a difference is not named, so the list only shrinks. Work through it entry by entry: remove the entry, watch the conformance test go red for that entry alone, make the two paths agree (or record the decision), keep the test green.

Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
91

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.