Skip to content

refactor(boundary): Move SSL and writable output contract#1161

Merged
leumor merged 1 commit intodevelopfrom
feature/crypto-keys-boundary-cleanup
Mar 23, 2026
Merged

refactor(boundary): Move SSL and writable output contract#1161
leumor merged 1 commit intodevelopfrom
feature/crypto-keys-boundary-cleanup

Conversation

@leumor
Copy link
Collaborator

@leumor leumor commented Mar 23, 2026

Summary

  • move SSL from network.crypta.crypt to network.crypta.node.runtime so future foundation-crypto-keys extraction work no longer pulls config/runtime glue through crypt
  • move network.crypta.io.WritableToDataOutputStream into :foundation-support without changing its package name or semantics
  • update affected production and test imports, and add network/crypta/io/WritableToDataOutputStream* to foundation-support owned output metadata

Testing

  • ./gradlew verifySelectiveLeafOwnershipMetadata compileJava compileTestJava
  • ./gradlew test --tests network.crypta.crypt.SSLTest --tests network.crypta.io.SSLNetworkInterfaceTest --tests network.crypta.node.NodeStarterTest --tests network.crypta.node.TextModeClientInterfaceServerTest --tests network.crypta.support.SerializerTest
  • grep -R "^import network\.crypta\.config\." src/main/java/network/crypta/crypt src/main/java/network/crypta/keys
  • ./gradlew cleanTest test

Notes

  • no intended behavior changes; this is a prep PR for a later foundation-crypto-keys extraction
  • a non-clean ./gradlew test hit a transient Gradle in-progress-results-*.bin NoSuchFileException, but the clean rerun passed

Move SSL into network.crypta.node.runtime so future crypto-keys extraction work no longer carries config glue inside network.crypta.crypt.

Move WritableToDataOutputStream into foundation-support and register its owned output pattern so stale aggregated root outputs are pruned correctly.

Update affected production and test imports to use the relocated types without changing behavior.
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
74.5% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@leumor leumor merged commit 3172afb into develop Mar 23, 2026
7 of 9 checks passed
@leumor leumor deleted the feature/crypto-keys-boundary-cleanup branch March 23, 2026 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant