Simplify Submission: drop type, namespace format, flatten content - #37
Merged
maximiliansoelch merged 2 commits intoSep 23, 2026
Merged
Conversation
…eld across all submission-related structures
m-messer
marked this pull request as ready for review
August 11, 2026 10:32
neagualexa
approved these changes
Aug 21, 2026
maximiliansoelch
approved these changes
Sep 23, 2026
maximiliansoelch
left a comment
Contributor
There was a problem hiding this comment.
Thanks for simplifying this. Code changes look good 👍
type, namespace format, flatten content (#30)type, namespace format, flatten content
maximiliansoelch
deleted the
30-simplify-submission-type-format-content
branch
September 23, 2026 17:24
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
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
type(TEXT/CODE/MATH/MODEL/OTHER) fromSubmission,FeedbackTarget, andArtefactProfile;formatalone now determines category via a namespaced, pattern-constrained convention (<category>:<subtype>, e.g.text:plain,code:sympy,math:sympy) — this also resolves the prior ambiguity wheresympy/wolframexisted under bothCODEandMATH.content's type-mirroring wrapper key ({ text: ... },{ expression: ... },{ code: ... }) to a single genericvaluekey for every artefact type, with format-specific auxiliary fields (entryPoint,imports,notation,diagramType) as siblings.ArtefactType.ymlenum.evaluate.yml/chat.yml/evaluate-health.ymlexamples to match.Closes #30. As a side effect, also resolves #28 (no documented fallback key for non-conventional content —
valueis now the universal key).Test plan
npm run lintpasses (matches pre-existing warning baseline onmain)npm run bundlesucceeds🤖 Generated with Claude Code