Commit History
-
research: Composer 2.5 data-gen + targeted-textual-feedback deep-research wave
Phase-3 of the deep-work-loop bringing Composer 2.5's dataset-generation and targeted-RL-with-textual-feedback methods into the framework. 5 new research docs (130KB), all with primary-source citations: - 06-feature-deletion-datagen.md: Feature Deletion env design (online pass-rate difficulty gate, reward-hacking safeguards, 5 OSS substrates w/ HF ids + licenses, deletion mechanics, FeatureDeletionEnv + TRL reward_fn adapter). - 07-sdpo-hint-generator.md: layered HintGenerator (template -> raw-error -> LLM-judge -> introspection -> learned -> SDPO sibling-bootstrap), actual template strings, judge prompt, slots into existing CollatorConfig hook. - 08-sdpo-grpo-integration.md: ComposerGRPOTrainer(GRPOTrainer) design adding SDPO KL at error turns on top of Dr. GRPO; PRIME-RL recipe blocked (log-probs only), TRL subclass is the host; CPU smoke plan. - 09-composer-blog-delta-2026.md: blog re-extraction delta; found the Composer 2 arXiv tech report; SDPO successful-rollout-as…6049d00
-
Integrate Cursor blog directly + audit research note + add SDPO/OPSD link
baladithyabUser flagged a real gap: I had dispatched a subagent to research Composer 2.5 but never personally read the Cursor blog. Audit findings: 1. The targeted-textual-feedback method = published SDPO (Hubotter et al., arXiv:2601.20802, ICLR 2026 Workshop) + OPSD (Zhao et al., arXiv:2601.18734, code at github.com/siyan-zhao/OPSD, MIT). Cursor cites these directly in footnote 1 of the blog. The subagent's research note never mentioned them. This is huge: there's published, MIT-licensed code for Composer's secret sauce. 2. Several claims in research/01-composer-2.5.md are NOT in the Cursor blog and were extrapolated from secondary sources ("85% post-training compute", "Anyrun" environment name, specific benchmark scores, "PPO or GRPO variant"). Likely correct via community consensus but not blog-verified. 3. Composer hint-distill (single model, hint-conditioned context) and trace-replay-distill (N external teachers) are TWO genuinely different mechanisms, not compe…1cede23 -
Initial commit: Composer 2.5 Replication Framework — research synthesis
Methodology repo (model type) for an open replication of Cursor's Composer 2.5 (post-trained Kimi K2.5) on any HuggingFace base model. Contents: - README.md (HF model card with frontmatter) - framework/composer-replication-framework.md (master synthesis, 18KB) - research/ (5 deep-dives by 5 different LLM families, ~107KB total) - 01-composer-2.5.md (Gemini 3.1 Pro) - 02-diloco-family.md (DeepSeek V4 Pro) - 03-monarch-torchforge-openenv.md (GPT-5) - 04-verl-trl.md (Sonnet 4.6) - 05-trace-replay-distillation.md (Kimi K2-Thinking) - docs/METHODOLOGY.md (how the synthesis was produced) - docs/HF_REPO_LAYOUT.md (planned multi-repo split) - LICENSE (MIT) Status: pre-spike. No code, no weights, no datasets yet. Trained variants and trace datasets will live in separate repos linked via HF Collection.7165832