Apply baseline repo tooling to atmosphere #1
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/atmosphere#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally filed by @coilysiren on 2026-05-21T06:03:42Z - https://github.com/coilysiren/atmosphere/issues/2
atmosphere was scaffolded in #1 without the standard coilysiren/* baseline. Apply it once idea-dumping settles down:
make apply-rulesetsfrom agentic-os-kai.make apply-agentic-os-hooks..coily/coily.yamlwith a catalog block and any dev-command verbs the first apps need.data/catalog-graph.yamlnodes and the repo-on-disk manifest so digests and the registry pick it up.Not urgent. The repo has no build commands yet, so the lockdown routing gap does not bite until the first app lands.
Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.