Add initial Code311 multi-package solution, Tabler foundations, host demo, licensing, EF Core persistence, and CI

[Code-311]

Motivation

• Establish a Phase‑0 repository baseline with a multi-project solution, centralized build and package governance, and a demo host to exercise package integrations.
• Provide framework‑neutral UI abstraction contracts and a Tabler-backed implementation surface (core, components, dashboard, widgets) so downstream adapters and hosts can be composed consistently.
• Add basic cross-cutting infrastructure (licensing runtime, provider‑agnostic EF Core persistence for user preferences), architecture docs, and a CI pipeline to enforce build/test quality gates.

Description

• Introduce solution and repo-level build configuration: Code311.sln, global.json, Directory.Build.props, Directory.Build.targets, and Directory.Packages.props to pin SDK, enable analyzers/nullable/XML docs, and centralize package versions.
• Add foundation packages and implementations under src/: Code311.Ui.Abstractions, Code311.Ui.Core, Code311.Tabler.Core, Code311.Tabler.Components, Code311.Tabler.Dashboard, widget packages (DataTables, Calendar, Charts), Code311.Tabler.Mvc, Code311.Tabler.Razor, Code311.Persistence.EFCore, Code311.Licensing, and a hybrid demo host Code311.Host with controllers, pages, views, and DI wiring in Program.cs.
• Implement Tabler mapping and asset contracts, TagHelpers/ViewComponents for a representative component set (forms, layout, feedback, data, media, navigation), widget slot contracts and widget implementations, EF Core preference entity/store and model mapping, plus a small licensing runtime (sources, validation, feature gate, diagnostics) and DI helpers.
• Add documentation and governance artifacts: README.md, ADRs under docs/adr/, and an architecture proposal; set up a GitHub Actions CI workflow (.github/workflows/ci.yml) that restores, builds, and runs tests using the pinned .NET SDK.
• Add comprehensive test projects under tests/ that exercise abstractions, core orchestration, Tabler core/components/dashboard/widgets, persistence, licensing, and integration points for MVC/Razor adapters.

Testing

• CI workflow added at .github/workflows/ci.yml runs dotnet restore Code311.sln, dotnet build Code311.sln --configuration Release --no-restore, and dotnet test Code311.sln --configuration Release --no-build --verbosity normal to validate the solution.
• Executed the solution test matrix via dotnet test Code311.sln, covering unit and integration suites in tests/* (examples: Code311.Tests.Tabler.Core, Code311.Tests.Tabler.Components, Code311.Tests.Licensing, Code311.Tests.Persistence.EFCore, Code311.Tests.Integration.Mvc, Code311.Tests.Integration.Razor), and all automated tests completed successfully in the validation run.
• Local verification included dotnet build and representative unit tests for mapping, widget slot initialization, EF Core preference store round‑trip, and licensing behavior, which passed in the run described above.

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.