release: publish v0.1.0 artifacts

Author: markhazleton

.documentation/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to ReactSparkPortfolio will be documented in this file.
+All notable changes to BootstrapSpark will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
@@ -9,18 +9,30 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- Tag-driven GitHub Release automation that packages the built site together with DevSpark release docs
-- World-class README.md with comprehensive documentation
-- Complete documentation suite in `/documentation` folder
-- Contributing guidelines and project governance
-- Architecture documentation with diagrams
-- Comprehensive deployment guide for multiple platforms
+### Changed
+
+## [0.1.0] - 2026-04-16
+
+### Added
+
+- **BootstrapSpark consolidation** - Merged the JsBootSpark feature surface into the React-based BootstrapSpark application and standardized the project identity.
+- **Robust theme switcher** - Expanded theming toward a richer Bootswatch-backed selector model with local catalog ownership and fallback behavior.
+- **Release automation path** - Added tag-driven GitHub Release packaging that ships generated release notes with a built site bundle.
 
 ### Changed
 
-- `/devspark.release` now relies on the upgraded release context contract in `.documentation/scripts/powershell/release-context.ps1`
-- Improved project organization with centralized documentation
-- Enhanced copilot instructions for better AI assistance
+- **Build artifact handling** - Stopped treating generated deploy output and coverage reports as source-controlled artifacts, leaving CI responsible for production builds.
+- **Release workflow** - `/devspark.release` now relies on the upgraded release context contract in `.documentation/scripts/powershell/release-context.ps1`.
+
+### Architectural Decisions
+
+- **ADR-001**: Build artifacts are generated in CI, not stored in git.
+- **ADR-002**: Consolidate BootstrapSpark as a single React SPA.
+- **ADR-003**: Use a local theme catalog and precompiled theme assets.
+
+### Contributors
+
+- Mark Hazleton
 
 ## [2.0.0] - 2025-01-05
 

.documentation/Guide.md

@@ -17,13 +17,13 @@ This is the living orientation document for `.documentation/`. It reflects the *
 ├── DEPLOYMENT.md                   ← Deployment guide (Azure Static Web Apps, GitHub Pages)
 ├── PROMPTSPARK_CHAT.md             ← PromptSpark real-time chat feature documentation
 ├── SECURITY.md                     ← CSP policy, security headers, allowlist rationale
-├── commands/                       ← Team-customized DevSpark command overrides
-├── copilot/                        ← AI-session working documents (currently empty)
 ├── decisions/                      ← Architecture Decision Records (ADRs)
 ├── memory/
 │   └── constitution.md             ← Project constitution (non-negotiable principles)
+├── releases/                       ← Versioned release archives generated by /devspark.release
+├── repo-story/                     ← Repository history and narrative outputs
 ├── scripts/                        ← Team script overrides for DevSpark
-├── specs/                          ← Active feature specifications (archive after merge)
+├── specs/                          ← Active feature specifications and pr-review records
 └── templates/                      ← DevSpark document templates (operational, do not archive)
 ```
 
@@ -39,7 +39,7 @@ This is the living orientation document for `.documentation/`. It reflects the *
 | `CACHE_BUSTING.md` | Cache invalidation strategy: build-date-based in prod, timestamp-based in dev |
 | `CHANGELOG.md` | Release history following Keep a Changelog / SemVer |
 | `CONTRIBUTING.md` | How to contribute, testing strategy, PR requirements |
-| `DEPLOYMENT.md` | Dual-target deployment: Azure Static Web Apps + GitHub Pages via `/docs` |
+| `DEPLOYMENT.md` | Deployment and release guide for Azure Static Web Apps and tag-driven GitHub Releases |
 | `SECURITY.md` | CSP policy, justified allowlist, intentional permissiveness rationale |
 | `PROMPTSPARK_CHAT.md` | SignalR-based real-time chat with AI personalities |
 
@@ -75,6 +75,6 @@ When that release commit is tagged and the tag is pushed, `.github/workflows/git
 
 ---
 
-## What Is in `.archive/`
+## Release Archives
 
-Completed and historical docs moved here by archive runs. **Do not read from here during normal operations.** Files are preserved for audit and traceability only. See `.archive/README.md` for the index of archive batches.
+Versioned release artifacts live under `.documentation/releases/vX.Y.Z/`. Each release folder contains release notes, metrics, and archived feature specs for that release cut.

.documentation/decisions/ADR-001-build-artifacts-in-ci.md

@@ -0,0 +1,30 @@
+# ADR-001: Build Artifacts Are Generated in CI, Not Stored in Git
+
+## Status
+
+Accepted
+
+## Context
+
+BootstrapSpark builds to `docs/`, producing hashed filenames on every production build. Keeping `docs/` and coverage reports under git tracking created persistent diff noise that obscured meaningful source changes. The Azure Static Web Apps workflow already builds from source during CI, so committed build output was redundant.
+
+## Decision
+
+Treat `docs/` and `coverage/` as build artifacts only. They are generated locally or in CI when needed, ignored by git, and no longer treated as source-controlled release content.
+
+## Consequences
+
+### Positive
+
+- Git history and pull requests stay focused on source changes.
+- CI remains the source of truth for production build output.
+
+### Negative
+
+- Contributors must run a build locally before previewing production output.
+
+## Source
+
+- **Spec**: 001-build-artifact-separation
+- **Release**: v0.1.0
+- **Date**: 2026-04-16

.documentation/decisions/ADR-002-bootstrapspark-react-consolidation.md

@@ -0,0 +1,30 @@
+# ADR-002: Consolidate BootstrapSpark as a Single React SPA
+
+## Status
+
+Accepted
+
+## Context
+
+Two separate Bootstrap-focused showcase repositories overlapped in purpose: one built with React/Vite/TypeScript and one built with vanilla JavaScript, Express, and EJS. Maintaining both created duplicate effort, fragmented feature discovery, and weakened the consistency of the Spark portfolio family.
+
+## Decision
+
+Consolidate the unique JsBootSpark features into the React-based application and standardize the project identity as BootstrapSpark. The merged application keeps a single frontend architecture built on React, Vite, TypeScript, Bootstrap, and a service/model/component structure.
+
+## Consequences
+
+### Positive
+
+- One repository now owns the Bootstrap showcase experience.
+- Feature growth stays aligned with the existing TypeScript and React architecture.
+
+### Negative
+
+- The consolidated app inherits a larger routing and component surface that requires stronger regression testing.
+
+## Source
+
+- **Spec**: 001-merge-jsbootspark
+- **Release**: v0.1.0
+- **Date**: 2026-04-16

.documentation/decisions/ADR-003-local-theme-catalog-and-precompiled-assets.md

@@ -0,0 +1,30 @@
+# ADR-003: Use a Local Theme Catalog and Precompiled Theme Assets
+
+## Status
+
+Accepted
+
+## Context
+
+BootstrapSpark needed a robust theme-switching experience that supports the BootstrapSpark default theme plus the Bootswatch catalog while remaining usable when external metadata is unavailable. A runtime dependency on live external theme data would reduce resilience and complicate CSP and fallback behavior.
+
+## Decision
+
+Use a locally maintained supported-theme catalog as the source of truth and apply curated themes by swapping precompiled static stylesheet assets. External Bootswatch metadata may enrich the catalog, but runtime correctness must not depend on it.
+
+## Consequences
+
+### Positive
+
+- Theme selection remains reliable even when external metadata is unavailable.
+- Theme switching stays simple and fast because assets are precompiled.
+
+### Negative
+
+- The local catalog and static assets must be maintained as Bootswatch evolves.
+
+## Source
+
+- **Spec**: 001-robust-theme-switcher
+- **Release**: v0.1.0
+- **Date**: 2026-04-16

.documentation/releases/v0.1.0/metrics.json

@@ -0,0 +1,31 @@
+{
+  "version": "0.1.0",
+  "releaseDate": "2026-04-16",
+  "release": {
+    "from": "project-start",
+    "to": "2026-04-16"
+  },
+  "previousVersion": "",
+  "features": {
+    "completed": 3,
+    "deferred": 0
+  },
+  "quickfixes": 0,
+  "pullRequests": {
+    "merged": 7,
+    "numbers": [16, 29, 38, 39, 40, 41, 42],
+    "filesChanged": 0,
+    "testsAdded": 0,
+    "breakingChanges": 0,
+    "resolvedHighFindings": 0
+  },
+  "adrs": 3,
+  "commits": 152,
+  "contributors": 1,
+  "specs": [
+    "001-build-artifact-separation",
+    "001-merge-jsbootspark",
+    "001-robust-theme-switcher"
+  ],
+  "timestamp": "2026-04-16T00:00:00Z"
+}

.documentation/releases/v0.1.0/release-notes.md

@@ -0,0 +1,83 @@
+# Release Notes: v0.1.0
+
+## Release Metadata
+
+- **Version**: v0.1.0
+- **Release Date**: 2026-04-16
+- **Release Window**: project start → 2026-04-16
+- **Previous Version**: none
+- **Commits**: 152
+- **Contributors**: 1
+- **Merged PRs**: 7
+
+## Highlights
+
+BootstrapSpark v0.1.0 establishes the first formal release artifact set for the consolidated project. This release turns a set of completed feature specs into a documented, archiveable release with versioned notes, ADRs, and a reproducible GitHub release packaging path.
+
+Functionally, the release captures three meaningful product and engineering milestones: the repo was consolidated and renamed to BootstrapSpark, the theme system was expanded into a richer Bootswatch-backed selector model, and the build/deployment workflow was cleaned up so generated output stops polluting normal source-control review.
+
+## New Features
+
+### Merge JsBootSpark Into BootstrapSpark
+
+BootstrapSpark now acts as the single React-based Bootstrap showcase application, absorbing the distinct JsBootSpark feature surface into a unified SPA architecture and branding model.
+
+**Spec**: [View archived spec](specs/001-merge-jsbootspark/spec.md)
+
+### Robust Theme Switcher
+
+The theming system evolved from a light/dark toggle into a resilient theme-selection experience centered on a BootstrapSpark default theme plus Bootswatch-backed options, local catalog ownership, and explicit fallback behavior.
+
+**Spec**: [View archived spec](specs/001-robust-theme-switcher/spec.md)
+
+### Build Artifact Separation
+
+Build output and coverage reporting were formally separated from committed source so CI remains responsible for generated deployable output and local builds stop flooding git history with hashed asset churn.
+
+**Spec**: [View archived spec](specs/001-build-artifact-separation/spec.md)
+
+## Bug Fixes
+
+No standalone quickfix records were included in this release.
+
+## Breaking Changes
+
+No breaking runtime changes were documented for this release.
+
+## Deprecations
+
+No deprecations were recorded for this release.
+
+## Architectural Decisions
+
+- **ADR-001**: Build artifacts are generated in CI, not stored in git - [View](../../decisions/ADR-001-build-artifacts-in-ci.md)
+- **ADR-002**: Consolidate BootstrapSpark as a single React SPA - [View](../../decisions/ADR-002-bootstrapspark-react-consolidation.md)
+- **ADR-003**: Use a local theme catalog and precompiled theme assets - [View](../../decisions/ADR-003-local-theme-catalog-and-precompiled-assets.md)
+
+## Deferred Features
+
+No active specs were deferred from this release window.
+
+## Upgrade Guide
+
+1. Pull the release commit and install dependencies as usual.
+2. Run `npm run build` before local production preview workflows that rely on generated `docs/` output.
+3. Push the matching git tag `v0.1.0` after the release commit if you want GitHub to publish the packaged release assets.
+
+## Metrics
+
+| Metric | Value |
+|--------|-------|
+| Features Delivered | 3 |
+| Bugs Fixed | 0 |
+| PRs Merged | 7 |
+| Files Changed | 0 |
+| Tests Added | 0 |
+| Breaking Changes | 0 |
+| ADRs Created | 3 |
+| Contributors | 1 |
+| Commits | 152 |
+
+---
+
+_Release documentation generated by /devspark.release v2.0.0_

…cs/001-build-artifact-separation/plan.md …cs/001-build-artifact-separation/plan.md.documentation/specs/001-build-artifact-separation/plan.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/plan.md .documentation/specs/001-build-artifact-separation/plan.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/plan.md

@@ -161,4 +161,4 @@ All gates pass. Ready for `/devspark.tasks`.
 
 ## Complexity Tracking
 
-No constitution violations. Table not needed.
+No constitution violations. Table not needed.

…01-build-artifact-separation/research.md …01-build-artifact-separation/research.md.documentation/specs/001-build-artifact-separation/research.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/research.md .documentation/specs/001-build-artifact-separation/research.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/research.md

@@ -27,4 +27,4 @@
 
 **Decision**: Leave as-is (no action in this feature).
 **Rationale**: This plugin writes `docs/.nojekyll` for GitHub Pages compatibility. The project now uses Azure SWA, so it's unnecessary but harmless. Removing it is a separate cleanup concern.
-**Alternatives considered**: Remove the plugin — deferred to avoid scope creep.
+**Alternatives considered**: Remove the plugin — deferred to avoid scope creep.

…cs/001-build-artifact-separation/spec.md …cs/001-build-artifact-separation/spec.md.documentation/specs/001-build-artifact-separation/spec.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/spec.md .documentation/specs/001-build-artifact-separation/spec.md renamed to .documentation/releases/v0.1.0/specs/001-build-artifact-separation/spec.md

@@ -101,4 +101,4 @@ This change will establish a clean boundary: **source files are committed, build
 - **SC-001**: [Measurable metric, e.g., "Users can complete account creation in under 2 minutes"]
 - **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
 - **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
-- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]
+- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]