Task: Scaffold story: Update ORE to v17

Table of Contents

This page documents a task in the Update ORE to v17 story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

Create the story that brings the vendored ORE engine up to v1.8.17.0. Scaffold its tasks and the branch, and wire them into Sprint 25.

2. Status

Field Value
State DONE
Parent story Update ORE to v17
Now Nothing.
Waiting on Review of PR #2070.
Next Nothing.
Last touched 2026-09-11

3. Acceptance

  • The story, its four tasks and the branch exist, and Sprint 25 lists the story.
  • The local site build check passes.

4. Plan

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

5. Notes

6. Test Scenarios

Manual QA scenarios (scaffolded via compass add test_scenario, run through the QA Validation Runner panel) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Scenario State Notes
     

7. PRs

PR Title
#2070 [agile] Scaffold the ORE v17 update story

8. Review

Comment summary File Decision Notes
       

9. Result

The story, its tasks and the branch are in place, and Sprint 25 lists the story.

  • feature/update-ore-to-v17 was created off origin/main (e4c8cf984f).
  • Four tasks were scaffolded: this one, the examples and XSD sync, the package build and vendor, and the dual-version publish.
  • The local site build check passed. compass build --direct site exited 0, and all five new pages published.

Two reconnaissance findings are recorded in the story's * Decisions: TA002_IR_Swap.tar.gz is unchanged, and external/ore/packages/manifest.json is stale against the tracked tarball.

Emacs 29.3 (Org mode 9.6.15)