feat: scaffold the static offline app, governance, and CI gate #61
No reviewers
Labels
No labels
area: arcade
area: art-studio
area: calendar
area: chapel
area: content
area: design
area: field-guide
area: infra
area: library
area: os
area: portal
area: sync
area: typing
blocked
breaking
bug
content: approved
content: changes-requested
content: drafting
content: needs-doctrinal-review
content: needs-review
dependencies
documentation
duplicate
enhancement
epic
github_actions
good first issue
help wanted
invalid
javascript
needs-triage
priority: high
priority: low
priority: medium
question
type: enhancement
type: feature
type: fix
type: perf
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Bosco/bosco!61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/core-scaffold"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
Establishes the v0.1.0 Core foundations — the offline invariant made mechanical, and the tracking/CI scaffolding the rest of the roadmap rides on.
adapter-static(strict) — every route prerendered; a non-prerenderable route fails the build..gitattributespins LF.scripts/check-external-urls.mjsgreps the built output and fails on any external URL.cicheck: type/a11y check → lint → build → external-URL guard → unit tests → PR-title lint.develop; Conventional Commits with a customcontent:type.scripts/serve-static.mjs: a zero-dep static server standing in for the production nginx container (offline verification).Verified locally:
pnpm check(0/0),pnpm lint,pnpm build,pnpm guard:external,pnpm test:unitall green.First of two PRs for Core; the content module, local-first data layer, and vendored calendar follow.