aere-network/aere-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

anchor/README: the staging script is cited as an operator-repository path and declared

Browse Source
This commit is contained in:
Aere Network 2026-09-02 21:46:50 +03:00
parent 1d3fc3e54e
commit 985bc961f4
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
CITATIONS-UNRESOLVED.md
View File

@ -13,9 +13,10 @@ Paths that DO resolve are written relative to a side-by-side checkout of the Aer
repositories, so they begin with a repository name, for example
`aere-contracts/contracts/pqc/AereCryptoRegistry.sol`.
Unresolvable distinct paths in this repository: **18**.
Unresolvable distinct paths in this repository: **19**.
- `aere-client2/src/Nethermind/Nethermind.Core/AereFloorLapse.cs` cited in: aere-node/SPEC.md
- `aerenew/publish-bundle/stage-anchor.cjs` cited in: aere-node/anchor/README.md
- `ARMAREA-IMPUNERII-MESAJELOR-2026-09-02.md` cited in: aere-node/SPEC.md
- `armeaza-impunerea-pe-flota.sh` cited in: aere-node/SPEC.md
- `CE-DEVINE-INVALID-LA-ANCORA-2026-08-07.md` cited in: aere-node/SPEC.md

2
anchor/README.md
View File

@ -126,7 +126,7 @@ now pinned: change one byte of it and the digest no longer matches, and the head
Updated 2026-08-29. The first publication of this directory, on 2026-08-11, was staged by hand and
was never refreshed: by 29 August, 63 of the 78 files here had changed in the tree we actually run
and 50 files had never been published at all. That is fixed at the root rather than by one copy —
`stage-anchor.cjs` in our repository derives this directory from the authoritative overlay, refuses
`aerenew/publish-bundle/stage-anchor.cjs` in the operator repository derives this directory from the authoritative overlay, refuses
to run if the two files this README tells you to read first are missing, deletes what we removed
rather than letting the published set grow monotonically, and stops on the secret-scanner's verdict
instead of around it. The per-file SHA-256 list is in `MANIFEST-sha256.txt`.