AtomiCloud.Diene.StandardConfig.TestHelper 1.0.0

Diene .NET library template

Diene's reproducible development environment is managed by Nix. Run direnv allow once, then use pls tasks from the loaded shell.

This branch is the workspace baseline inherited by every downstream sample: split CI/CD, secrets, release configuration, validators, standards, and vendored agent-skill synchronization.

Commands

• pls setup — synchronize installed diene package skills.
• pls lint — run every pre-commit gate.
• pls secret:scan — scan tracked content for secrets.
• pls skills:sync — rebuild .claude/skills/vendor/ from installed packages.

Standards

• CI/CD workflows
• conventional commits
• Infisical and secrets
• linting and pre-commit
• Nix flakes and development shells
• release automation
• service-tree identity
• shell scripts
• Taskfile conventions

Shared standards

• Authorization
• Contributor documentation
• Date and time
• Domain-driven design
• Functional practices
• Software design philosophy
• SOLID principles
• Stateless OOP and dependency injection
• Testing
• Three-layer architecture
• Utility libraries
• Data validation

Domain-specific documentation belongs under docs/domain/. The docs/standards/contracts/ location is reserved for the separately owned C0 contracts standard.

.NET 10 foundation

This branch adds the .NET 10 toolchain, the App/Lib/UnitTest/IntTest/MetaTest sample, merged multi-project coverage, strict and LLM dead-code modes. See the .NET baseline.

Common commands:

• pls build, pls dev, pls run, and pls preview
• pls test, pls test:unit, pls test:int, pls test:meta, and the coverage variants
• pls deadcode for the non-blocking review; CI owns strict dn-inspect

The infra-preset domain is documented in docs/domain/standard-config.md. Production observability is intentionally absent until the observability add-back.

Publishable library packages

This repository publishes AtomiCloud.Diene.StandardConfig and the companion AtomiCloud.Diene.StandardConfig.TestHelper package at one committed version. It carries the four C0-frozen infra config presets — postgres, cache, kv, and storage — as typed, validated, schema-generating blocks, plus the small S3-compatible block-storage surface and Testcontainers glue for testing against the real dependencies. It ships schemas only: AtomiCloud.Diene.Config remains the sole merger and validator, and engine blocks belong to their engine libs.

dotnet add package AtomiCloud.Diene.StandardConfig
dotnet add package AtomiCloud.Diene.StandardConfig.TestHelper

using AtomiCloud.Diene.StandardConfig.Presets;

builder.Services.AddStandardConfigs(
    StandardConfigPreset.Postgres | StandardConfigPreset.Cache | StandardConfigPreset.Storage);

// later, wherever the connection is needed
var main = postgres.Value.Named("MAIN");   // IOptions<PostgresBlock>

using AtomiCloud.Diene.StandardConfig.TestHelper.Containers;

await using var db = await StandardConfigContainers.StartPostgresAsync();
var configuration = new ConfigurationBuilder()
    .AddInMemoryCollection(db.ConfigurationValues(PostgresOption.Key))
    .Build();

Adding a second named connection is a YAML edit — every preset is a keyed map of UPPERCASE-named connections (R14), so REPLICA alongside MAIN needs no code.

Run nix develop .#ci -c ./scripts/ci/pkg-validate.sh to pack both packages, validate metadata and symbols, and restore them into a scratch consumer. See the library baseline for release and promotion guidance.