Engineering review
Render service, sprint 14
Where the work stands, what ships next quarter, and the evidence from the latest run.
Sprint board
To do2 cards
Retry artifact uploads with backoff
Storage resets drop
run_8123uploads; retry with jitter before failing the run.Per-key rate limit dashboard
In progress2 cards
Validate roadmap periods at compile time
Report unknown and reversed periods at the item path.
Stream compile logs to the run page
Review1 card
Drop the legacy v0 runs endpoint
Every client moved to
/v1/runsin sprint 12.
Done2 cards
Deterministic schema tree order
Cache spec hashes per key
Roadmap
- 2026-Q3
- 2026-Q4
- 2027-Q1
- 2027-Q2
Compiler core
- Composition and datasets
- Engineering widgets
- Theme dialects
Platform
- Upload retries and backoff
- Multi-region artifact storage
2026-Q3
- Composition and datasets
2026-Q4
- Engineering widgets
- Upload retries and backoff
2027-Q1
- Theme dialects
- Multi-region artifact storage
Latest test run
2 of 10 tests failed
- Failed
- 2
- Flaky
- 1
- Skipped
- 1
- Passed
- 6
- Duration
- 4.6 s
- Coverage
- 87.4%
compiler/normalize1 failed, 3 passed · 122 ms
- Failedrejects a reversed roadmap range18 ms
tests/unit/engineering-widgets.test.ts:212 - Passedkeeps node ids stable across runs42 ms
- Passedreports nested slot paths37 ms
- Passedresolves datasets once25 ms
storage/uploads1 failed, 1 passed · 3.1 s
- Failedretries a reset connection3 s
tests/unit/storage-upload.test.ts:48 - Passedwrites the etag on success88 ms
render/engineering1 flaky, 1 skipped, 2 passed · 1.3 s
- Flakylog viewer adds search past 20 lines1.2 s
- Passedkanban rows carry the filter contract61 ms
- Passedroadmap renders no inline style33 ms
- Skippedschema tree prints open
Service log
render-api, 10:00 to 10:08 UTC
40 lines ·
- 7 debug
- 23 info
- 6 warn
- 4 error
- INFOapi
- INFOworker
- DEBUGworker
- INFOcompiler
- INFOapi
- DEBUGscheduler
- INFOworker
- WARNworker
- INFOcompiler
- DEBUGstorage
- INFOapi
- WARNapi
- INFOworker
- ERRORstorage
- WARNworker
- ERRORstorage
- WARNworker
- INFOstorage
- INFOapi
- DEBUGscheduler
- INFOworker
- INFOcompiler
- ERRORcompiler
- INFOapi
- WARNapi
- INFOworker
- DEBUGworker
- INFOapi
- ERRORapi
- INFOscheduler
- DEBUGscheduler
- INFOworker
- INFOcompiler
- INFOstorage
- INFOapi
- WARNworker
- INFOworker
- INFOcompiler
- INFOscheduler
- DEBUGscheduler
API reference
POST /v1/projects/{project}/runs
Queues a compile of one Page Spec and returns the run. The artifact is ready when status is done.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
project required | path | string | Project slug, such as docs-site. |
priority | query | boolean | Use the priority queue. Counts double against the rate limit. |
Idempotency-Key | header | string | Repeat a request safely; the same key returns the same run for 24 hours. |
Request body
{
"spec": "version: 1\nmeta:\n title: Weekly recap",
"theme": "terminal-mono"
}Responses
201The run was queued.
201 responsejson{ "id": "run_8128", "status": "queued", "createdAt": "2026-10-06T10:08:12Z" }422The spec failed validation;
diagnosticslists every problem with its path.429The key exceeded its rate limit. Retry after the
Retry-Afterseconds.
Run payload schema
- idstringrequired
Run id, such as
run_8128. - statusenumrequired
queued, running, done or failed.
projectobject
- slugstringrequired
- namestring
specobject
- hashstringrequired
SHA-256 of the normalized spec.
- bytesinteger
artifactobject
- urlstring
Present once the run is done.
- bytesinteger
- etagstring
timingobject
- queuedMsinteger
- compileMsinteger
diagnosticsarray
Empty when the spec is valid.
- codestringrequired
- pathstringrequired
JSON path of the problem, such as
$.blocks[2].items[0].end. - messagestring