docs(changelog): backfill missing unreleased entries

- Add `[UnReleased]` entries for #201 (inner_order_property flag, _StrictProperty export) and #200 (circular chain RuntimeError, _StrictProperty module path fix)
- Add CHANGELOG update rule to AGENTS.md `Always:` block: write entry at PR-creation time with `(#N)` link; skip docs/tests/CI/refactoring
- Add matching checklist item to CONTRIBUTING.md "Before Opening a PR"

---
Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>

Author: Borda

.github/CONTRIBUTING.md

@@ -131,6 +131,7 @@ Complete this checklist before opening a pull request to ensure quality and smoo
 - [ ] Added tests for new functionality (happy path, failure path, edge cases)
 - [ ] Ran tests locally and they pass (`pytest .`)
 - [ ] Updated documentation if needed (README, docs/guide pages, docstrings, inline comments)
+- [ ] Updated `CHANGELOG.md` under `[UnReleased]` — write the entry **at PR-creation time** (once the PR number is known and content is stable); re-assess against the final diff, not individual commits; include `(#N)` PR link; exclude docs-only, test-only, CI, and internal refactoring changes
 - [ ] Updated `docs/llms.txt` if public API behavior, patterns, or anti-patterns changed
 - [ ] Self-reviewed my code
 - [ ] Linked to related issue(s)

AGENTS.md

@@ -118,6 +118,8 @@ Write a clear explanation linking to both sources, then let maintainers decide o
 
 - **Keep README and docs site in sync** — any API addition, rename, or behavior change must be reflected in `README.md` **and** the relevant `docs/guide/` page; new troubleshooting items go in `docs/troubleshooting.md` **and** the FAQPage JSON-LD in `docs/overrides/main.html`
 
+- **Update `CHANGELOG.md` at PR-creation time** — once the PR number is known and the diff is stable, add or re-assess the entry under `[UnReleased]` (new features → `Added`, fixes → `Fixed`, behavior changes → `Changed`); always include `(#N)` PR link; skip docs-only, test-only, CI, and pure internal refactoring changes; do not write entries during iterative development commits — content may pivot before the PR is opened
+
 - **Update inline comments when changing behavior** — after any logic change, scan changed files for comments describing that behavior; update stale ones (stale comments mislead more than none)
 
 - **Keep AI-agent documentation in sync** — `docs/llms.txt` is a machine-readable contract read by AI agents before generating code; it must reflect actual behavior at all times. Apply this sync table on every relevant change:

CHANGELOG.md

@@ -4,6 +4,10 @@
 
 ### Added
 
+- **`DeprecationWrapperInfo.inner_order_property` flag.** `find_deprecation_wrappers()` now sets `inner_order_property=True` when a plain `property` (not `_DeprecatedProperty`) has a `@deprecated`-wrapped `fget` — the inner-order `@property @deprecated` shape where only the getter warns; setters and deleters added via `@value.setter` / `@value.deleter` remain silently unprotected. CI pipelines can filter on this field to reject the pattern. ([#201](https://github.com/Borda/pyDeprecate/pull/201))
+
+- **Opt-in strict `property` replacement.** `from deprecate import property` now exports `_StrictProperty`, a `property` subclass that raises `TypeError` at class-definition time when handed an already-`@deprecated` getter (inner-order detection). Import it in modules that want compile-time enforcement; star imports (`from deprecate import *`) are unaffected. ([#201](https://github.com/Borda/pyDeprecate/pull/201))
+
 ### Changed
 
 ### Deprecated
@@ -12,6 +16,10 @@
 
 ### Fixed
 
+- **Circular deprecation chains now raise `RuntimeError` at call time.** Callable `target` chains that form a cycle (A → B → A) previously caused unbounded recursion and a `RecursionError`. The decorator now detects the cycle via a `ContextVar` re-entrancy guard and raises a clear `RuntimeError` naming the circular path. Async deprecation cycle detection was also improved to avoid false positives from concurrent tasks sharing a threading-local guard. ([#200](https://github.com/Borda/pyDeprecate/pull/200))
+
+- **`_StrictProperty` `TypeError` message now references the correct module path.** The error previously pointed to `deprecate._StrictProperty`; corrected to `deprecate.deprecation._StrictProperty`, which is the actual import path.
+
 ______________________________________________________________________
 
 ## [0.10.0] — 2026-06-21 — Property accessors, class attribute mapping & descriptor targets