Prepare for v0.1 release

Author: codewithkyle

.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  build-and-test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Build
+        run: make clean && make all
+
+      - name: Test
+        run: make test

CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+## [0.1.0] - 2026-05-18
+
+Initial public release of `psa-parser`.
+
+- Provides a C parser library for PSA planogram files with streaming callbacks.
+- Includes JSON helper APIs and document-oriented parse helpers.
+- Ships a CLI supporting document output, NDJSON streaming, and summary mode.
+- Includes test coverage for numeric parsing, preprocessing, JSON encoding, and sample parsing.
+- Adds integration guidance for foreign-language bindings via `docs/bindings.md`.

README.md

@@ -22,7 +22,7 @@ No external runtime dependencies are required for the parser library or CLI.
 - `src/`: parser, record mapping, JSON helpers
 - `cli/main.c`: command-line interface
 - `tests/`: unit and synthetic integration tests
-- `spec/`: file format and record mapping specification
+- `docs/spec/`: file format and record mapping specification
 
 ## Development Commands
 
@@ -95,3 +95,10 @@ Help:
   - `psa_parse_buffer_to_json_document(...)` (same contract for in-memory PSA content)
 
 See `include/psa.h` for full API details and record structures.
+
+## Versioning and Compatibility
+
+- Current release target: `v0.1.0`.
+- API/ABI compatibility for `0.x` releases is best effort and may evolve based on implementation feedback.
+- Error code semantics (`PSA_OK`, `PSA_ERR_*`) are intended to remain stable across minor releases.
+- Production consumers should pin to a specific tag or commit.

docs/bindings.md

@@ -112,3 +112,5 @@ If your application wants display-specific normalization (for example, convertin
 - Keep your binding layer thin and faithful to C behavior.
 - Perform optional transformations in a separate higher-level layer.
 - Pin against a specific library version/commit in production.
+
+For `0.x` releases, API/ABI stability is best effort while the library matures.