update md files, update icon

Author: danielklecha

AGENTS.md

@@ -1,68 +1,37 @@
 # Agent Integration Notes for SharpIpp
 
-This file is the human-readable integration guide for AI/code agents working in this repository.
-It summarizes verified specification coverage, highlights known parity gaps, and defines a safe workflow
-for implementing missing IPP/PWG features.
+This file provides architectural pointers and development workflows for AI and code agents working in this repository.
 
-## Scope and source of truth
+## Documentation & Specifications
 
-- Primary runtime API surface: `SharpIpp/ISharpIppClient.cs` and `SharpIpp/ISharpIppServer.cs`
-- Operation identifiers: `SharpIpp/Protocol/Models/IppOperation.cs`
-- Request/response wiring: `SharpIpp/Mapping/Profiles/Requests` and `SharpIpp/Mapping/Profiles/Responses`
-- Server dispatch: `SharpIpp/SharpIppServer.cs`
-- Validation tests:
-  - unit: `SharpIpp.Tests.Unit`
-  - integration: `SharpIpp.Tests.Integration`
-- Specification document corpus: `docs/Content/Specification` (includes RFCs and PWG specs through 5100.22-2025)
+To avoid duplication, full documentation is maintained in the [`docs`](docs) directory:
+- **Client Operations & Examples:** See [`docs/Content/Client/Operations.md`](docs/Content/Client/Operations.md) and individual operation guides in [`docs/Content/Client/`](docs/Content/Client/).
+- **Server Implementation:** See [`docs/Content/Server/index.md`](docs/Content/Server/index.md).
+- **Client Nuances & Best Practices:** See [`docs/Content/Client/ConfigurationAndBestPractices.md`](docs/Content/Client/ConfigurationAndBestPractices.md).
+- **Specification Corpus:** Full RFCs and PWG specifications (through PWG 5100.22-2025) are located in [`docs/Content/Specification/`](docs/Content/Specification/).
 
-## Verified specification coverage snapshot
+## Core Source of Truth
 
-- Legacy baseline remains RFC 2911 + CUPS operations (see `README.md`).
-- Expanded spec corpus is present under DocFX, including:
-  - RFC 2911, RFC 8010, RFC 8011
-  - PWG 5100.x families including 5100.5, 5100.7, 5100.18, and 5100.22
-- IPP System Service support from PWG 5100.22-2025 is broadly implemented in client models and mappings.
+- **Client Contract:** [`SharpIpp/ISharpIppClient.cs`](SharpIpp/ISharpIppClient.cs) and `SharpIppClient.*.cs`
+- **Server Contract & Dispatch:** [`SharpIpp/ISharpIppServer.cs`](SharpIpp/ISharpIppServer.cs) and [`SharpIpp/SharpIppServer.cs`](SharpIpp/SharpIppServer.cs)
+- **Operation Enumeration:** [`SharpIpp/Protocol/Models/IppOperation.cs`](SharpIpp/Protocol/Models/IppOperation.cs)
+- **Mapping Profiles:** `SharpIpp/Mapping/Profiles/Requests` and `SharpIpp/Mapping/Profiles/Responses`
+- **Tests:** `SharpIpp.Tests.Unit` and `SharpIpp.Tests.Integration`
 
-## PWG 5100.22-2025 implementation notes
+## Agent Workflow for Spec-Parity Changes
 
-Implemented and wired in the client contract include System Service operations such as:
+When adding or updating an IPP operation or attribute, implement parity end-to-end:
 
-- `AllocatePrinterResourcesAsync`, `DeallocatePrinterResourcesAsync`
-- `CreatePrinterAsync`, `DeletePrinterAsync`, `GetPrintersAsync`, `GetPrinterResourcesAsync`
-- `GetSystemAttributesAsync`, `GetSystemSupportedValuesAsync`, `SetSystemAttributesAsync`
-- `DisableAllPrintersAsync`, `EnableAllPrintersAsync`, `PauseAllPrintersAsync`, `ResumeAllPrintersAsync`
-- `ShutdownOnePrinterAsync`, `StartupOnePrinterAsync`, `ShutdownAllPrintersAsync`, `StartupAllPrintersAsync`
-- `RestartSystemAsync`, `RestartOnePrinterAsync`
-- `RegisterOutputDeviceAsync`
-- System/resource subscription operations (`CreateSystemSubscriptionsAsync`, `CreateResourceSubscriptionsAsync`, etc.)
+1. Confirm or add the operation ID in [`IppOperation.cs`](SharpIpp/Protocol/Models/IppOperation.cs).
+2. Create request and response model types in `SharpIpp.Models`.
+3. Add client contract method in [`ISharpIppClient`](SharpIpp/ISharpIppClient.cs) and implementation in `SharpIppClient.*.cs`.
+4. Add request/response AutoMapper profiles.
+5. Add server dispatch mapping in [`SharpIppServer.ReceiveRequestAsync`](SharpIpp/SharpIppServer.cs).
+6. Add unit and integration tests (mapping, validation, and round-trip tests).
+7. Update documentation in [`docs/Content/Client/`](docs/Content/Client/) and [`docs/Content/Client/Operations.md`](docs/Content/Client/Operations.md).
 
-Additional 5100.22 model/mapping support verified:
+## Practical Guidance
 
-- `ResourceStatusAttributes.ResourceUuid`
-- strong typed collections for system/resource and power-policy/state objects
-- collection mapping in `CollectionProfiles` and related response profiles
-
-## Agent workflow for spec-parity changes
-
-When adding or correcting a spec operation/attribute, treat parity as end-to-end:
-
-1. Add/confirm operation id in `IppOperation`.
-2. Add request/response model types.
-3. Add client contract method in `ISharpIppClient` and implementation in `SharpIppClient.*.cs`.
-4. Add request/response profile wiring.
-5. Add server dispatch mapping in `SharpIppServer.ReceiveRequestAsync`.
-6. Add or update protocol attribute/profile mappings for any new fields.
-7. Add tests:
-   - unit mapping tests
-   - unit client request-operation mapping tests
-   - integration request/response roundtrip tests
-8. Update docs:
-  - `docs/Content/Client/Operations.md`
-   - any relevant specification or API pages
-
-## Practical guidance for agents
-
-- Prefer small, focused patches and keep naming aligned with existing IPP operation style.
-- Preserve bidirectional mapping symmetry for new attributes.
-- For enum arrays in IPP attributes, ensure both read and write mapping paths are covered.
-- Do not assume DocFX pages are fully current; verify behavior from code + tests first.
+- Prefer small, focused patches and preserve naming consistency with existing IPP models.
+- Maintain bidirectional mapping symmetry (read and write) for all protocol attributes.
+- Verify behavior against unit and integration tests before finishing.

CONTRIBUTING.md

@@ -18,16 +18,35 @@ git clone https://github.com/danielklecha/SharpIppNext.git
 cd SharpIppNext
 ```
 
+## Repository Structure
+
+The solution is divided into the following projects:
+
+- **[`SharpIpp`](SharpIpp)**: The core IPP protocol library, containing client (`ISharpIppClient`) and server (`ISharpIppServer`) implementations, models, and protocol serialization (targets `netstandard2.0` and `net10.0`).
+- **[`SharpIpp.Generators`](SharpIpp.Generators)**: Roslyn incremental source generators (`IIncrementalGenerator`) that produce compile-time object mapping (`SimpleMapper`) and validation routines, ensuring zero-reflection NativeAOT and trimming compatibility (targets `netstandard2.0`).
+- **[`SharpIpp.Generators.Tests.Unit`](SharpIpp.Generators.Tests.Unit)**: Unit tests for verifying source generator output and behavior.
+- **[`SharpIpp.Tests.Unit`](SharpIpp.Tests.Unit)** & **[`SharpIpp.Tests.Integration`](SharpIpp.Tests.Integration)**: Comprehensive test suites for protocol serialization, mapping symmetry, and end-to-end client/server workflows.
+- **`SharpIpp.Samples.*`**: Sample applications demonstrating standard usage, NativeAOT deployment, and UWP integrations.
+
 ## How to Contribute
 
 ### Building the Project
 
-You can build the project using the .NET CLI:
+You can build the entire solution using the .NET CLI:
 
 ```bash
 dotnet build --configuration Release
 ```
 
+### Working with Source Generators (`SharpIpp.Generators`)
+
+If you are modifying or extending attributes (`[IppRequest]`, `[IppResponse]`, `[IppAttribute]`) or mapping logic:
+
+- **Target Framework**: `SharpIpp.Generators` targets `netstandard2.0` as required by the Roslyn compiler infrastructure.
+- **Testing Generators**: When changing generator logic, add or update tests in [`SharpIpp.Generators.Tests.Unit`](SharpIpp.Generators.Tests.Unit).
+- **IDE Caching**: Visual Studio and IDEs may cache generator outputs in background compiler processes. If generated code does not appear to reflect edits immediately, rebuild the solution or restart the IDE Roslyn language server.
+
+
 ### Running Tests
 
 We use MSTest V2 for testing. To run all tests and collect coverage information, use:

README.md

@@ -5,7 +5,6 @@
 [![Docs](https://img.shields.io/badge/project-docs-blue)](https://danielklecha.github.io/SharpIppNext/)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](https://github.com/danielklecha/SharpIppNext/blob/master/LICENSE.txt)
 [![Coverage Status](https://coveralls.io/repos/github/danielklecha/SharpIppNext/badge.svg?branch=master)](https://coveralls.io/github/danielklecha/SharpIppNext?branch=master)
-[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/danielklecha/SharpIppNext)
 
 A .NET Standard library for building Internet Printing Protocol (IPP) clients and servers.
 
@@ -17,6 +16,8 @@ A .NET Standard library for building Internet Printing Protocol (IPP) clients an
 - **Over 70 Supported Operations**: Out-of-the-box methods for standard IPP operations, plus support for sending custom/extended requests via raw message mapping.
 - **System Service Support**: Broad support for IPP System Service operations defined in PWG 5100.22-2025, including system and printer resource management, power policies, and subscription operations.
 - **Two-Tier Validation**: Recursive model-level validation via a built-in zero-dependency validation engine alongside strict low-level RFC 8011 attribute and octet-limit validation.
+- **AOT & Trimming**: Full support for Native AOT compilation and assembly trimming.
+- **No Reflection**: Uses static validators and mappers with zero runtime reflection for optimal performance and trim safety.
 - **Strong-Named Assembly**: Available in both standard and strong-named NuGet packages.
 
 ## Installation
@@ -65,8 +66,10 @@ Console.WriteLine($"Printer State: {response.PrinterAttributes?.PrinterState}");
 
 ### Examples
 
-- Examples of the IPP client are included in the solution ([SharpIpp.Samples.Client](https://github.com/danielklecha/SharpIppNext/tree/master/SharpIpp.Samples.Client) and [SharpIpp.Samples.Client.NativeAot](https://github.com/danielklecha/SharpIppNext/tree/master/SharpIpp.Samples.Client.NativeAot)).
-- An example of the IPP server is available in the [SharpIppNextServer repository](https://github.com/danielklecha/SharpIppNextServer).
+- A basic IPP client example is included in the solution ([SharpIpp.Samples.Client](SharpIpp.Samples.Client)).
+- A NativeAOT IPP client example is included in the solution ([SharpIpp.Samples.Client.NativeAot](SharpIpp.Samples.Client.NativeAot)).
+- An example of the IPP client is available in the [IppCli repository](https://github.com/danielklecha/IppCli).
+- An example of the IPP server is available in the [IppPrinter repository](https://github.com/danielklecha/IppPrinter).
 
 ### Setting the IPP Version
 

SECURITY.md

@@ -2,12 +2,12 @@
 
 ## Supported Versions
 
-The following table outlines the support status for security updates. The current active version is `4.x.x`. We do not plan to update older versions. When version `5.0.0` is released, support for `4.x.x` will end.
+Security fixes are provided only for the **latest stable release**. Older versions and pre-releases are not supported. When a new release is published, support for previous versions ends immediately.
 
 | Version | Supported          |
 | ------- | ------------------ |
-| 4.x.x   | :white_check_mark: |
-| < 4.0   | :x:                |
+| Latest stable release | :white_check_mark: |
+| Older releases | :x:                |
 
 ## Reporting a Vulnerability
 

SharpIpp/SharpIpp.csproj

@@ -2,7 +2,7 @@
   <PropertyGroup>
     <TargetFrameworks>netstandard2.0;net10.0</TargetFrameworks>
     <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
-    <PackageIcon>ipp256.png</PackageIcon>
+    <PackageIcon>icon256.png</PackageIcon>
     <PackageIconUrl />
     <PackageProjectUrl>https://github.com/danielklecha/SharpIppNext</PackageProjectUrl>
     <Authors>Daniel Klecha;Evgeny Zelenov</Authors>
@@ -27,7 +27,7 @@
     <IsTrimmable>true</IsTrimmable>
   </PropertyGroup>
   <ItemGroup>
-    <None Include="..\ipp256.png">
+    <None Include="..\icon256.png">
       <Pack>True</Pack>
       <PackagePath></PackagePath>
     </None>

docs/Content/Client/AcknowledgeIdentifyPrinter.md

@@ -1,7 +1,29 @@
 # Acknowledge-Identify-Printer Example
 
+Acknowledges that an identify-printer request was received and acted upon by the output device.
+
+> [!NOTE]
+> Specification Reference: **PWG 5100.18 Section 6.2**
+
 ```csharp
+using System;
+using System.IO;
+using System.Threading.Tasks;
+using SharpIpp;
+using SharpIpp.Models.Requests;
+using SharpIpp.Protocol.Models;
+
 var client = new SharpIppClient();
-var request = new AcknowledgeIdentifyPrinterRequest();
+
+var request = new AcknowledgeIdentifyPrinterRequest
+{
+    OperationAttributes = new()
+    {
+        PrinterUri = new Uri("ipp://localhost:631/printers/my-printer")
+    }
+};
+
 var response = await client.AcknowledgeIdentifyPrinterAsync(request);
+Console.WriteLine($"Status: {response.StatusCode}");
 ```
+

docs/Content/Client/AddDocumentImages.md

@@ -1,7 +1,31 @@
 # Add-Document-Images Example
 
+Adds pre-processed document images to an existing document in a job.
+
+> [!NOTE]
+> Specification Reference: **PWG 5100.5**
+
 ```csharp
+using System;
+using System.IO;
+using System.Threading.Tasks;
+using SharpIpp;
+using SharpIpp.Models.Requests;
+using SharpIpp.Protocol.Models;
+
 var client = new SharpIppClient();
-var request = new AddDocumentImagesRequest();
+
+var request = new AddDocumentImagesRequest
+{
+    OperationAttributes = new()
+    {
+        PrinterUri = new Uri("ipp://localhost:631/printers/my-printer"),
+        JobId = 42,
+        DocumentNumber = 1
+    }
+};
+
 var response = await client.AddDocumentImagesAsync(request);
+Console.WriteLine($"Status: {response.StatusCode}");
 ```
+

docs/Content/Client/AllocatePrinterResources.md

@@ -1,7 +1,31 @@
 # Allocate-Printer-Resources Example
 
+Allocates installed resources (fonts, forms, ICC profiles) to a specific printer service.
+
+> [!NOTE]
+> Specification Reference: **PWG 5100.22-2025 Section 6.3.2**
+
 ```csharp
+using System;
+using System.IO;
+using System.Threading.Tasks;
+using SharpIpp;
+using SharpIpp.Models.Requests;
+using SharpIpp.Protocol.Models;
+
 var client = new SharpIppClient();
-var request = new AllocatePrinterResourcesRequest();
+
+var request = new AllocatePrinterResourcesRequest
+{
+    OperationAttributes = new()
+    {
+        SystemUri = new Uri("ipp://localhost:631/system"),
+        PrinterId = 1,
+        ResourceIds = [101, 102]
+    }
+};
+
 var response = await client.AllocatePrinterResourcesAsync(request);
+Console.WriteLine($"Status: {response.StatusCode}");
 ```
+

docs/Content/Client/CancelSubscription.md

@@ -1,7 +1,30 @@
 # Cancel-Subscription Example
 
+Cancels an existing event notification subscription.
+
+> [!NOTE]
+> Specification Reference: **RFC 3995 Section 5.3**
+
 ```csharp
+using System;
+using System.IO;
+using System.Threading.Tasks;
+using SharpIpp;
+using SharpIpp.Models.Requests;
+using SharpIpp.Protocol.Models;
+
 var client = new SharpIppClient();
-var request = new CancelSubscriptionRequest();
+
+var request = new CancelSubscriptionRequest
+{
+    OperationAttributes = new()
+    {
+        PrinterUri = new Uri("ipp://localhost:631/printers/my-printer"),
+        NotifySubscriptionId = 10
+    }
+};
+
 var response = await client.CancelSubscriptionAsync(request);
+Console.WriteLine($"Status: {response.StatusCode}");
 ```
+