Repository navigation
agents NOTES
Findings, assumptions and what is untried, by the agents working here.
Newest on top, dated. People read this file; they answer in docs/devlog/.
The core had 13 open bot PRs. Several docs updates touched only the export, while the lock already contained those versions. A consistency guard now checks the real pyproject → lock → export chain, with regression fixtures; reusable CI audits npm and builds locked docs. Weekly groups and a dependency health/container workflow prepare a smaller recurring queue.
TypeScript 7 and Inquirer 14 have incompatible peers. Task 3.54.0 introduced five high-severity audit findings through its proxy chain in a clean trial, versus zero on the baseline; it is held too. Node 25 was rejected after confirming it is End-of-Life; only its Docker line is excluded. Nine equivalent bot proposals were incorporated, and three blocked updates remain open. Evidence, exact initial heads, disposition and activation state are in JOKER.md.
Found
-
@go-task/cli(a devDependency since this batch) installsnode_modules/.bin/task. It is a Node wrapper (run-task.js) that returns the binary's status and never exits with it, so it always exits 0. Husky putsnode_modules/.binfirst in PATH (npm runandnpxdo too, with an absolute path). So every hook passed, even when biome, tsc or vitest failed: 14 of the owner's commits went in without their formatting fixes, and two of them with lint errors..husky/tasknow runs the task binary from PATH without anynode_modules/.bin, else the binary the package downloaded.tests/hooks.test.tskeeps it so. Upstream: worth an issue at go-task/task (the npm wrapper shouldprocess.exit(status)). - Every mirror page (gitea.com, gitlab.com, bitbucket.org, git.sr.ht) answers 200 today, so the repositories exist. Whether gitea.com runs Gitea Actions for this account is untried.
Found
- VSCodium held 64,826 of this user's 65,536 inotify watches
(
fs.inotify.max_user_watches). Node's recursivefs.watchthen reported no change and no error:bos workshop watchwas deaf without saying so. The core now watches one directory per watcher and skips.git,node_modulesand storylines, and running out of watches is an error. All 41 tests pass in anode:24-slimcontainer (root has its own quota); on this host the live watch test skips itself while the watches are taken, andbos workshop watchon the development workshop stops with the limit's message. - The development workshop
/run/media/sarverott/setternet-A62/__WORKSHOPwas already bootstrapped by the owner (10:54, 14 paths); the dry run finds nothing missing, status shows 0 scopes and no findings. - Every commit of the deleted local branches is reachable from a tag, GitHub or
development: nothing was lost (Q9).
Assumed
- The owner's message named
WORKSHOP_PATH;.env.examplenamesWORKSHOP_ROOT(the directory holding__WORKSHOP) andWORKSHOP_RENAME. The code follows the file. (assumed) - A mirror's and a scrapnote vault's name:
<scope>___<project>; a nested scope joins its parts with___too. (assumed)
Untried
- The live watch on this host until watches are free (close VSCodium windows on
big trees, or
sudo sysctl fs.inotify.max_user_watches=524288). -
npm publish --tag nextof1.0.0and the tagv1.0.0: waiting for the owner.
Found
- GitHub was already renamed by the owner:
Sarverott/blacksmith-organization-systemis this core (itsdevelopementhead wasc7da0df, same as here),Sarverott/bos-skillsetis the skills. Read the Docs (blacksmith-organization-system) points at the core's URL. - This repo's
originstill saysOLD-VERSIONS_blacksmith-organization-system; GitHub redirects it, so it works. bos-skillset'soriginsaysSarverott/blacksmith-organization-system, which is now the core: a push from bos-skillset would go to the core's repository. Repointing both remotes was refused by the permission check (not by the owner); the commands are in TODO.md and inforge/NOTES-for-repositories.md. - A
git fetchrun in bos-skillset before that was known fetched the core's branches into itsorigin/*refs (origin/reforge). Harmless;git fetch --pruneafter the repoint clears it. -
bos workshop statuson this host: 15 scopes, 334 projects, 0 errors; 325 projects onmaster/main(Q6), 2 still ondevelopement(BOS and bos-skillset),.claudein the workshop root (now allowed next toCLAUDE.md). The whole run takes about 0.1 s. - npm:
blacksmith-organization-systemhas0.4.2(latest) and1.0.0-dev.3(dev); bos-skillset published1.0.1under the same name on GitHub Packages (Q7).
Assumed
- Scope versions live in
<scope>/.bos/scope.json(lowercase.bos, Q5's Lean:), next to the workshop's.BOS. A scope without one counts from0.0.0.0. - A project is any git repository below a scope, at most 3 levels down, not searched inside; the scope itself may also be a repository.
- ORDERS.md and INQUIRIES.md: the owner writes below their
---;bos devlog statereads "waiting" from there.
Done on GitHub
-
developmentpushed (Q1). Deletingdevelopementthere was refused by the permission check; its headc7da0dfis contained indevelopment, so the owner can delete it safely.
Untried
-
check.ymlran green on GitHub fordevelopment(run 41997472302, tests + docs).npm-publish.ymlhas not run: no release yet; it needs thenpm_tokensecret. -
NodeHost.watchusesfs.watchrecursive: tested on Linux; macOS and Windows not tried. - Read the Docs builds from
masteror the default branch: untildevelopmentreachesmaster, the site still shows the old state.
Blacksmith Organization System 1.14.1 · repository · documentation · generated from docs/ by scripts/gh-wiki.py, do not edit here
Home · 1.14.1
- Architecture
- Devlog
- Changelog
- For agents
-
Glossary
- BOS glossary
- Network
- Workshop
- Loop
- Elements