stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

chore(docs+devops): cross-module doc sync + sprint archival moves + compose updates

Browse Source 
Bundled pre-session doc + ops work:
- docs/modules/**: sync across advisory-ai, airgap, cli, excititor,
  export-center, findings-ledger, notifier, notify, platform, router,
  sbom-service, ui, web (architectural + operational updates)
- docs/features/**: updates to checked excititor vex pipeline,
  developer workspace, quick verify drawer
- docs top-level: README, quickstart, API_CLI_REFERENCE, UI_GUIDE,
  code-of-conduct/TESTING_PRACTICES updates
- docs/qa/feature-checks/: FLOW.md + excititor state update
- docs/implplan/: remaining sprint updates + new Concelier source
  credentials sprint (SPRINT_20260422_003)
- docs-archived/implplan/: 30 sprint archival moves (ElkSharp series,
  misc completed sprints)
- devops/compose: .env + services compose + env example + router gateway
  config updates

File-level granularity preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
master
2026-04-22 16:06:39 +03:00
parent ad77711ac2
commit 7943cfb3af
121 changed files with 10483 additions and 387 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/code-of-conduct/TESTING_PRACTICES.md
View File

@@ -32,7 +32,11 @@
- Some Stella Ops test projects expose the xUnit v3 in-process runner through Microsoft Testing Platform.
- On those projects, `dotnet test --filter ...` may be ignored even when the caller expects a narrow subset.
- For targeted verification on those projects, use `pwsh ./scripts/test-targeted-xunit.ps1 -Project <test-project>.csproj ...` or execute the produced test DLL directly with `dotnet exec`.
- For targeted verification on those projects, use `pwsh ./scripts/test-targeted-xunit.ps1 -Project <test-project>.csproj ...` when PowerShell 7 is available, or `powershell -ExecutionPolicy Bypass -File .\scripts\test-targeted-xunit.ps1 -Project <test-project>.csproj ...` on Windows PowerShell hosts.
- The helper auto-selects the correct runner:
- `dotnet exec <test-dll>` for standard library-style test assemblies
- `dotnet run --project <test-project> -- ...` for ASP.NET host tests that reference `Microsoft.AspNetCore.Mvc.Testing`
- Do not force raw `dotnet exec` for MVC-testing projects; that can fail with loader-context false negatives even when the targeted test actually passes through the normal project runner.
- Capture the exact targeted method/class/trait arguments in sprint evidence so reviewers can confirm the run was actually scoped.
- If the test assembly is stale, rebuild the specific `.csproj` first; prefer a scoped build over a solution-wide rebuild.