Skip to content

RDoc-4091 Agentic Documentation & RDoc-4100 - #2660

Open
poissoncorp wants to merge 2 commits into
ravendb:mainfrom
poissoncorp:RDoc-4091-host-agent-skill
Open

RDoc-4091 Agentic Documentation & RDoc-4100#2660
poissoncorp wants to merge 2 commits into
ravendb:mainfrom
poissoncorp:RDoc-4091-host-agent-skill

Conversation

@poissoncorp

Copy link
Copy Markdown
Contributor

Issue link

https://issues.hibernatingrhinos.com/issue/RDoc-4091
https://issues.hibernatingrhinos.com/issue/RDoc-4100

Additional description

Two commits, one per ticket.

RDoc-4091 serves the agent skill from static/skills/ravendb/ at /skills/ravendb/, verbatim, no plugin. Needs md in staticAssetRegex or every skill URL 404s.

RDoc-4100 makes deploy phase 3 publish the edge function and the CSP. Both needed a manual step that fails silently when skipped: the site deploys green while the edge stays old. The CSP moves from an uncommitted JS generator to scripts/lib/csp-policy.js.

Type of change

  • Content - docs
  • Content - cloud
  • Content - Quill
  • Content - guides
  • Content - start pages/other
  • New docs feature (consider updating /templates or readme)
  • Bug fix
  • Optimization
  • Other

Changes in docs URLs

  • No changes in docs URLs
  • Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

  • No changes in UX/UI
  • Changes in UX/UI (include screenshots and description)

Serve the RavenDB agent skill from static/skills/ravendb/ at /skills/ravendb/,
verbatim, outside the version prefix. No plugin, no build step.

handle_redirects.js gains `md` in staticAssetRegex; without it a versionless
.md URL 301s to /7.2/<path>.md and every skill URL 404s. The tree is kept as
published because SKILL.md navigates it with relative links.
The viewer-request function and the CSP live in this repo but never travelled
with the S3 upload, so both needed a manual publish that fails silently when
skipped: the site deploys cleanly while the edge keeps behaving like the
previous release. deploy.ps1 phase 3 now pushes them alongside the KVS table.

The CSP becomes scripts/lib/csp-policy.js, shaped like version-policy.js: a
directive map with a comment per host naming the tag that needs it, plus a
render function, runnable directly to print the header. It renders
byte-identical to what production serves, so prod is a no-op; staging is on an
April CSP and gets brought up to date.

Both AWS APIs replace the whole config, so both scripts re-send it verbatim.
For the CSP the patch is also proved to touch one field before writing and read
back afterwards, since that policy carries CORS and a one-year HSTS besides.
@poissoncorp
poissoncorp requested a review from Lwiel September 10, 2026 01:38
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.

2 participants