REMEDIATE-WEBSITE: remove ArcadiaB exports and internal docs; publish a built _site/; hermes-gate deprecated - #126
Merged
Merged
Conversation
Authorised by op-at-specs/OPEN-CLOSED-RULE.md ledger, 2026-08-25: "ArcadiaB CSVs + internal docs in website repo | Remove from public tree" "Internal docs in public trees | Removed, except op-adapters FIDELITY-NOTES" Removed: arcadiab-facebook.csv, arcadiab-linkedin.csv, arcadiab-linkedin-week.csv (added 2dd421c, 2026-03-13); internal/stats/index.html (88305b9, 2026-05-12); REPO_MAP.md (fc66257); IMPLEMENTATION_GUIDE.md (6d5bfba); DEMO-SCRIPT-MAR18.md (56f6324); scripts/ATLAS-HANDOFF.md (d45a490). Serving is unchanged by this commit: every one of these paths already returned a forced 404 from netlify.toml. What changes is the repository, which is public, so the files were readable there regardless of what the domain served. RESIDUAL HISTORY: removal from HEAD does not remove these blobs from history. They remain reachable at every commit from their addition to this one, on this branch and on every other ref that carries those commits, and in any clone or fork already taken. No force-push and no history rewrite, per the rule's principle 4 and the standing retirement of force-push over pushed commits.
…here the SDK repo pointer lands
@observer-protocol/hermes-gate has carried an npm deprecation notice since
2026-08-04 (measured 2026-08-25: version 0.2.1, no repository field, superseded
by @observer-protocol/policy-engine plus the per-rail adapters, nothing
unpublished). The page still offered three npx bootstrap commands as the way
in. The install block is gone, the copy button's script with it, and the
Solution section now opens with the deprecation and where the replacement is.
The .install-block CSS rules stay: nothing uses them, but removing them is a
stylesheet edit this change does not need.
@observer-protocol/sdk (npm) and observer-protocol (PyPI) both name
github.com/observer-protocol/observer-protocol-spec as their repository. That
repository was renamed and GitHub 301s it to observer-protocol/op-legacy-deployment
(measured 2026-08-25, gh api: public, not archived). integrate/ links two paths
under the old name and now says where they land; ows/ says the same beside its
existing deprecation note. The links are kept: they resolve, and the note is
what tells a reader why the destination has a different name.
Session REMEDIATE-WEBSITE, under op-at-specs/OPEN-CLOSED-RULE.md ledger
2026-08-25 ("Internal docs in public trees"; "op-legacy-deployment" ruling
not yet executed, so this copy states the redirect and not the visibility).
netlify.toml said `publish = "."` and documented the durable fix as "a repo restructure ... deliberately not being done here". This is that fix, done without moving a single served file: tools/build-site.sh builds _site/ from an allowlist (root files by web extension, plus fourteen named directories), refuses if any non-web kind reaches the output, and prints every tracked file it withheld. netlify.toml publishes _site/ and runs the script as the build command. Shipping a file is now a decision made in that script, in a commit; until now it was the default and nothing looked broken when it happened. VERIFIED LOCALLY BEFORE THIS COMMIT. The built set is 103 files, identical as a set to the served population derived from the tree (tracked, minus dotfiles, netlify.toml, scripts/, tools/, internal/ and the two forced-404 root files), and byte-identical file by file (cmp, 0 mismatches). Every path that returned 200 on the live site at 21aa1ff and is a file in the tree is present. Four mutations behaved: a .csv inside an allowlisted directory fails the build; a .md at the root and a new directory are withheld; a root .html ships. The per-file forced-404 rules are gone with the files they named (removed at 1d34fb1) and with the mechanism that made them necessary. The /internal/*, /scripts/*, /tools/* and two root-file rules go too: those paths are not in the allowlist, so they do not exist in the publish directory, and a rule for a path that cannot exist is a second representation of one decision. The five directory walkers in scripts/ (check-shared-copy, sweep-sentences, check-outbound-links, check-measured-figures, sentences-at-risk) now skip _site/. Measured: with a local build present, check-shared-copy re-reported three allowed exceptions under their _site/ paths and went red; with the skip it is green. CI never has a build present, so CI would not have shown this; a developer's local run would have, for the wrong reason. CONVENTIONS §3 rewritten: it said adding a non-web file makes it public, and that is no longer true. .gitignore excludes _site/. Session REMEDIATE-WEBSITE, under op-at-specs/OPEN-CLOSED-RULE.md ledger 2026-08-25 ("ArcadiaB CSVs + internal docs in website repo"; "Internal docs in public trees"), and the 2026-08-06 ruling to move the publish directory off the repository root.
Derived by tools/make-sitemap.py from git; the three pages changed in the previous content commit and the sitemap must be regenerated after, not before. Session REMEDIATE-WEBSITE.
✅ Deploy Preview for observerprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Authorised by op-at-specs/OPEN-CLOSED-RULE.md ledger 2026-08-25 (b2b9987), entries
"ArcadiaB CSVs + internal docs in website repo | Remove from public tree" and
"Internal docs in public trees | Removed, except op-adapters FIDELITY-NOTES".
Four commits, each standing alone:
1d34fb1removes arcadiab-facebook.csv, arcadiab-linkedin.csv, arcadiab-linkedin-week.csv, internal/ (incl. internal/stats/), REPO_MAP.md, IMPLEMENTATION_GUIDE.md, DEMO-SCRIPT-MAR18.md, scripts/ATLAS-HANDOFF.md from HEAD. Residual history: the blobs stay reachable at every earlier commit and in every clone; no force-push, no rewrite.6facb1chermes-agents.html marks @observer-protocol/hermes-gate deprecated (npm notice dated 2026-08-04) and drops the npx install block; integrate/ and ows/ say the SDK packages' repository pointer (observer-protocol-spec) redirects to op-legacy-deployment.4d09165the restructure netlify.toml called deliberately deferred:publish = "_site", built by tools/build-site.sh from an allowlist. Verified locally: 103 files, identical set and identical bytes to the served population derived from the tree. Five scripts/ walkers skip _site/. CONVENTIONS §3 rewritten.7165173sitemap lastmod regenerated.Deploy-preview checks to run before merge: the three previously forced-404 paths still 404, every sitemap page 200, non-HTML artifacts byte-identical to the tree.