#37 docs: integrate security and I2P portfolio publication workflow

[Anonymous]

Originally created by: knoksen

Summary

Adds a repository-native publication structure for the consolidated Secure Systems & I2P portfolio without committing large PDF binaries to Git history.

Included

• portfolio landing pages and editorial manifest;
• evidence classes and explicit claim-control rules;
• canonical SHA-256 values for the prepared Executive PDF, Complete PDF, and publication ZIP;
• cross-platform PowerShell integrity verification;
• GitHub CLI release publishing with hash gating, exact asset matching, -WhatIf, and no embedded credentials;
• validation, publishing, changelog, and next-step documentation.

Validation performed

• Recalculated SHA-256 digests for all three prepared artifacts.
• Confirmed the branch is based on current main and only adds portfolio documentation and release automation.
• Large PDFs remain release assets and do not bloat repository history.

Validation still required

PowerShell 7 was not available in the preparation runtime. Before merge or publication:

1. parse and run both PowerShell scripts with PowerShell 7;
2. execute Publish-PortfolioRelease.ps1 with -WhatIf;
3. verify the authenticated gh account and release target;
4. review all external-facing security claims against primary repository evidence.

Security boundary

This PR does not claim that the simulator provides production I2P routing, anonymity, quantum resistance, or verified end-to-end encryption. The added editorial rules require simulations, prototypes, research synthesis, verified implementations, and future targets to be distinguished explicitly.

[Anonymous]

Originally posted by: codacy-production[bot]

Not up to standards ⛔

🔴 Issues 1 medium

>
> > > **Alerts:** > ⚠ 1 issue (≤ 0 issues of at least minor severity) > > > **Results:** > `1` new issue > > | Category | Results | > | ------------- | ------------- | > | ErrorProne | `1` medium | > > > [View in Codacy](https://app.codacy.com/gh/knoksen/I2P_knoks/pull-requests/37/issues) >

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

<themed-picture data-catalyst-inline="true" data-catalyst="" style="visibility: visible;"><picture></picture></themed-picture>

_{TIP This summary will be updated as you push new changes.}

[Anonymous]

Ticket changed by: knoksen

• status: open --> closed