openDox root: bump code to 05bbde80 (S3 fail-closed follow-up, S4 route-tail split, S6 /source core-arm)

[brettheap]

Lane: openxfactory-4-opendox-extraction

Refs opensoft/openxFactory#656 (stays OPEN). CLAIM: 5647338637.

First leg of the pin lockstep that advances openxFactory's openDox and
openXdox pins to the § 3.4 S4/S6 landings (precedent: this root's own #6,
openXdox's #8, then openxFactory#984 — the same order, followed here).

code (opensoft/openDox-code) advances a99eba03 → 05bbde80:

• S4 (§ 3.4 S4: split the three RULED SPLIT files — thirteen route tails to the bindings that call them openDox-code#17): the thirteen gate-route constants
  declared in lens-model.js, repo-selector.js, staging-workbench- model.js split to the class-B bindings that call them (four new files);
  /actions/refresh measured and stays class A.
• S3 fail-closed follow-up (View registry: refuse a malformed contributed-routes column instead of coercing it (S3 follow-up; fails closed per § 4.1) openDox-code#18, landed via #22
  after a base-branch retarget correction — see openDox + openXdox: two open-source layers, an installable app with users, projects and a database; domain descendants pin openXdox (Brett's ruling 2026-09-04) openxFactory#656's
  S4 landing note for the detail): requireRouteShape(claimed) now refuses
  a contributed-routes entry with a missing string pattern or a
  non-boolean is_prefix, shared between manifestRoutes() and
  ownershipBreach().
• S6 (§ 3.4 S6: /source becomes openDox's own fixed core arm (RULED Q4) openDox-code#16, RULED Q4): /source becomes openDox's
  own fixed core arm in serve.py, above the § 2.4 contributed consult.

spec is unchanged. scripts/validate-pins.py recomputes the tree digest
(98634678b193dd9e24a6ab86211546e6b415864dabffd44999f18ff646c01a81) and
confirms gitlink/pin-file lockstep; validate-manifest.py and
validate-repository-naming.py also pass. No .github/workflows/*.yml
names this leg by sha.

🤖 Generated with Claude Code

Summary by Sourcery

Advance the openDox code pin to incorporate route validation hardening, route-tail classification, and the fixed /source core arm.

New Features:

• Advance the openDox code dependency to the S4/S6 landing revision, including fail-closed route validation and a fixed core /source arm.

Bug Fixes:

• Reject contributed route entries with missing or invalid route-shape fields during manifest and ownership checks.

Enhancements:

• Separate gate-route constants into class-B bindings while retaining /actions/refresh as class A.

Chores:

• Update the code pin and verified tree digest to maintain repository lockstep.

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 17 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the openDox code pin to 05bbde80 and its verified tree digest, incorporating the S4 route-tail binding split, S3 fail-closed route-shape validation, and S6 fixed core handling for /source; specification files remain unchanged.

Sequence diagram for fail-closed contributed-route validation

sequenceDiagram
    participant Manifest as manifestRoutes()
    participant Shape as requireRouteShape(claimed)
    participant Breach as ownershipBreach()

    Manifest->>Shape: validate contributed route
    Shape-->>Manifest: valid route shape
    Breach->>Shape: validate contributed route
    Shape-->>Breach: valid route shape
    alt missing string pattern or non-boolean is_prefix
        Shape-->>Manifest: reject route
        Shape-->>Breach: reject route
    end

Loading

Flow diagram for fixed core /source routing

flowchart TD
    Request[HTTP request]
    Source{path is /source}
    Core[openDox fixed core arm]
    Contributed[Contributed route consult]
    Response[Route response]

    Request --> Source
    Source -->|yes| Core
    Source -->|no| Contributed
    Core --> Response
    Contributed --> Response

Loading

File-Level Changes

Change	Details	Files
Advance the openDox code submodule pin and synchronize its verified tree digest.	Update the code gitlink from a99eba03 to 05bbde80. Replace the recorded tree SHA-256 digest with the digest for the new revision. Preserve commit-based pin verification and lockstep metadata.	code contracts/code-pin.yaml
Bring in S4 route-tail binding splits while retaining the class-A refresh route.	Move thirteen gate-route constants from model modules into four class-B binding files. Keep /actions/refresh measured as class A.	code
Harden contributed-route validation to fail closed on malformed route shapes.	Require contributed routes to have a string pattern and boolean is_prefix. Share the validation between manifest route generation and ownership-breach checks.	code
Make /source an openDox-owned fixed core arm before contributed-route consultation.	Add the fixed /source handling in serve.py ahead of the § 2.4 contributed consult. Apply the S6 core-arm routing behavior.	code

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

🔵 Needs a closer look

Advance the code gitlink to match the recorded pin and restore lockstep validation.

Pull request overview

Advances the openDox code pin to include route validation hardening, route-tail classification, and the fixed /source core arm.

Changes:

• Updates the pinned commit and verified tree digest.
• Preserves the documented spec and workflow references.
• The corresponding code gitlink remains unadvanced, breaking pin lockstep.

File summaries

File	Summary
contracts/code-pin.yaml	Records the new code commit and tree digest; the matching code gitlink must also be updated.

Review details

Suppressed comments (1)

contracts/code-pin.yaml:24

• This change updates only the recorded pin; the corresponding code submodule gitlink is not moved in the diff. That leaves the lockstep invariant broken and scripts/validate-pins.py will report pin-gitlink-mismatch until the gitlink is advanced to 05bbde80f91a870f23aaa762fc03e40635ccbffd in the same commit. Please use scripts/bump-leg.py (or otherwise update the gitlink and rerun make validate).

commit: "05bbde80f91a870f23aaa762fc03e40635ccbffd"

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.