Repository navigation
Add Serena project config and onboarding memories - #4
Merged
Merged
Conversation
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.
Adds Serena scaffolding so an AI coding agent working in this
repo starts from the project's real invariants instead of rediscovering them (or guessing) each
session.
What's here
.serena/project.yml— project config: languages, timeouts, tool settings..serena/memories/— eight onboarding notes, organised as a reference graph fromcore.md:tech_stack,suggested_commands,conventions,task_completion, plus per-moduleagents/coreandgateway/core..gitignore— ignore/.roborev/snapshots.What the memories actually say
They deliberately point at
CONTRIBUTING.md§ "Things that will bite you" and.roborev.tomlrather than transcribing them, and spend their words on things written downnowhere, each verified against the code rather than inferred:
LocalStorage's root is the repo checkout itself, which is whytests/conftest.pymutates thealready-imported
storagesingleton instead of re-creating it — and why code that resolvespaths from anything but
storage.rootescapes the fixture and writes into the working tree.mcp/registry.pysetsMCP_CONFIG_DIR = Path.cwd() / "configs"at module scope, sopytestmust run from the repo root (the same reason
ci.ymlforbidsworking-directory).pytestpicks up--covfromaddopts; CI runs-q --no-cov.is_llm_graph_source()merges admin-added CKAN portals at runtime, so the set of LLM-graphsource ids cannot be found by grepping.
messagesis the only reducer-backedGraphStatekey — every other list key islast-write-wins, so a node returning a partial
execution_tracesilently drops earlier entries.UP042ruff ignore is load-bearing: rewriting(str, Enum)toStrEnumwould change howthese enums render in prompts, notebooks and logs.
Scope
Documentation and config only — no source file is touched, and the three commits add 432 lines
across 11 files with no deletions.
.serena/cacheand.serena/project.local.ymlare excluded by.serena/.gitignore;.serena/logsis already covered by the rootlogs/rule.Worth a deliberate call on whether agent scaffolding belongs in the repo at all — it's easy to
drop if the answer is no.
🤖 Generated with Claude Code