The fastlane manifest: where development actually happens #6
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Ting/Jostoph!6
Loading…
Reference in a new issue
No description provided.
Delete branch "agent.teyla/Jostoph:tango/fastlane-manifest"
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?
Owner direction, 2026-08-10 (in flake-ops' kanidm session): the estate's development manifest lives HERE, with the steward, beside the
.doctor.justcurrently in transit — not in a repo of its own. Both halves ship in this PR, dotfiles like the seams that read them..fastlane.toml— the canonical map every repo's seam fetches raw (anonymous https) and caches beside its justfile: each midgard-pinned flake input named to the development repo the source org actually works on..fastlane.just— the seam itself, a standalone justfile with one recipe. A consuming repo picks it up two ways:mod? fastlane ".fastlane.just"for direct use (just fastlane::assemble), and a variable —flake_override := if path_exists(...) == "true" { `just -f .fastlane.just assemble` } else { "" }— whose flags whatever runs nix splices in. PRESENCE IS THE TOGGLE: file in place → evaluations run against the manifest's dev repos atref(default fastlane,ref=<other>per invocation); file absent → the published world. Deploys run from the lock regardless.First consumer: lar.ad/flake-ops, wired exactly this way; its fetch falls back to the cached copy until this merges (fallback path exercised). The
midgard/fastlanerepo briefly created for this purpose today is superseded by this PR and should be deleted (the agent toolset has no repo-delete verb).