@danmoisan/drm-copilot-mcp 1.1.23 → 1.1.25

package/resources/claude-customizations/.claude/skills/discovery-repo-inventory/SKILL.md

@@ -1,80 +1,46 @@
 ---
 name: discovery-repo-inventory
-description: 'Drive the language-neutral repository and project inventory analyzer for the discovery workflow. Use when running the inventory stage against the domain profile source and target roots, recording analyzer outputs under the profile artifacts root, and running stack-specific analyzers generically per the profile technology stack. Second stage after profile load.'
-allowed-tools: Bash Read Glob Grep
+description: 'Dispatch repository inventory to the canonical legacy inventory workflow. Use when invoking the existing discovery repo-inventory alias.'
 ---
 
-# Discovery Repo Inventory
-
-Runs the inventory stage of the discovery and parity-definition workflow. It
-drives the language-neutral repository/project inventory analyzer against the
-roots declared in the domain profile, records outputs under the profile's
-artifact root, and then runs any stack-specific analyzers generically, without
-naming any concrete technology. All domain specificity is read from the domain
-profile at runtime.
+# Discovery Repository Inventory Alias
 
 ## When to Use This Skill
 
-- You have loaded the domain profile and are ready to inventory the legacy
-  source and the modern target.
-- You need analyzer outputs recorded as evidence for the coverage stage.
-
-## Prerequisites
-
-- The domain profile loads via `dev.discovery.profile`.
-- The analyzer framework CLI is available (referenced by name only; the full
-  registry lives in `discovery-workflow`).
-
-## Workflow
+Use this compatibility name only to dispatch to its canonical workflow.
 
-1. **Load the domain profile.** Run `dev.discovery.profile` to load and echo the
-   consumer repository's `discovery-profile.yaml`. Read the following keys and
-   use them for every subsequent step; do not hard-code any of them:
-   - `legacy_source.root` — the legacy application source root.
-   - `target.root` — the modern target root.
-   - `artifacts.root` — where analyzer outputs and discovery artifacts are
-     recorded.
-   - `technology_stack` — the declared stack, used to select stack-specific
-     analyzers generically.
+## Inputs
 
-2. **Run the language-neutral inventory analyzer.** Drive the inventory command
-   (assumed `dev.discovery.inventory`; see the fan-in note below) against
-   `legacy_source.root` and `target.root`. Record all outputs under
-   `artifacts.root` following the profile's artifact conventions.
+| Input | Required contract |
+| --- | --- |
+| inputs | Required inputs of the linked canonical workflow, forwarded unchanged. |
 
-   **Fan-in reconciliation assumption:** the inventory command name
-   `dev.discovery.inventory` is assumed and may be renamed when the analyzer
-   framework (epic #9006) lands. The canonical registry entry and this fragment
-   are the only two locations to reconcile; the canonical entry lives in
-   `discovery-workflow`.
+Forward all other supplied canonical inputs to the selected target. These
+alias selectors are not service-request fields. A fixed mapping requires no
+additional selector; it does not add fields to `prepare-agent`.
 
-3. **Run stack-specific analyzers generically.** For the declared
-   `technology_stack`, run any stack-specific analyzer commands documented by the
-   analyzer framework. Do not name a concrete analyzer or technology here; the
-   profile's `technology_stack` value selects the applicable analyzers at
-   runtime. Record their outputs under `artifacts.root` as well.
+## Dispatch
 
-4. **Record evidence references.** Capture each analyzer output as an
-   evidence-reference instance so downstream stages can cite provenance.
+| Selector | Canonical skill |
+| --- | --- |
+| fixed | inventory-legacy-system |
 
-## Validation
+Dispatch directly to `inventory-legacy-system`. Its prepared Legacy Parity Analyst owns inventory and selected coverage dispositions; this alias grants no role or tool.
 
-- Before the inventory stage begins, confirm the profile is valid with
-  `dev.discovery.validate-profile`.
-- After recording evidence references, validate them with
-  `dev.discovery.validate-evidence-reference`.
-- An empty error list is a pass. On any error, follow the direction in
-  `discovery-validate-artifacts`, which owns the canonical validation-gate
-  mechanics.
+This alias has no independent output or write authority. Do not duplicate
+business validation, call tools independently, create a receipt, change a model
+or auto-launch a role. Use only the linked canonical workflow's lifecycle and
+exact grants; no alias chain or filesystem fallback is permitted.
 
-## Referenced Skills
+## Stop and result
 
-- `discovery-workflow` — stage order and the canonical Referenced Contracts
-  registry (analyzer command, agent slugs, schema paths, validators).
-- `discovery-validate-artifacts` — pass/fail semantics and error routing.
+Return the selected canonical workflow's explicit result and references without
+changing failed, blocked, pending or incremental outcomes into completion.
+An unknown selector fails with no fallback. Missing configuration or native
+capability is handled by the canonical workflow, including initialization's
+explicit root bootstrap exception. The alias cannot bypass prepare/finalize or
+native start/stop requirements.
 
-## Notes
+## References
 
-- This skill introduces no domain-specific identifier. Source root, target root,
-  artifact root, and stack are all read from the domain profile at runtime.
-- Outputs from this stage feed `discovery-coverage-ledger`.
+- [inventory-legacy-system](../inventory-legacy-system/SKILL.md)

package/resources/claude-customizations/.claude/skills/discovery-runtime-characterization/SKILL.md

@@ -1,63 +1,46 @@
 ---
 name: discovery-runtime-characterization
-description: 'Produce runtime characterization scenarios and evidence references in the discovery workflow. Use when characterizing observed runtime behavior of the legacy application into scenarios with supporting evidence and routing analysis to the runtime role. Fourth stage, after coverage and before parity.'
+description: 'Dispatch runtime characterization to its canonical supplied-evidence workflow. Use when invoking the existing runtime-characterization alias.'
 ---
 
-# Discovery Runtime Characterization
-
-Runs the runtime characterization stage of the discovery and parity-definition
-workflow. It captures observed runtime behavior of the legacy application as
-characterization scenarios, each backed by evidence references, so that parity
-analysis can compare intended contracts against observed behavior. All domain
-specificity is read from the domain profile at runtime.
+# Discovery Runtime Characterization Alias
 
 ## When to Use This Skill
 
-- Feature contracts and the coverage ledger exist from the coverage stage.
-- You need documented runtime behavior scenarios before building the parity
-  matrix.
-
-## Prerequisites
-
-- `discovery-coverage-ledger` has completed.
-- The domain profile is loaded and valid.
-
-## Workflow
-
-1. **Produce characterization scenarios.** For each behavior requiring runtime
-   observation, produce a scenario conforming to the schema
-   `schemas/discovery/v1/runtime-characterization-scenario.schema.json`. Each
-   scenario records the observed runtime behavior in a domain-neutral form.
+Use this compatibility name only to dispatch to its canonical workflow.
 
-2. **Record evidence references.** Attach evidence to each scenario as
-   evidence-reference instances conforming to the schema
-   `schemas/discovery/v1/evidence-reference.schema.json`, so the provenance of
-   each observation is traceable.
+## Inputs
 
-3. **Route analysis.** Hand the scenarios to the runtime role for analysis (see
-   `## Worker Routing`).
+| Input | Required contract |
+| --- | --- |
+| inputs | Required inputs of the linked canonical workflow, forwarded unchanged. |
 
-## Worker Routing
+Forward all other supplied canonical inputs to the selected target. These
+alias selectors are not service-request fields. A fixed mapping requires no
+additional selector; it does not add fields to `prepare-agent`.
 
-- Worker: `runtime-characterization-analyst`
+## Dispatch
 
-The runtime role analyzes and confirms each characterization scenario and its
-evidence before the workflow proceeds to parity.
+| Selector | Canonical skill |
+| --- | --- |
+| fixed | characterize-runtime-behavior |
 
-## Validation
+Dispatch directly to `characterize-runtime-behavior`. The canonical workflow preserves supplied evidence and honest manual, not-run or blocked states; the alias does not execute applications.
 
-- Validate scenarios with `dev.discovery.validate-runtime-scenario`.
-- Validate evidence references with `dev.discovery.validate-evidence-reference`.
-- An empty error list is a pass. On any error, follow the direction in
-  `discovery-validate-artifacts`.
+This alias has no independent output or write authority. Do not duplicate
+business validation, call tools independently, create a receipt, change a model
+or auto-launch a role. Use only the linked canonical workflow's lifecycle and
+exact grants; no alias chain or filesystem fallback is permitted.
 
-## Referenced Skills
+## Stop and result
 
-- `discovery-workflow` — stage order and the canonical Referenced Contracts
-  registry.
-- `discovery-validate-artifacts` — pass/fail semantics and error routing.
+Return the selected canonical workflow's explicit result and references without
+changing failed, blocked, pending or incremental outcomes into completion.
+An unknown selector fails with no fallback. Missing configuration or native
+capability is handled by the canonical workflow, including initialization's
+explicit root bootstrap exception. The alias cannot bypass prepare/finalize or
+native start/stop requirements.
 
-## Notes
+## References
 
-- Scenarios and evidence references from this stage are consumed by
-  `discovery-parity-matrix`.
+- [characterize-runtime-behavior](../characterize-runtime-behavior/SKILL.md)

package/resources/claude-customizations/.claude/skills/discovery-validate-artifacts/SKILL.md

@@ -1,79 +1,46 @@
 ---
 name: discovery-validate-artifacts
-description: 'Canonical validation-gate mechanics for the discovery workflow. Use when running the per-artifact discovery validators after each stage and the completion gate at the end, interpreting the empty-error-list pass semantics, and routing any validator error back to the owning stage skill. Seventh and final stage.'
-allowed-tools: Bash Read
+description: 'Dispatch artifact validation to the canonical explicit-kind and mode workflow. Use when invoking the existing validate-artifacts alias.'
 ---
 
-# Discovery Validate Artifacts
-
-Owns the canonical validation-gate mechanics for the discovery and
-parity-definition workflow. Each discovery artifact is validated against its
-schema by a `dev.discovery.validate-*` console script after its owning stage,
-and `dev.discovery.validate-all` runs as the workflow completion gate. This skill
-is the single canonical location for the pass/fail semantics; stage skills defer
-to it by name.
+# Discovery Artifact Validation Alias
 
 ## When to Use This Skill
 
-- A stage has produced an artifact and you need to validate it before the next
-  stage proceeds.
-- You have completed all stages and need to run the workflow completion gate.
-- A validator reported errors and you need the routing rule back to the owning
-  stage skill.
-
-## Prerequisites
-
-- The relevant discovery artifacts exist under the profile's artifact root.
-- The validator console scripts are available (registry in `discovery-workflow`).
-
-## Pass/Fail Semantics
-
-Every `dev.discovery.validate-*` invocation yields a `list[str]` of error
-messages. An empty list is a pass; a non-empty list is a failure whose entries
-name the exact problems. The validators never mutate the artifacts they check.
+Use this compatibility name only to dispatch to its canonical workflow.
 
-## Per-Stage Validators
+## Inputs
 
-Run each validator after its owning stage produces its artifact. On a non-empty
-error list, return to the named owning stage skill, correct the artifact, and
-re-run the validator until the list is empty.
+| Input | Required contract |
+| --- | --- |
+| inputs | Required inputs of the linked canonical workflow, forwarded unchanged. |
 
-| Validator | Validates schema | Owning stage skill |
-|---|---|---|
-| `dev.discovery.validate-profile` | (domain profile) | `discovery-repo-inventory` |
-| `dev.discovery.validate-evidence-reference` | `schemas/discovery/v1/evidence-reference.schema.json` | `discovery-repo-inventory`, `discovery-runtime-characterization` |
-| `dev.discovery.validate-feature-contract` | `schemas/discovery/v1/feature-contract.schema.json` | `discovery-coverage-ledger` |
-| `dev.discovery.validate-coverage-ledger` | `schemas/discovery/v1/coverage-ledger.schema.json` | `discovery-coverage-ledger` |
-| `dev.discovery.validate-runtime-scenario` | `schemas/discovery/v1/runtime-characterization-scenario.schema.json` | `discovery-runtime-characterization` |
-| `dev.discovery.validate-parity-matrix` | `schemas/discovery/v1/parity-matrix.schema.json` | `discovery-parity-matrix` |
-| `dev.discovery.validate-unspecified-behavior` | `schemas/discovery/v1/unspecified-behavior-record.schema.json` | `discovery-behavior-reconciliation` |
-| `dev.discovery.validate-product-decision` | `schemas/discovery/v1/product-decision-record.schema.json` | `discovery-behavior-reconciliation` |
+Forward all other supplied canonical inputs to the selected target. These
+alias selectors are not service-request fields. A fixed mapping requires no
+additional selector; it does not add fields to `prepare-agent`.
 
-## Completion Gate
+## Dispatch
 
-After all stages pass their per-stage validators, run
-`dev.discovery.validate-all` as the workflow completion gate. It validates the
-full artifact set across all seven schemas under `schemas/discovery/v1/`:
+| Selector | Canonical skill |
+| --- | --- |
+| fixed | validate-discovery-artifacts |
 
-- `schemas/discovery/v1/feature-contract.schema.json`
-- `schemas/discovery/v1/coverage-ledger.schema.json`
-- `schemas/discovery/v1/runtime-characterization-scenario.schema.json`
-- `schemas/discovery/v1/parity-matrix.schema.json`
-- `schemas/discovery/v1/unspecified-behavior-record.schema.json`
-- `schemas/discovery/v1/product-decision-record.schema.json`
-- `schemas/discovery/v1/evidence-reference.schema.json`
+Dispatch directly to `validate-discovery-artifacts`. Forward its exact artifact kind/selection and explicit mode without type probing or substituting a different gate.
 
-An empty error list from `dev.discovery.validate-all` means the workflow is
-complete. A non-empty list names the exact artifact and problem; route each entry
-back to its owning stage skill using the per-stage table above, correct the
-artifact, and re-run the gate.
+This alias has no independent output or write authority. Do not duplicate
+business validation, call tools independently, create a receipt, change a model
+or auto-launch a role. Use only the linked canonical workflow's lifecycle and
+exact grants; no alias chain or filesystem fallback is permitted.
 
-## Referenced Skills
+## Stop and result
 
-- `discovery-workflow` — stage order and the canonical Referenced Contracts
-  registry (analyzer command, agent slugs, schema paths, validators).
+Return the selected canonical workflow's explicit result and references without
+changing failed, blocked, pending or incremental outcomes into completion.
+An unknown selector fails with no fallback. Missing configuration or native
+capability is handled by the canonical workflow, including initialization's
+explicit root bootstrap exception. The alias cannot bypass prepare/finalize or
+native start/stop requirements.
 
-## Notes
+## References
 
-- This skill names no domain-specific identifier; artifact locations are read
-  from the domain profile at runtime.
+- [validate-discovery-artifacts](../validate-discovery-artifacts/SKILL.md)

package/resources/claude-customizations/.claude/skills/discovery-workflow/SKILL.md

@@ -1,146 +1,62 @@
 ---
 name: discovery-workflow
-description: 'Umbrella sequencing skill for the domain-neutral legacy discovery and parity-definition workflow. Use when onboarding or running the end-to-end discovery workflow across inventory, coverage, runtime characterization, parity, behavior reconciliation, and the validation gate, and when reconciling upstream analyzer and agent contract names. Holds the canonical Referenced Contracts registry.'
+description: 'Dispatch an explicit canonical discovery workflow without adding authority. Use when invoking the legacy discovery umbrella with a selected skill_id.'
 ---
 
-# Discovery Workflow
-
-Sequences the reusable, domain-neutral discovery and parity-definition workflow
-end to end. This skill is the entry point: it establishes the stage order,
-directs each stage to its owning skill, and holds the single canonical registry
-of upstream contract names (analyzer CLI commands, agent slugs, schema paths,
-and validators).
-
-All domain specificity is read at runtime from the consumer repository's domain
-profile (`discovery-profile.yaml`) via `dev.discovery.profile`. This skill names
-no concrete repository, path, or technology stack.
+# Discovery Workflow Alias
 
 ## When to Use This Skill
 
-- You are onboarding the discovery and parity-definition workflow in a consumer
-  repository and need the documented stage order.
-- You need the canonical list of upstream contract names to reconcile a renamed
-  analyzer command or agent slug at epic fan-in.
-- You need to know which stage skill owns which artifact and validator.
-
-## Prerequisites
-
-- A `discovery-profile.yaml` domain profile exists in the consumer repository and
-  loads cleanly via `dev.discovery.profile`.
-- The analyzer framework CLI and the four generic agent roles are available in
-  the consumer environment (referenced here by name only).
-
-## Stage Order
-
-Run the workflow in this fixed order. Each stage validates its artifacts before
-the next stage proceeds:
-
-1. **profile** — load and echo the domain profile via `dev.discovery.profile`.
-2. **inventory** — drive the language-neutral repository/project inventory
-   analyzer (`discovery-repo-inventory`).
-3. **coverage** — produce feature contracts and the coverage ledger
-   (`discovery-coverage-ledger`).
-4. **runtime** — produce runtime characterization scenarios and evidence
-   references (`discovery-runtime-characterization`).
-5. **parity** — produce or refresh the parity matrix (`discovery-parity-matrix`).
-6. **reconciliation** — capture unspecified or contradictory behavior and
-   reconcile it into product decisions (`discovery-behavior-reconciliation`).
-7. **validation gate** — run the per-stage validators and the completion gate
-   (`discovery-validate-artifacts`).
-
-Compact form: profile -> inventory -> coverage -> runtime -> parity ->
-reconciliation -> validation gate.
-
-## Worker Routing
-
-The four generic agent roles are routed by slug from their owning stage skills.
-The routing table below is the canonical mapping; each stage skill repeats only
-the single slug it routes to.
-
-| Stage skill | Agent slug |
-|---|---|
-| `discovery-coverage-ledger` | `migration-coverage-reviewer` |
-| `discovery-runtime-characterization` | `runtime-characterization-analyst` |
-| `discovery-parity-matrix` | `legacy-parity-analyst` |
-| `discovery-behavior-reconciliation` | `requirements-reconciler` |
-
-## Referenced Contracts
-
-This registry is the single canonical location for upstream contract names.
-Stage skills name only the specific contract(s) they use and defer to this
-registry for the full set. Indirect reference by skill name is not duplication.
-
-### Domain profile (config contract, issue #360 / epic #9001)
-
-- Config artifact: `discovery-profile.yaml`.
-- CLI: `dev.discovery.profile`.
-
-### Schemas (issue #359 / epic #9002)
-
-Seven schemas under `schemas/discovery/v1/`:
-
-- `schemas/discovery/v1/feature-contract.schema.json`
-- `schemas/discovery/v1/coverage-ledger.schema.json`
-- `schemas/discovery/v1/runtime-characterization-scenario.schema.json`
-- `schemas/discovery/v1/parity-matrix.schema.json`
-- `schemas/discovery/v1/unspecified-behavior-record.schema.json`
-- `schemas/discovery/v1/product-decision-record.schema.json`
-- `schemas/discovery/v1/evidence-reference.schema.json`
-
-### Validators (issue #361 / epic #9003)
-
-Nine `dev.discovery.validate-*` console scripts. Each yields a `list[str]` of
-errors; an empty list is a pass.
-
-- `dev.discovery.validate-profile`
-- `dev.discovery.validate-feature-contract`
-- `dev.discovery.validate-coverage-ledger`
-- `dev.discovery.validate-runtime-scenario`
-- `dev.discovery.validate-parity-matrix`
-- `dev.discovery.validate-unspecified-behavior`
-- `dev.discovery.validate-product-decision`
-- `dev.discovery.validate-evidence-reference`
-- `dev.discovery.validate-all`
-
-### Analyzer framework (epic #9006, in preparation)
-
-- Language-neutral repository/project inventory command: `dev.discovery.inventory`.
-
-  **Fan-in reconciliation assumption:** the inventory command name
-  `dev.discovery.inventory` is assumed. It is not fixed by the prepared upstream
-  summaries and is the epic #9006 owner's decision. This assumption is isolated
-  to this single registry line plus one fragment in `discovery-repo-inventory`.
-  If #9006 lands a different command name, update those two locations only.
-
-### Agent roles (epic #9007, in preparation)
-
-Four generic agent personas, referenced by slug in the Worker Routing table
-above:
-
-- `legacy-parity-analyst`
-- `runtime-characterization-analyst`
-- `requirements-reconciler`
-- `migration-coverage-reviewer`
-
-  **Fan-in reconciliation assumption:** the four agent slugs are assumed to be
-  the kebab-case of the persona titles. Final slugs are the epic #9007 owner's
-  decision. The assumption is isolated to this registry and the per-stage
-  `## Worker Routing` fragments; reconciling a renamed slug at fan-in is a
-  bounded edit.
-
-## Referenced Skills
-
-- `discovery-repo-inventory` — inventory stage mechanics.
-- `discovery-coverage-ledger` — coverage stage mechanics.
-- `discovery-runtime-characterization` — runtime stage mechanics.
-- `discovery-parity-matrix` — parity stage mechanics.
-- `discovery-behavior-reconciliation` — reconciliation stage mechanics.
-- `discovery-validate-artifacts` — canonical validation-gate mechanics.
-
-## Notes
-
-- No skill in this workflow asserts the existence of upstream analyzer or agent
-  files; upstream contracts are referenced by name only, so this workflow stays
-  correct regardless of upstream merge order.
-- Domain specificity (source and target roots, technology stack, artifact
-  conventions) is read from the domain profile at runtime, never hard-coded.
+Use this compatibility name only to dispatch to its canonical workflow.
+
+## Inputs
+
+| Input | Required contract |
+| --- | --- |
+| skill_id | Required exact one of the nine canonical skill IDs listed below; unknown or missing values fail with no fallback. |
+
+Forward all other supplied canonical inputs to the selected target. These
+alias selectors are not service-request fields. A fixed mapping requires no
+additional selector; it does not add fields to `prepare-agent`.
+
+## Dispatch
+
+| Selector | Canonical skill |
+| --- | --- |
+| inventory-legacy-system | inventory-legacy-system |
+| extract-feature-contract | extract-feature-contract |
+| characterize-runtime-behavior | characterize-runtime-behavior |
+| reconcile-parity-matrix | reconcile-parity-matrix |
+| review-discovery-coverage | review-discovery-coverage |
+| adjudicate-unspecified-behavior | adjudicate-unspecified-behavior |
+| generate-acceptance-scenarios | generate-acceptance-scenarios |
+| initialize-discovery-workspace | initialize-discovery-workspace |
+| validate-discovery-artifacts | validate-discovery-artifacts |
+
+Select exactly one canonical workflow using `skill_id`. Forward its supplied inputs without inventing defaults or reinterpreting source identity. Each target owns its root prepare, exact launch, granted operations, finalize, native stop and root result; this umbrella adds no scheduler.
+
+This alias has no independent output or write authority. Do not duplicate
+business validation, call tools independently, create a receipt, change a model
+or auto-launch a role. Use only the linked canonical workflow's lifecycle and
+exact grants; no alias chain or filesystem fallback is permitted.
+
+## Stop and result
+
+Return the selected canonical workflow's explicit result and references without
+changing failed, blocked, pending or incremental outcomes into completion.
+An unknown selector fails with no fallback. Missing configuration or native
+capability is handled by the canonical workflow, including initialization's
+explicit root bootstrap exception. The alias cannot bypass prepare/finalize or
+native start/stop requirements.
+
+## References
+
+- [inventory-legacy-system](../inventory-legacy-system/SKILL.md)
+- [extract-feature-contract](../extract-feature-contract/SKILL.md)
+- [characterize-runtime-behavior](../characterize-runtime-behavior/SKILL.md)
+- [reconcile-parity-matrix](../reconcile-parity-matrix/SKILL.md)
+- [review-discovery-coverage](../review-discovery-coverage/SKILL.md)
+- [adjudicate-unspecified-behavior](../adjudicate-unspecified-behavior/SKILL.md)
+- [generate-acceptance-scenarios](../generate-acceptance-scenarios/SKILL.md)
+- [initialize-discovery-workspace](../initialize-discovery-workspace/SKILL.md)
+- [validate-discovery-artifacts](../validate-discovery-artifacts/SKILL.md)