Skip to content

feat(memory)!: bring the wiki up to date now with wiki update - #165

Merged
arthware-dev merged 2 commits into
mainfrom
feat/curator-cycles
Sep 27, 2026
Merged

arthware-dev merged 2 commits into
mainfrom
feat/curator-cycles

Conversation

@arthware-dev

@arthware-dev arthware-dev commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • stack memory wiki becomes a noun with verbs: wiki update waits until the latest filings are in the wiki, wiki update --all runs the nightly rebuild now, the page flags move under update, and a bare wiki lists the verbs. Both waits print each step and page as the curator writes it.
  • The curator stays the brain's only writer: the commands leave a trigger and wait for its record.
  • The command rules every stacklet command follows are written down in docs/stack-reference.md (CLI Commands), with pointers from the CLI header and the engineer guide.

BREAKING CHANGE: stack memory wiki no longer regenerates pages on its own. Use stack memory wiki update --all, or stack memory wiki update --home and the other page flags as before.

Base automatically changed from feat/drive-tool to main September 27, 2026 08:45
@arthware-dev
arthware-dev force-pushed the feat/curator-cycles branch 2 times, most recently from aec9efd to c663526 Compare September 27, 2026 11:10
The curator regenerates the pages a filing touched after a quiet window,
and rebuilds the whole wiki once a night. Checking that a filing reached
the wiki meant waiting for one or the other.

`stack memory wiki` is now a noun with verbs:

- `wiki update` asks the curator for the pages the latest filings
  touched and waits until they are written.
- `wiki update --all` asks it for the nightly rebuild now (diary,
  source reconcile, every page) and waits for it.
- `wiki update --home`, `--member`, `--topic`, `--topics` and
  `--dry-run` regenerate those pages directly, as the bare command did.
- `wiki clean` is unchanged; a bare `wiki` lists the verbs.

While waiting, the command prints each step and each page the curator
writes or skips. The curator stays the brain's only writer: the command
leaves a trigger and waits for the record the curator writes when done.

BREAKING CHANGE: `stack memory wiki` no longer regenerates pages on its
own. Use `stack memory wiki update --all` for every page, or
`stack memory wiki update --home` and the other page flags as before.
Every stacklet adds commands, and without written rules each one names
its commands and flags its own way. `docs/stack-reference.md` now lists
them under CLI Commands: name what the admin wants, not the component
or the schedule; nouns with verbs; one meaning per flag; apply by
default; wait with progress on background work; return a dict. The CLI
module header and the engineer guide point to them.
@arthware-dev arthware-dev changed the title feat(memory): run the curator's timed work now from the CLI feat(memory)!: bring the wiki up to date now with wiki update Sep 27, 2026
@arthware-dev
arthware-dev merged commit 8c0f38c into main Sep 27, 2026
2 checks passed
@arthware-dev
arthware-dev deleted the feat/curator-cycles branch October 7, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant