Skip to content

docs: deprecation banner — standalone is public release surface only - #7

Closed
random1st wants to merge 1 commit into
mainfrom
g0.1b-deprecation-notice
Closed

docs: deprecation banner — standalone is public release surface only#7
random1st wants to merge 1 commit into
mainfrom
g0.1b-deprecation-notice

Conversation

@random1st

Copy link
Copy Markdown
Owner

Summary

  • Adds a deprecation banner to the README clarifying that this repo is now a public release surface synced from the Diana monolith
  • v0.5.3 was the last release built directly from this source tree
  • New versions will land here via tools/release-secguard.sh (G0.5 / RAN-424)

Context

Active development moved into the Diana monolith on 2026-05-19 via decision.diana-monolith-restoration. secguard v2 production hardening continues there under RAN-411.

Test plan

  • Banner renders correctly on GitHub README view
  • Links resolve (RAN-411, RAN-424)
  • No accidental changes to install.sh, Cargo.toml, or source

Active development moved into the Diana monolith on 2026-05-19
(decision.diana-monolith-restoration). Canonical crates now live at
~/.diana/src/rust/crates/diana-{guard,secrets,secguard-brain}/.

This repo continues as the public release surface — new versions
published here via tools/release-secguard.sh sync from monolith.
v0.5.3 was the last release built from this source tree directly.

Linked: RAN-411 (epic), RAN-412 (G0.1 deprecation notice),
RAN-424 (G0.5 sync mechanism), decision.secguard-sync-mechanism.
@random1st

Copy link
Copy Markdown
Owner Author

Superseded. This banner said active development had moved into the Diana monolith; as of d45bbb5 the direction is the other way — six detectors (autostash, deobfuscate, findings, injection, lockdown, verifier, 3532 lines) were ported into this repository because the guard layer lives here now. The Linear links are also stale: that tracker was replaced by Diana's native one.

Closing rather than merging: a public README should not carry a statement that was true in May and is false today. If a banner is still wanted, it should describe the current arrangement, and that is a new PR, not this one.

@random1st random1st closed this Aug 10, 2026
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