chore: post-migration cleanup — drop planning artifacts, move to maintenance mode#255
Draft
marc0olo wants to merge 1 commit into
Draft
chore: post-migration cleanup — drop planning artifacts, move to maintenance mode#255marc0olo wants to merge 1 commit into
marc0olo wants to merge 1 commit into
Conversation
…aintenance mode Migration is complete. All Learn Hub articles migrated; portal submodule removed; all content PRs merged. This commit closes issue #224 and brings AGENTS.md into maintenance mode. Changes: - Remove .docs-plan/decisions.md (decisions are baked into the codebase; new structural choices go in PR descriptions per issue #224 guidance) - Remove .docs-plan/migration-plan.md, synthesis.md, developer-journey.md, icp-cli-examples-inventory.md, jssdk-skills-mapping.md (migration-phase artifacts with no ongoing value; each was >170 lines loaded on every relevant task, burning context tokens for nothing) - Update AGENTS.md: remove decisions.md/migration-plan references, simplify Quick Orientation (7 steps → 4), replace "record in decisions.md" with "document in PR description", replace "not in migration plan" guard with "needs a GitHub Issue", remove stale "Previous work" section - Update .docs-plan/README.md: strip migration-era table; keep only the two evergreen workflow files (content-authoring.md, review-guidelines.md) - Update .docs-plan/content-authoring.md: remove decisions.md pointer and dead "Beads status" submit step Closes #224
|
🤖 Here's your preview: https://k7oic-piaaa-aaaam-ai7uq-cai.icp0.io |
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
.docs-plan/files (decisions.md,migration-plan.md,synthesis.md,developer-journey.md,icp-cli-examples-inventory.md,jssdk-skills-mapping.md) — these were scaffolding for the initial content build; the structure is now the recordAGENTS.mdfor maintenance mode: simplifies Quick Orientation (7 steps to 4), removes alldecisions.mdandmigration-plan.mdreferences, replaces "record in decisions.md" with "document in PR description", replaces "not in migration plan" guard with "needs a GitHub Issue", removes stale "Previous work" section.docs-plan/README.mdand.docs-plan/content-authoring.mdto remove dead references (Beads submit step, decisions.md pointer)Closes #224
Token efficiency rationale
The 6 deleted files totalled ~2,100 lines. Agents were instructed to load
decisions.md(419 lines) on every structural task. Removing that instruction plus the file cuts ~420 lines of context per structural session — roughly a 10% reduction in per-session context cost for the most common agent workflows.Sync recommendation
hand-written— governance/workflow files, no upstream equivalent