Verification and traceability

Platform spec article

Verification and traceability

Back to Template packages ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (3)

1. 0001-explicit-package-kind Explicit packageKind Accepted

   Explicit packageKind

   Context

   Registry taxonomy.

   Decision

   Explicit packageKind on beskid.package.v1.

   Consequences

   pckg validators.

   Verification anchors

   Validator tests.

   Open full ADR page

2. 0002-template-registry-ui-mode Template UI mode Accepted

   Template UI mode

   Context

   Registry taxonomy.

   Decision

   Template pages hide API docs.

   Consequences

   pckg validators.

   Verification anchors

   Validator tests.

   Open full ADR page

3. 0003-no-api-json-for-templates No api.json Accepted

   No api.json

   Context

   Registry taxonomy.

   Decision

   template kind must not require api.json.

   Consequences

   pckg validators.

   Verification anchors

   Validator tests.

   Open full ADR page

Articles

• Contracts and edge cases Publish-time and UI rules for template packages on pckg. article Standard Reviewed Thu May 21
• Design model `packageKind`, `.bpk` layout, and pckg registry presentation for template packages. article Standard Reviewed Thu May 21
• Verification and traceability Server and CLI tests for template package profile. article Standard Reviewed Thu May 21

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 10 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Template packages

  Parent feature hub

Purpose and scope

Traceability for pckg template profile implementation.

Tests

Test	Location (planned)
Template .bpk validates without api.json	pckg/src/Server.Tests/Unit/PackageArtifactValidatorTests.cs
Library .bpk still requires api.json when policy on	same
Template package page hides docs	Server.Tests integration or bUnit on package detail
Pack sets packageKind: template	beskid_tests pack golden package.json

Manual QA

1. Publish beskid.templates.console to test registry.
2. Open package page — confirm no API docs tab.
3. beskid new install beskid.templates.console — success.
4. Yank version — beskid new console prints warning.