docs: #978 - [M3-P4] Update Documentation and Create M4 Follow-up Issue#982
Merged
Gorkowski merged 3 commits intouncscode:mainfrom Jan 30, 2026
Merged
Conversation
Add Jupytext workflow guidance to AGENTS.md and finalize M3 maintenance plan. AGENTS.md updates: - Add "Notebook Editing (Jupytext Paired Sync)" section with 5-step workflow - Update Last Updated date to 2026-01-30 M3 maintenance plan updates: - Change status from "Planning" to "Shipped" - Fill in issue numbers for all 4 phases (uncscode#975, uncscode#976, uncscode#977, uncscode#978) - Mark all phase tasks as complete - Add completion entry to Change Log - Reference M4 follow-up issue #175 in Future Work section Closes uncscode#978 ADW-ID: 2b58aa9a
Contributor
There was a problem hiding this comment.
Pull request overview
This PR completes Phase 4 (final phase) of the M3 Jupytext Pilot Migration by updating documentation to reflect the Jupytext paired sync workflow. It adds notebook editing guidance to AGENTS.md, marks the M3 maintenance plan as "Shipped", and documents the creation of M4 follow-up issue #979 for migrating the remaining notebooks.
Changes:
- Added "Notebook Editing (Jupytext Paired Sync)" section to
AGENTS.mdwith a 5-step workflow guide for LLM agents - Updated M3 maintenance plan status from "Planning" to "Shipped", filled in all phase issue numbers, and marked all tasks complete
- Added completion entry to the M3 plan's Change Log
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
AGENTS.md |
Added new notebook editing workflow section after "Quick Checks" and updated the "Last Updated" date to 2026-01-30 |
adw-docs/dev-plans/maintenance/M3-jupytext-notebook-sync.md |
Changed status to "Shipped", filled in issue numbers for all phases, marked all tasks complete, updated Change Log, and referenced M4 follow-up |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.
Target Branch:
mainFixes #978 | Workflow:
2b58aa9aSummary
Completes Phase 4 (final phase) of the M3 Jupytext Pilot Migration by updating documentation to reflect the Jupytext paired sync workflow. This adds notebook editing guidance to
AGENTS.md, marks the M3 maintenance plan as "Shipped", and creates the M4 follow-up issue (#979) for migrating the remaining ~35 notebooks.What Changed
Modified Components
AGENTS.md- Added new "Notebook Editing (Jupytext Paired Sync)" section after the "Quick Checks" section with a concise 5-step workflow guide and key points. Updated "Last Updated" date to 2026-01-30.adw-docs/dev-plans/maintenance/M3-jupytext-notebook-sync.md- Updated M3 maintenance plan:How It Works
This is a documentation-only change with no code modifications. The workflow documented in AGENTS.md follows this pattern:
Key workflow principles:
.pyfiles, not.ipynbdirectlyImplementation Notes
adw-docs/documentation_guide.md(lines 341-534)Testing
References
M3 Pilot Migration:
Follow-up Work: