TenantAtlas/apps/platform/tests/Feature/ReasonTranslation/ReasonTranslationExplanationTest.php
ahmido ad16eee591 Spec 204: harden platform core vocabulary (#234)
## Summary
- add the Spec 204 platform vocabulary foundation, including canonical glossary terms, registry ownership descriptors, canonical operation type and alias resolution, and explicit reason ownership and platform reason-family metadata
- harden platform-facing compare, snapshot, evidence, monitoring, review, and reporting surfaces so they prefer governed-subject and canonical operation semantics while preserving intentional Intune-owned terminology
- extend Spec 204 unit, feature, Filament, and architecture coverage and add the full spec artifacts, checklist, and completed task ledger

## Verification
- ran the focused recent-change Sail verification pack for the new glossary and reason-semantics work
- ran the full Spec 204 quickstart verification pack under Sail
- ran `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent`
- ran an integrated-browser smoke pass covering tenant dashboard, operations, operation detail, baseline compare, evidence, reviews, review packs, provider connections, inventory items, backup schedules, onboarding, and the system dashboard/operations/failures/run-detail surfaces

## Notes
- provider registration is unchanged and remains in `bootstrap/providers.php`
- no new destructive actions or asset-registration changes are introduced by this branch

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #234
2026-04-14 06:09:42 +00:00

56 lines
2.1 KiB
PHP

<?php
declare(strict_types=1);
use App\Support\Baselines\BaselineCompareReasonCode;
use App\Support\Baselines\BaselineReasonCodes;
use App\Support\Governance\PlatformVocabularyGlossary;
use App\Support\ReasonTranslation\ReasonPresenter;
use App\Support\Ui\OperatorExplanation\TrustworthinessLevel;
it('exposes trust-impact and absence-pattern semantics for governance reasons', function (
string $reasonCode,
string $expectedTrustImpact,
?string $expectedAbsencePattern,
): void {
$envelope = app(ReasonPresenter::class)->forArtifactTruth($reasonCode, 'artifact_truth');
expect($envelope)->not->toBeNull()
->and($envelope?->trustImpact)->toBe($expectedTrustImpact)
->and($envelope?->absencePattern)->toBe($expectedAbsencePattern)
->and(app(ReasonPresenter::class)->dominantCauseExplanation($envelope))->not->toBe('');
})->with([
'trustworthy no-drift compare result' => [
BaselineCompareReasonCode::NoDriftDetected->value,
TrustworthinessLevel::Trustworthy->value,
'true_no_result',
],
'suppressed compare result' => [
BaselineCompareReasonCode::CoverageUnproven->value,
TrustworthinessLevel::LimitedConfidence->value,
'suppressed_output',
],
'missing baseline input' => [
BaselineReasonCodes::SNAPSHOT_CAPTURE_FAILED,
TrustworthinessLevel::LimitedConfidence->value,
'unavailable',
],
'fallback review blocker' => [
'review_missing_sections',
TrustworthinessLevel::Unusable->value,
'missing_input',
],
]);
it('keeps governance reason ownership and family semantics explicit', function (): void {
$presenter = app(ReasonPresenter::class);
$semantics = $presenter->semantics(
$presenter->forArtifactTruth(BaselineCompareReasonCode::CoverageUnproven->value, 'artifact_truth'),
);
expect($semantics)->not->toBeNull()
->and($semantics['owner_label'] ?? null)->toBe('Governance detail')
->and($semantics['family_label'] ?? null)->toBe('Coverage')
->and($semantics['boundary_classification'] ?? null)->toBe(PlatformVocabularyGlossary::BOUNDARY_CROSS_DOMAIN_GOVERNANCE);
});