Repository navigation
chore: move superpowers/ to docs/dev (ITL-1169) - #411
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ITL-1169) The hash audit example that docs/reference/hashing.md runs moves to scripts/. Plans go in the Linear issue or the pull request description, and the per-release checklist in the release pull request's description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
plan.md, function-execution-improvements-plan.md, TESTING_PLAN.md, design/, and the agent plans and specs under docs/metamorphic, docs/plans, docs/specs and docs/design. Nothing links to them, and mkdocs would publish the ones under docs/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-1169) The notebooks under notebooks/old_tutorials target an earlier API and were kept for reference only; the tutorial lives in docs/tutorial. The example scripts do not read examples/dataset1 or examples/dataset2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t (ITL-1169) src/orcapod/databases/file_utils.py and tests/test_hashing/test_string_cacher/test_redis_cacher.py hold no code: every line is a comment, and nothing imports them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/migrate_design_issues.py split DESIGN_ISSUES.md into one file per entry (ITL-968); that log no longer exists. Its tests go with it; the tests of scripts/design_issues.py stay. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…1169) The SpiralDB integration job takes the project from the SPIRAL_PROJECT_ID repository variable only, and fails loudly when it is unset, as it does for the workload secret. The integration tests skip unless SPIRAL_PROJECT_ID is set. RELEASING.md no longer names another repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s/dev (ITL-1169) design_issues/ becomes docs/dev/design_issues/ and orcapod-design.md becomes docs/dev/orcapod-design.md, so the repository root holds fewer entries. docs/dev is developer material: mkdocs excludes it from the site, and the documentation sample test does not run it. scripts/design_issues.py reads the new location and fails, in every mode, while an entry file is left at the old top-level design_issues/, naming the new path, so a branch that adds an entry at the old path is caught when it merges. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ository-cleanup-before-the-v030-tag # Conflicts: # docs/dev/design_issues/ITL-1165-RN1.md
The superpowers/ removal moves to its own pull request, so that this one stays under CodeRabbit's file limit. This reverts commit c7e5b2c. The docs/dev sentence that follows the documentation rule stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ITL-1169) Re-applies c7e5b2c, which the cleanup pull request reverted to stay under CodeRabbit's file limit. The hash audit example that docs/reference/hashing.md runs moves to scripts/. Plans go in the Linear issue or the pull request description, and the per-release checklist in the release pull request's description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ITL-1169 Repository cleanup before the v0.3.0 tag: remove unused and stale files
Overviewv0.3.0 is the first release whose The developer has marked the Goals & Success Criteria
Scope & BoundariesIn scope:
Out of scope:
Dependencies & Risks
|
|
CodeRabbit review record: CodeRabbit cannot review this pull request. It changes about 480 files, over CodeRabbit's 300-file limit (the same limit skipped #410 at 713 files). The CodeRabbit CLI was not run (developer decision, budget). Apart from deletions, the change is the nine items listed in the description. The coordinator verifies them, and CI covers them. Head: 81b21c0. Posted by a Claude Code agent on behalf of @eywalker. |
|
Important Review skippedToo many files! This PR contains 491 files, which is 191 over the limit of 300. To get a review, reduce the PR to 300 files or fewer by splitting it into smaller PRs or changing its base branch. Usage-priced reviews support at most 300 files.
|
…ing them (ITL-1169) Developer decision: development documents are kept, under docs/dev. The plans and specs that were under docs/metamorphic, docs/plans, docs/specs and docs/design move to docs/dev/plans and docs/dev/specs, text unchanged. mkdocs excludes docs/dev from the site. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…g' into eywalker/itl-1169-remove-superpowers
…ing them (ITL-1169) Developer decision: development documents are kept. superpowers/plans, superpowers/specs and superpowers/scripts move to docs/dev/plans, docs/dev/specs and docs/dev/scripts, text unchanged; hash_audit_example.py stays in scripts/. CLAUDE.md and .zed/rules get a 'Development documents' section; AGENT_COORDINATION.md and RELEASING.md point to docs/dev/plans; the docstrings and design issues entries that cite those files use the new paths; the .gitignore allow-list follows the move. scripts/design_issues.py --check now also refuses a file in a top-level superpowers/, naming its place under docs/dev/, because open pull requests still add files there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
CodeRabbit review record for head fc2bc98: this pull request is now a move to Posted by a Claude Code agent on behalf of @eywalker. |
…ove-superpowers # Conflicts: # .zed/rules # CLAUDE.md # scripts/design_issues.py # tests/test_design_issues.py
|
CodeRabbit review record for head fa26e22 (merge of Posted by a Claude Code agent on behalf of @eywalker. |
…ial tags slice (ITL-1023) - #410/#411: the slice's design issues (ITL-1017-RT2, ITL-1023-RT1) and its four plans move to docs/dev/design_issues/ and docs/dev/plans/. - #409 (map_columns, strict MapTags/MapData): main's operators with the slice's referential behaviour re-applied. MapTags takes strict, then tag_only; tag_only enters the identity only when set. StreamBase.map_tags takes tag_only beside strict and the keyword renames. MapColumns does not handle referential tags yet and refuses them (ITL-1022), as listed in the docs and the changelog fragment. After GroupBy, map_tags on a referential non-key now raises and points to map_data; the docs say so. - #408 (connector databases refuse what they cannot store): a function node's up-front check (require_storable_tables) also asks for the referential marker first, so a referential job on a SQLite/PostgreSQL database is still refused with the ITL-1019 message before anything runs. Golden files identical to main's. Refs ITL-1023, ITL-1019, ITL-1160, ITL-1162 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Summary
This moves the development documents from the top-level
superpowers/todocs/dev/. The developer keeps development documents in the repository, all underdocs/dev/, which mkdocs excludes from the published site.superpowers/plans,superpowers/specsandsuperpowers/scriptsbecomedocs/dev/plans,docs/dev/specsanddocs/dev/scripts(git mv, text unchanged). The one exception ishash_audit_example.py, which goes toscripts/becausedocs/reference/hashing.mdruns it.#410 is merged and
mainis merged in here, so the diff againstmainis exactly this PR's change: 502 files. That is 472 unchanged renames, 1 rename with its usage line updated, and the 29 modified files below.CodeRabbit cannot review this PR because it exceeds the 300-file limit. The developer agreed that a pure move needs no CodeRabbit review; the coordinator verifies the changes below.
Every change that is not an unchanged rename
superpowers/scripts/hash_audit_example.pymoves toscripts/hash_audit_example.py. Its usage line changes to the new path, and the script still runs.docs/reference/hashing.md: the command that regenerates the worked example now runsscripts/hash_audit_example.py..basedpyright/baseline.json: the script's entry is re-keyed to./scripts/hash_audit_example.pywith identical diagnostics. No other entry changes, because no other moved.pyfile had one.CLAUDE.mdand.zed/rules: the "Superpowers artifacts" section becomes "Development documents". Specs go indocs/dev/specs/, plans indocs/dev/plans/, and their scripts indocs/dev/scripts/. They never go in the published docs or at the top level, anddocs/dev/stays out of the site and the sample test. The sentence under "Documentation samples" now says thatdocs/outsidedocs/dev/is library documentation.AGENT_COORDINATION.md: save the plan underdocs/dev/plans/before changing code; the PR may summarise it.RELEASING.md: per-release checklists live indocs/dev/plans/..gitignore: thesuperpowers/allow-list becomes adocs/dev/allow-list (specs,plans,scripts,design_issues,orcapod-design.md).src/orcapod/pipeline/dag.py,tests/test_arrays/test_array_value_format.pyandtests/test_pipeline/test_node_view_review_fixes.py: the docstrings that cite those documents use the new paths. They are docstrings only and enter no hash.docs/dev/design_issues/(19 references):superpowers/{specs,plans,scripts}/paths becomedocs/dev/{specs,plans,scripts}/, and every rewritten path exists. Two entries that mentionsuperpowers/as a directory in a historical count are unchanged.scripts/design_issues.py: besides the old log locations that chore: repository cleanup before the v0.3.0 tag (ITL-1169) #410 refuses (a rootDESIGN_ISSUES.mdand a top-leveldesign_issues/),--check, and every other mode, also refuses a file in a top-levelsuperpowers/. The message names its place underdocs/dev/and thegit mvthat puts it there, because open pull requests still add files at the old path. There is a new test intests/test_design_issues.py.Test plan
tests/test_docs(doc samples andmkdocs build --strict;docs/devis excluded),tests/test_design_issues.py,tests/test_changelog_fragments.pyand the two changed test files: 375 passed.scripts/hash_audit_example.pyruns.basedpyrightexits 0 (0 errors).ruff check .andruff format --check .are clean, includingdocs/dev/**/*.py.Linear
Fixes ITL-1169
🤖 Generated with Claude Code