bQUARKz
46bd0c42d3
All checks were successful
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
JaCoCo Coverage #### Project Overview
No changes detected, that affect the code coverage.
* Line Coverage: 61.95% (17766/28676)
* Branch Coverage: 52.69% (6860/13019)
* Lines of Code: 28676
* Cyclomatic Complexity: 11490
#### Quality Gates Summary
Output truncated.
Test / Build skipped: 15, passed: 643
Intrepid/Prometeu/Studio/pipeline/pr-master This commit looks good
Move lifecycle assembly out of the PBS frontend into a common AssembleLifecyclePipelineStage. PBS emits a typed IRLifecycleDeclaration; the assembler owns wrappers, boot guard, and single project-init execution. Housekeep DSC-0059 with LSN-0062, and include the DSC-0062 PVM/PBX neutrality spec and lesson already present on this branch.
PBS Specs
This directory contains the normative PBS specification set.
Purpose
Specs define the official PBS language/frontend contract.
They exist to make behavior, constraints, and interfaces stable across implementations and reviews.
Cross-language acceptance rules are not defined here.
Those are maintained in docs/general/specs.
Expected Format
The exact structure may vary by document, but a spec should usually contain:
- Title
- Status
- Scope or Applies To
- Purpose
- Authority and Precedence
- Normative Inputs
- Core Rules
- Non-Goals
- Exit Criteria
Some specs may also include:
- already-settled inputs,
- initial section targets,
TODOsections for tracked unresolved items,- cross-references to adjacent specs.
Writing Rules
- Write in normative language.
- Integrate only decisions that have already been closed.
- Keep debate history and exploratory alternatives out of the spec body.
- Preserve clear boundaries between adjacent specs.
- Use
TODOonly for explicitly tracked unresolved items, not as a substitute for agenda work.
Upstream Rule
Specs should normally be fed by:
- agendas that frame the open topic,
- decisions that close the architectural question,
- then spec integration.
If a spec edit would require guessing an unresolved design choice, the correct action is to stop and surface the missing decision first.
Current Chapter Focus
The active PBS chapter focus is:
11. AST Specification.md12. Diagnostics Specification.md13. Lowering IRBackend Specification.md
Frontend-Owned Semantic Presentation Rule
PBS, as a frontend, owns its semantic vocabulary and semantic editor presentation contract.
That means:
- PBS semantic keys are PBS-owned contract data,
- PBS semantic highlight resources belong to PBS rather than to Studio or LSP,
- PBS publishes that contract through
FrontendSpec, - and Studio/LSP consume that contract without becoming owners of PBS semantic presentation assets.