docs: update documentation for plan modifier fix and remove obsolete fgam_serialization

Updates documentation to reflect the plan modifier fix that resolves "Provider produced
inconsistent result after apply" errors introduced with FGAM field additions in v0.4.0.

Changes:
- CHANGELOG.md: Add v0.5.0 entry documenting plan modifier fix, mark v0.4.1 as [YANKED]
- docs/guides/troubleshooting.md: Add section for "Provider produced inconsistent result" error with upgrade instructions
- docs/index.md: Remove obsolete fgam_serialization provider

Author: Verolop

CHANGELOG.md

@@ -7,11 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.4.1] - 2025-01-08
+### Fixed
+- Resolved plan modifier inconsistencies introduced with FGAM field additions in v0.4.0
+- Fixed "Provider produced inconsistent result after apply" errors by correctly configuring UseStateForUnknown() plan modifiers for immutable vs mutable computed fields
+- Immutable fields (id, created_at, creator) now use UseStateForUnknown() to prevent "(known after apply)" noise
+- Mutable FGAM fields (updated_at, updater) correctly omit UseStateForUnknown() to display actual API values
+
+## [0.4.1] - 2025-01-08 [YANKED]
 
 ### Fixed
 - Ensures consistent behavior across all resources and eliminates plan inconsistencies for policy updates
 
+**Note:** This version has been yanked due to incomplete plan modifier configuration. Use v0.5.0+ instead.
+
 ## [0.4.0] - 2025-01-08
 
 ### Added

docs/guides/troubleshooting.md

@@ -111,6 +111,24 @@ provider "authzed" {
 }
 ```
 
+## Resource Management Issues
+
+### "Provider produced inconsistent result after apply"
+
+If you encounter errors like:
+
+```
+Error: Provider produced inconsistent result after apply
+
+When applying changes to authzed_policy.example, provider 
+"registry.terraform.io/authzed/authzed" produced an unexpected new value: 
+.created_at: was "2025-01-08T10:00:00Z", but now cty.StringVal("").
+```
+
+**Root Cause:**
+This error was caused by incorrect plan modifier configuration for computed fields in provider versions prior to v0.5.0.
+
+
 ## Getting Help
 
 If you continue to experience issues:

docs/index.md

@@ -28,8 +28,7 @@ provider "authzed" {
   # Uncomment to specify a different API version
   # api_version = "25r1"
   
-  # Uncomment to enable serialization for high-concurrency scenarios
-  # fgam_serialization = true
+
 }
 ```
 
@@ -49,7 +48,7 @@ To obtain a token, contact your AuthZed account team. They will provide you with
 * `endpoint` - (Required) The host address of the AuthZed Cloud API. Default is `https://api.admin.stage.aws.authzed.net`.
 * `token` - (Required) The bearer token for authentication with AuthZed.
 * `api_version` - (Optional) The version of the API to use. Default is "25r1".
-* `fgam_serialization` - (Optional) Enable serialization of operations to prevent conflicts. When enabled, resources within the same permission system will be created/updated sequentially instead of in parallel. Default is `false`.
+
 
 ## Important Notes