Migrate ELF issue tracking to Linear-only#107
Open
yvette-carlisle wants to merge 6 commits intomainfrom
Open
Conversation
…ete linear-only issue migration","intent":"remove repository and API dependencies on GitHub Issues so ELF uses Linear as the sole work tracker","impact":"disables GitHub Issues, removes triage automation, updates docs references, and rejects legacy doc issue_number provenance","breaking":true,"risk":"medium","authority":"linear","delivery_mode":"status-only","refs":[]}
…openviking issue appendix","intent":"remove an unnecessary issue-link appendix from the external comparison research doc while keeping the architectural guidance intact","impact":"simplifies the research note by leaving only the architectural comparison and source references","breaking":false,"risk":"low","authority":"linear","delivery_mode":"status-only","refs":[]}
…issue inventory link from readme","intent":"keep the public README focused on product-facing documentation instead of internal work tracking artifacts","impact":"removes the research issue inventory link from the README while preserving the detailed external comparison entrypoint","breaking":false,"risk":"low","authority":"linear","delivery_mode":"status-only","refs":[]}
… issue-number doc provenance support","intent":"separate ELF project workflow migration from the dev-source provenance schema so content can still refer to GitHub issues when needed","impact":"re-enables issue_number for doc_source_ref/v1 dev payloads in the MCP schema, service validation, and spec","breaking":false,"risk":"low","authority":"linear","delivery_mode":"status-only","refs":[]}
…xum route params to brace syntax","intent":"restore CI integration and e2e jobs by using the path parameter syntax required by axum 0.8 routers","impact":"prevents router construction panics in elf-api so the API boots correctly under integration and harness coverage","breaking":false,"risk":"low","authority":"linear","delivery_mode":"status-only","refs":[]}
… payload shaping integration fixtures","intent":"restore the red integration suite by seeding searchable chunk data for API payload-shaping tests and aligning service assertions with current write-gate behavior","impact":"keeps payload-shaping coverage green across elf-api and elf-service integration runs without changing runtime behavior","breaking":false,"risk":"low","authority":"linear","delivery_mode":"status-only","refs":[]}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
issue_numberfrom doc dev provenance so docs ingestion no longer depends on GitHub Issues#nnreferences and deleting GitHub issue attachmentsVerification
cargo make fmt-rust-checkcargo make test-rustNotes
doc_source_ref/v1dev payloads withissue_number