Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
106 changes: 0 additions & 106 deletions .basedpyright/baseline.json
Original file line number Diff line number Diff line change
@@ -1,111 +1,5 @@
{
"files": {
"./bench/bench_file_hasher_cache.py": [
{
"code": "reportUnusedCallResult",
"range": {
"startColumn": 12,
"endColumn": 26,
"lineCount": 1
}
},
{
"code": "reportUnknownParameterType",
"range": {
"startColumn": 14,
"endColumn": 16,
"lineCount": 1
}
},
{
"code": "reportMissingParameterType",
"range": {
"startColumn": 14,
"endColumn": 16,
"lineCount": 1
}
},
{
"code": "reportUnknownParameterType",
"range": {
"startColumn": 19,
"endColumn": 23,
"lineCount": 1
}
},
{
"code": "reportMissingParameterType",
"range": {
"startColumn": 19,
"endColumn": 23,
"lineCount": 1
}
},
{
"code": "reportUnknownVariableType",
"range": {
"startColumn": 4,
"endColumn": 10,
"lineCount": 1
}
},
{
"code": "reportUnknownVariableType",
"range": {
"startColumn": 11,
"endColumn": 26,
"lineCount": 1
}
},
{
"code": "reportUnknownMemberType",
"range": {
"startColumn": 37,
"endColumn": 58,
"lineCount": 1
}
},
{
"code": "reportUnknownMemberType",
"range": {
"startColumn": 33,
"endColumn": 56,
"lineCount": 1
}
},
{
"code": "reportUnknownMemberType",
"range": {
"startColumn": 29,
"endColumn": 52,
"lineCount": 1
}
},
{
"code": "reportUnknownMemberType",
"range": {
"startColumn": 12,
"endColumn": 28,
"lineCount": 1
}
},
{
"code": "reportUnknownArgumentType",
"range": {
"startColumn": 22,
"endColumn": 31,
"lineCount": 1
}
},
{
"code": "reportUnknownArgumentType",
"range": {
"startColumn": 39,
"endColumn": 48,
"lineCount": 1
}
}
],
"./examples/async_vs_sync_pipeline.py": [
{
"code": "reportUnusedCallResult",
Expand Down
40 changes: 0 additions & 40 deletions .devcontainer/Dockerfile

This file was deleted.

39 changes: 0 additions & 39 deletions .devcontainer/devcontainer.json

This file was deleted.

12 changes: 9 additions & 3 deletions .github/workflows/run-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ jobs:
runs-on: ubuntu-latest
# Only run on push/manual trigger — not on PRs — to avoid consuming SpiralDB
# resources on every review cycle.
# Requires SPIRAL_WORKLOAD_ID secret; fails loudly if absent so missing
# credentials don't silently drop coverage. Runs only on the development repository:
# Requires the SPIRAL_WORKLOAD_ID secret and the SPIRAL_PROJECT_ID repository variable;
# fails loudly if either is absent so missing settings don't silently drop coverage. Runs only on the development repository:
# the public repository has no SpiralDB credentials, so the job is skipped there (ITL-1007).
if: >-
github.repository == 'metamorphic-labs/orcapod-python'
Expand All @@ -64,7 +64,7 @@ jobs:
env:
SPIRAL_WORKLOAD_ID: ${{ secrets.SPIRAL_WORKLOAD_ID }}
SPIRAL_INTEGRATION_TESTS: "1"
SPIRAL_PROJECT_ID: ${{ vars.SPIRAL_PROJECT_ID || 'test-orcapod-362211' }}
SPIRAL_PROJECT_ID: ${{ vars.SPIRAL_PROJECT_ID }}
SPIRAL_SERVER_URL: https://api.spiraldb.dev # plain http no longer answers (ITL-1008); the repository variable of this name is not read

steps:
Expand All @@ -74,6 +74,12 @@ jobs:
echo "::error::SPIRAL_WORKLOAD_ID secret is not set. SpiralDB integration tests cannot run. Configure the secret or investigate why it is missing."
exit 1

- name: Check for SPIRAL_PROJECT_ID
if: env.SPIRAL_PROJECT_ID == ''
run: |
echo "::error::SPIRAL_PROJECT_ID repository variable is not set. SpiralDB integration tests cannot run. Configure the variable or investigate why it is missing."
exit 1

- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
fetch-depth: 0 # required: hatch-vcs needs full tag history
Expand Down
10 changes: 0 additions & 10 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,11 +1,5 @@
# NFS cache files
.nfs*
# Ignore data files in notebooks folder
notebooks/**/*.json
notebooks/**/*.yaml
notebooks/**/*.parquet
notebooks/**/*.pkl
notebooks/**/*.db

# Ignore npy and npz data files by default
*.np[yz]
Expand All @@ -25,10 +19,6 @@ notebooks/**/*.db
# Ignore profiler output
*.prof

# Ignore any notebook that starts with an underscore or test
notebooks/**/_*.ipynb
notebooks/**/test*.ipynb

# Ignore vscode settings
.vscode/

Expand Down
24 changes: 14 additions & 10 deletions .zed/rules
Original file line number Diff line number Diff line change
Expand Up @@ -15,31 +15,32 @@ When adding or changing any instruction, update BOTH:

## Design issues log

design_issues/ at the project root is the canonical log of known design problems, bugs, and
code quality issues: one file per entry (developer, November 11, 2026; ITL-968). There is no
DESIGN_ISSUES.md; never bring it back, and never put two entries in one file.
docs/dev/design_issues/ is the canonical log of known design problems, bugs, and code
quality issues: one file per entry (developer, November 11, 2026; ITL-968). There is no
DESIGN_ISSUES.md and no top-level design_issues/ (moved in ITL-1169; --check refuses both);
never bring either back, and never put two entries in one file.

- An entry is the file design_issues/<LINEAR-ISSUE-ID>-<ENTRY-ID>.md (e.g.
design_issues/ITL-955-GB1.md). Its first line is the "## <area heading>" it belongs
- An entry is the file docs/dev/design_issues/<LINEAR-ISSUE-ID>-<ENTRY-ID>.md (e.g.
docs/dev/design_issues/ITL-955-GB1.md). Its first line is the "## <area heading>" it belongs
under, then a blank line, "### <ENTRY-ID> — <title>", the **Status:** ("open",
"in progress" or "resolved"), **Severity:** and **Issue:** lines, a blank line and the
body.
- Read the log with `uv run python scripts/design_issues.py` (index by area; --status open
filters; --full prints every entry). Find one entry by id: ls design_issues/*-GB1.md.
filters; --full prints every entry). Find one entry by id: ls docs/dev/design_issues/*-GB1.md.
- Check the files with `uv run python scripts/design_issues.py --check`
(tests/test_design_issues.py runs it in CI).
- design_issues/README.md is the full statement of the convention, with the severity
- docs/dev/design_issues/README.md is the full statement of the convention, with the severity
guide.

When fixing a bug or addressing a design problem:
1. Check design_issues/ first — if a matching entry exists, edit its file: update its
1. Check docs/dev/design_issues/ first — if a matching entry exists, edit its file: update its
status to "in progress" while working and "resolved" once done, adding a brief Fix:
note.
2. If no matching entry exists, ask the user whether it should be added before proceeding.
If yes, add it as a new file (status "open" or "in progress" as appropriate).

When discovering a new issue that won't be fixed immediately, ask the user whether it should be
logged in design_issues/ before adding it.
logged in docs/dev/design_issues/ before adding it.

## Superpowers artifacts

Expand Down Expand Up @@ -80,6 +81,9 @@ other ReST cross-reference roles. Use plain ``backtick`` notation to refer to na

## Documentation samples

docs/dev/ (the design issues log and the design specification) is developer material, kept
out of the published site (exclude_docs in mkdocs.yml) and out of the sample test.

Every fenced python block in README.md, docs/index.md, docs/getting-started.md,
docs/troubleshooting.md, docs/concepts/, docs/reference/ and docs/tutorial/ is executed by
tests/test_docs/test_doc_samples.py, and tests/test_docs/test_mkdocs_build.py runs
Expand Down Expand Up @@ -562,7 +566,7 @@ tests/

## Architecture overview

See orcapod-design.md at the project root for the full design specification.
See docs/dev/orcapod-design.md for the full design specification.

### Core data flow

Expand Down
4 changes: 2 additions & 2 deletions AGENT_COORDINATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ recorded.
decisions the developer has already made. An issue that needs a design decision is not
ready to dispatch until the decision is made, or the spec says to stop and ask.
5. **Check for overlap.** Two workers must not edit the same file region. Where overlap is
unavoidable (`CLAUDE.md`, a shared operator base class, one `design_issues/` entry),
unavoidable (`CLAUDE.md`, a shared operator base class, one `docs/dev/design_issues/` entry),
name the overlap in both specs and say who owns the shared part. Sequence the issues
instead if the overlap is substantial.
6. **Move the issues to In Progress** in Linear once the developer approves the wave.
Expand Down Expand Up @@ -104,7 +104,7 @@ developer.

- **Decision routing.** Send every design or scope question to the coordinator with the
orchestration `ask` command and wait. Never open a local question prompt. Wherever
`CLAUDE.md` says "ask the user" or "wait for user approval" (adding a `design_issues/`
`CLAUDE.md` says "ask the user" or "wait for user approval" (adding a `docs/dev/design_issues/`
entry, creating a Linear issue, approving a PR-review revision plan), that means `ask`.
If the developer types into the worker's terminal directly, that instruction wins; tell
the coordinator with an escalation.
Expand Down
24 changes: 14 additions & 10 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,31 +19,32 @@ When adding or changing any instruction, update BOTH:

## Design issues log

`design_issues/` at the project root is the canonical log of known design problems, bugs, and
code quality issues: one file per entry (developer, November 11, 2026; ITL-968). There is no
`DESIGN_ISSUES.md`; never bring it back, and never put two entries in one file.
`docs/dev/design_issues/` is the canonical log of known design problems, bugs, and code
quality issues: one file per entry (developer, November 11, 2026; ITL-968). There is no
`DESIGN_ISSUES.md` and no top-level `design_issues/` (moved in ITL-1169; `--check` refuses both);
never bring either back, and never put two entries in one file.

- An entry is the file `design_issues/<LINEAR-ISSUE-ID>-<ENTRY-ID>.md` (e.g.
`design_issues/ITL-955-GB1.md`). Its first line is the `## <area heading>` it belongs
- An entry is the file `docs/dev/design_issues/<LINEAR-ISSUE-ID>-<ENTRY-ID>.md` (e.g.
`docs/dev/design_issues/ITL-955-GB1.md`). Its first line is the `## <area heading>` it belongs
under, then a blank line, `### <ENTRY-ID> — <title>`, the `**Status:**` (`open`,
`in progress` or `resolved`), `**Severity:**` and `**Issue:**` lines, a blank line and the
body.
- Read the log with `uv run python scripts/design_issues.py` (index by area; `--status open`
filters; `--full` prints every entry). Find one entry by id: `ls design_issues/*-GB1.md`.
filters; `--full` prints every entry). Find one entry by id: `ls docs/dev/design_issues/*-GB1.md`.
- Check the files with `uv run python scripts/design_issues.py --check`
(`tests/test_design_issues.py` runs it in CI).
- `design_issues/README.md` is the full statement of the convention, with the severity
- `docs/dev/design_issues/README.md` is the full statement of the convention, with the severity
guide.

When fixing a bug or addressing a design problem:
1. Check `design_issues/` first — if a matching entry exists, edit its file: update its
1. Check `docs/dev/design_issues/` first — if a matching entry exists, edit its file: update its
status to `in progress` while working and `resolved` once done, adding a brief **Fix:**
note.
2. If no matching entry exists, ask the user whether it should be added before proceeding.
If yes, add it as a new file (status `open` or `in progress` as appropriate).

When discovering a new issue that won't be fixed immediately, ask the user whether it should be
logged in `design_issues/` before adding it.
logged in `docs/dev/design_issues/` before adding it.

## Superpowers artifacts

Expand Down Expand Up @@ -84,6 +85,9 @@ to refer to names (e.g. ``PollingSource``, ``iter_data``, ``CursorInvalidatedErr

## Documentation samples

`docs/dev/` (the design issues log and the design specification) is developer material, kept
out of the published site (`exclude_docs` in `mkdocs.yml`) and out of the sample test.

Every fenced `python` block in `README.md`, `docs/index.md`, `docs/getting-started.md`,
`docs/troubleshooting.md`, `docs/concepts/`, `docs/reference/` and `docs/tutorial/` is executed
by `tests/test_docs/test_doc_samples.py`, and `tests/test_docs/test_mkdocs_build.py` runs
Expand Down Expand Up @@ -575,7 +579,7 @@ tests/

## Architecture overview

See `orcapod-design.md` at the project root for the full design specification.
See `docs/dev/orcapod-design.md` for the full design specification.

### Core data flow

Expand Down
2 changes: 1 addition & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -275,5 +275,5 @@ does not block or fail the release (no publish job depends on them). They call
Because the Release workflow runs on `nauticalab`, these jobs do not run for a release at all
today; completing the Linear release is a manual step until the developer decides otherwise
(the issue ITL-1007 notes this "needs more thought"). Setup on `metamorphic-labs`: the
`LINEAR_ACCESS_KEY` repo secret (the key `metamorphic-brain/axon` uses) and a Linear release
`LINEAR_ACCESS_KEY` repo secret (the organisation's Linear access key) and a Linear release
configured in the workspace.
Loading
Loading