Where does the e2e Practice Pack live, and what name prefix does it own? #545

Activity

1. orioltf

   added

   app:unic-archon-dlc

   wayfinder:grillingWayfinder ticket: decide it by grillingWayfinder ticket: decide it by grilling

   on Sep 23, 2026
2. orioltf

   added a parent issue on Sep 23, 2026

   • wayfinder: e2e specs from acceptance criteria, at a second Consumer #538
3. orioltf

   marked this as blocked by 2 issues on Sep 23, 2026

   • Is the internal QA plugin's content reused in the e2e Practice Pack, and on what terms? #544
   • Practice Packs must stack: /setup replaces .archon/methods/ wholesale, and the override tier was deleted #520
4. orioltf commented on Oct 1, 2026

   

   orioltf

   on Oct 1, 2026

   Last edited by orioltf

   MemberAuthor

   More actions

   Input: what goes into the Practice Pack, and what stays with the Consumer, 2026-10-01

   The maintainer asked whether the Consumer-side changes from #543 would go into a Playwright Practice Pack: the CLAUDE.md pointer, the suite README and the setup. This is input for this ticket. It decides nothing.

   The test: would it still be true in another Consumer that uses Playwright? If yes, it belongs in the Practice Pack. If no, it stays in the Consumer's own context.

   Piece	True in another Consumer?	Where it goes
   The fixtures import pattern, Page Objects, test.step, the criterion ID in the test title	yes	Practice Pack
   Cross-platform script rules, a reviewer checklist for test code, a reference architecture	yes	Practice Pack, under the terms of #544
   The sabotage technique from #540, and a tag scheme of smoke tests first and feature tests in later stages	yes	Practice Pack
   The actual tags, the suite's paths, its environments and its access secret	no	the Consumer's suite README
   Who owns which part of the suite directory, and the review rule	no	the Consumer
   Setup, teardown and test data	no: #550 gives them to the suite's author	the Consumer. The Practice Pack may carry a template, never the data
   The line in CLAUDE.md that points at the conventions	the mechanism yes, the content no	written when the Practice Pack is installed, as a managed block, the way /setup writes the DLC's blocks

   Two risks to weigh here:

   1. Two copies of the same conventions drift apart. If the Practice Pack carries the conventions the Consumer's README already states, the two copies diverge, the same risk wayfinder: e2e specs from acceptance criteria, at a second Consumer #538's fog records for the internal QA plugin. One shape avoids it: the Practice Pack carries the defaults, and the Consumer's README states only where it differs. The Consumer already uses this shape for another of its generators, whose conventions file names its own exception as "the exception, not the pattern".
   2. Extracting from one Consumer. One Consumer uses Playwright today. What is generic in its conventions is a guess until a second Consumer confirms it. Proposed: for now the Consumer's README stays the authority. When a second Consumer arrives, the shared part moves into the Practice Pack.

   How a Practice Pack installs and stacks, including whether it writes a managed block into CLAUDE.md, is #520's question.
5. orioltf

   unmarked this as blocked on Oct 20, 2026

   • Is the internal QA plugin's content reused in the e2e Practice Pack, and on what terms? #544
6. orioltf commented on Oct 21, 2026

   

   orioltf

   on Oct 21, 2026

   MemberAuthor

   More actions

   What Practice Packs must stack now gives this ticket, 2026-10-21

   #520 has approved criteria and is ready-for-agent. Its decisions 5 and 6 bound the choice this ticket makes:

   • The prefix. Pick one prefix for the e2e Practice Pack. It must not be unic-dlc or unic-archon-dlc, which are reserved. Whether one prefix may begin another is still open on Practice Packs must stack: /setup replaces .archon/methods/ wholesale, and the override tier was deleted #520, so prefer a prefix that neither begins nor is begun by unic-dlc.
   • What the prefix owns. The pack's installer reads, writes, overwrites or removes only .claude/skills/<prefix>-*/, a <prefix>:begin / <prefix>:end block in the Consumer's CLAUDE.md and in each line-based formatter ignore file, and .archon/packs/<prefix>.config.yaml for its default values. It assumes nothing about any other name, and stops and asks if another pack holds its prefix.
   • What it ships. Context artefacts and default config values only, never a Box or a Method. Its conventions reach a Box run through its own CLAUDE.md block, which points at them.
   • The CLAUDE.md question from comment 5928278130 is answered: yes, the pack writes its own managed block, under its own markers.

   Still this ticket's to decide: where the pack's own repository lives, and the prefix itself.