docs: align README/CHANGELOG with real behavior; fix GitHub templates

Rewrite the docs to match what the code now does and drop the claims it never
backed: no more "lock-free" (the async path is a mutex-synchronized MPSC
queue), no "sub-microsecond / fastest" framing, and the benchmark section now
explains async's actual tradeoff (hot-path offload + losslessness, not higher
end-to-end throughput) with re-measured numbers and stated hardware. Document
the output format, the threading model, rotation, and flush(); fix the broken
Benchmarks anchor and the stderr-vs-stdout wording. Add a v0.2.0 changelog
entry and correct the build steps in CONTRIBUTING.

Fix the GitHub templates: issue forms now use a valid top-level description and
drop the unsupported "about:" key; the PR template moves from .yml (which GitHub
ignores) to Markdown. Extend .gitignore to cover benchmark artifacts and
locally-built test binaries.

Author: mbn-code

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,34 +1,37 @@
-name: Bug report
-about: Create a bug report to help us improve
-labels: bug
+name: Bug report
+description: Report a problem so we can fix it
+labels: [bug]
 body:
-  - type: input
+  - type: textarea
+    id: what-happened
     attributes:
       label: What happened?
-      description: Describe the bug in detail.
+      description: Describe the bug clearly.
     validations:
       required: true
-  - type: input
+  - type: textarea
+    id: repro
     attributes:
       label: Steps to reproduce
-      description: Include code, platform, and reproduction steps.
+      description: Include a minimal code sample, the compile/run command, and what you observed.
       placeholder: |
         1. Code sample
-        2. Compile/run this way
-        3. Observe...
+        2. Compile/run command
+        3. Observed vs. expected
     validations:
       required: true
   - type: input
+    id: expected
     attributes:
       label: Expected behavior
       description: What should have happened?
-      placeholder: Clear statement of correct behavior...
-      validations:
-        required: true
+    validations:
+      required: true
   - type: textarea
+    id: environment
     attributes:
-      label: System details
-      description: OS, compiler, and library versions
-      placeholder: Ubuntu 22.04, g++ v10, ...
+      label: Environment
+      description: OS, compiler and version, C++ standard, and cLog++ version/commit.
+      placeholder: "Ubuntu 22.04, g++ 12, -std=c++17, cLog++ @ <commit>"
     validations:
       required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,22 +1,25 @@
 name: Feature request
-about: Suggest an idea for cLog
-labels: enhancement
+description: Suggest an idea or improvement for cLog++
+labels: [enhancement]
 body:
-  - type: input
+  - type: textarea
+    id: feature
     attributes:
       label: What feature do you want?
       description: Be as specific as possible.
     validations:
       required: true
   - type: textarea
+    id: motivation
     attributes:
       label: Motivation
       description: Why is this needed? What problem does it solve?
-      validations:
-        required: false
+    validations:
+      required: false
   - type: textarea
+    id: solution
     attributes:
       label: Possible solution
-      description: Optional: sketch or describe how this could work.
-      validations:
-        required: false
+      description: Optional sketch of how this could work.
+    validations:
+      required: false

.github/pull_request_template.md

@@ -0,0 +1,10 @@
+## What changed?
+
+<!-- Describe the change and link any related issues, e.g. "Fixes #12". -->
+
+## Checklist
+
+- [ ] Builds and tests pass: `cmake -S . -B build && cmake --build build && ctest --test-dir build`
+- [ ] Added or updated tests for the change
+- [ ] Code is clear and commented where non-obvious
+- [ ] I license my contribution under the MIT license

.github/pull_request_template.yml

@@ -29,3 +29,12 @@ cmake-build*/
 .turd*
 __pycache__/
 .env
+
+# Benchmark artifacts
+benchmark_results.csv
+bench_cLogpp_file.txt
+
+# Locally-built binaries dropped next to sources (CMake builds go in build/).
+# Keep the sources; ignore everything else that lands in tests/.
+tests/*
+!tests/*.cpp

.gitignore

@@ -1,14 +1,41 @@
 # cLog++ Changelog
 
-## [v0.1.0] - 2026-02-10
+All notable changes are documented in this file.
+
+## [v0.2.0] - 2026-06-09
 ### Added
-- First public release: async by default, robust background log draining, JSON output.
-- File/console sink, chainable API for log creation.
-- Test suite for async flush, sync mode, file sink, and crash-avoidance.
-- Modern, minimal, single-header main implementation.
+- Timestamp (`ts`, ISO-8601 UTC) and `level` fields in every JSON line.
+- Native JSON typing for fields: integers, unsigned integers, `double`, and `bool`
+  are emitted unquoted (e.g. `{"n":42}`); `kv` gained overloads for these types and `const char*`.
+- `RotatingFileSink` (size-based rotation with a bounded number of backups).
+- `Logger::flush()` to block until everything submitted so far is written, plus a
+  `Sink::flush()` hook (default no-op) honored on flush and destruction.
+- `clear_sinks()` to drop the default console sink, and a configurable async queue
+  capacity via `Logger(Mode, capacity)`.
+- CMake build (`clogpp::clogpp` interface target), `ctest` integration, and CI on
+  Linux, macOS, and Windows.
+- Regression tests for level filtering, async losslessness, JSON field shape, and rotation.
 
 ### Fixed
-- Thread shutdown is now completely lossless. The background logging thread always fully drains before the logger is destroyed.
+- **Level filtering now works.** `set_level()` was previously never consulted, so all
+  levels were emitted regardless.
+- **Async logging is now lossless.** Earlier versions ignored the queue-full signal and
+  silently dropped entries under load (a tight loop could lose the large majority of its
+  logs), and the shutdown drain discarded entries. The queue now applies backpressure and
+  drains completely before the worker exits.
+- **Concurrent logging is now safe.** Per-entry state moved onto a per-statement
+  `LogRecord`, removing the shared mutable builder that races when multiple threads log
+  on one `Logger`.
+
+### Changed
+- `info()`/`error()`/etc. now return a `LogRecord` (which emits when it goes out of
+  scope) instead of `Logger&`. Existing chained usage — `log.info("e").kv("k", v);` —
+  is unchanged.
+- Documentation no longer describes the async path as "lock-free"; it is a
+  mutex-synchronized multi-producer queue. Benchmarks were re-measured end-to-end.
 
----
-All changes will be documented in this file.
+## [v0.1.0] - 2026-02-10
+### Added
+- First public release: async-by-default logger with background draining and JSON output.
+- File/console sinks and a chainable API.
+- Initial test suite and CI.

CHANGELOG.md

@@ -6,7 +6,13 @@ Thank you for your interest in contributing!
 1. **Fork the repository** and clone it locally.
 2. **Create a new branch** for each feature or fix.
 3. **Write clear code** and **add tests** for any new behavior.
-4. **Run all tests** (`g++ -std=c++17 -pthread -Iinclude tests/*.cpp && ./...`) before submitting.
+4. **Build and run the tests** before submitting:
+   ```bash
+   cmake -S . -B build
+   cmake --build build
+   ctest --test-dir build --output-on-failure
+   ```
+   To compile a single test directly: `g++ -std=c++17 -pthread -Iinclude tests/levels.cpp -o levels && ./levels`
 5. **Open a pull request** (PR) with a clear, descriptive title and summary.
 6. **Participate in code review. Please be responsive, constructive, and open!**