docs: VeraCrypt knowledge base + widen crossrepostatus to all tracked repos - #29
Merged
Conversation
Resolves crossrepostatus.md: main pruned the file from 748 to 195 lines (29afb8b), so the pruned version is taken as the base and the scope-widening edits are reapplied on top rather than reverting the prune. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P5zDjB2RVZPB7rGAgHBsEn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a knowledge base for the VeraCrypt work and widens
crossrepostatus.mdso itcovers every tracked repository, not just the four Java siblings.
Why
The workspace was implicitly Java-only:
crossrepostatus.mdopened with "items thatspan ≥ 2 of the four sibling repos", and every guide, policy and the
java-tdd-guideskill assumed Maven. VeraCrypt (C/C++) had nowhere to live, so a long session's findings
existed only in a chat transcript.
What changed
1. New
VeraCrypt/folder — 8 files, ~1030 linesREADME.mdupstream-sync.mdbuild-verification.mdcoverage-measurement.mdlcov/gcovrreport wrong numbers here; use plaingcovtest-coverage-work.mdconcurrency-findings.mdcode-findings.mdif_debugin Release, uncovered-but-reachable pathscontributions.mdThe single most reusable fact recorded: different platforms compile different source
files.
src/Common/is not in the LinuxPROJ_DIRS, andsrc/Volume/**appears in no.vcxprojat all — so "where is this code used" has no single answer, and severalotherwise-sensible assumptions break on it.
2. Two-tier scope in
crossrepostatus.mdandCLAUDE.mdRather than deleting the Java-only limitation, the repos are now split into a Java tier
(BAF, jllama, srcmorph, sb — governed by the guides, policies and the skill) and other
tracked repos (VeraCrypt, llama.cpp, subprocess.h — own conventions, own folder).
The parity tables compare Maven, PIT and SpotBugs, so they genuinely cannot have rows for
a C/C++ repo. The scope note now says so explicitly — a blank is a non-applicability
rather than a gap — otherwise every missing VeraCrypt row reads as an omission.
Factual statements in the body of
crossrepostatus.mdthat say "all four repos" were leftalone; they are true statements about the Java repos and rewriting them would damage
correct history.
Merge resolution worth noting
mainprunedcrossrepostatus.mdfrom 748 to 195 lines in 29afb8b while this branch wasopen, which conflicted. Resolved by taking main's pruned version as the base and
reapplying the scope-widening edits on top — the prune is not reverted. Verified: the diff
against
maincontains no deletions.Scope
Documentation only. No production code, no build system, no changes to any sibling repo.
The findings in
concurrency-findings.mdandcode-findings.mdare a local record andwere deliberately not reported upstream; the upstream PR (veracrypt/VeraCrypt#1850)
contains tests only.
Assembled with the support of Anthropic Claude Opus.