48 KiB
phase, plan, type, wave, depends_on, files_modified, autonomous, requirements, estimate, must_haves
| phase | plan | type | wave | depends_on | files_modified | autonomous | requirements | estimate | must_haves | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 20-demo-instance-with-every-shared-plugin | 01 | execute | 1 |
|
false |
|
|
|
Phase Goal
ROADMAP Goal (not in user-story format; no story is invented here, see the planning return): sm-demo-app runs every shared Golem15 plugin collected so far in one binary, and its public Nuxt site shows them working: chat and channels with realtime, video calls, presentations, quizzes, journal, FAQ, subscriptions and the rest. Phase 19.4.1 deployed the demo early; this phase adds the chat family to that live instance.
This plan's slice (plan 1 of 6, wave 1, per D-20): the shared plugin release the demo needs before it can require the chat family by tag. Fast-forward the stale sibling checkouts, add the generic pre-save seams to chat and forum (D-18), create sm-moderation-plugin (D-17), fix the go.mod files that break module mode, and, after the user's go-ahead, push and tag all eight repositories.
Decisions taken in this plan (Claude's discretion, recorded)
- Seam shape (D-18 discretion): a festival "-ing" event fired before the write transaction, mirroring
user.Deleting/user.Deactivatingin sm-user-plugin. chat getsevents.MessageSaving, forum a neweventspackage withevents.PostSaving. A listener refuses by returning the plugin's owncontracts.Rejection{Field, Message}. Each plugin declares its own type, so forum does not import chat and neither imports moderation. The API mapserrors.As(err, &rej)to the existing 422 envelope. Rationale:festival.Bus.Firealready returns the joined listener errors, chat already holdss.bus, forum holds an unusedBusfield, and no service gains a new registration method. RESEARCH Pattern 2. - Event names:
MessageSavingEventName = "golem15.chat.message.saving"andPostSavingEventName = "golem15.forum.post.saving". They are Go-only seams with no PHP counterpart; the doc comments say so. - Op values: chat
OpCreate = "create"andOpUpdate = "update"; forumOpThread = "thread",OpReply = "reply"andOpUpdate = "update". - Moderation lists: two textareas, one entry per line; an
enabledswitch defaults to true; at most 500 entries of at most 200 characters per list (validated inBeforeValidate). The filter reads the singleton row on everyCheckand recompiles its matchers only when the stored text changed. RE2's\bis ASCII-only, so word boundaries are built from[^\p{L}\p{N}_]to cover Polish letters. - Violation message:
Violation{Kind, Match, Message}. Message comes from the plugin's lang files (golem15.moderation::lang.violation.wordand.link, EN and PL) in the localetowel.Locale(ctx)carries, resolved through the framework's phrasebook. Without a locale it is English. The chat-family APIs answer in English today, so English is an acceptable fallback. - Dependants require existing tags: chatvideo, herald and userfriends require
sm-chat-plugin v0.1.3(the newest tag before this plan),sm-user-plugin v0.1.13andsummercms v0.5.1, the set RESEARCH compiled. That keeps their module-mode check independent of the new chat tag; minimal version selection gives the demo chat v0.1.4. - Repository creation: with the go-ahead, Claude creates
golem15/sm-moderation-pluginon git.golem15.com withteawhentea login listshows a git.golem15.com login, using the same visibility assm-sitemap-plugin. Otherwise the user creates it. - spec-less probe fallback skipped: phase has no requirement IDs to probe (visible skip).
Artifacts this phase produces (this plan)
- sm-chat-plugin (v0.1.4):
events.MessageSaving,events.MessageSavingEventName,events.OpCreate,events.OpUpdate,contracts.Rejection(Error()), the 422 mapping inwriteChatError, smoke testTestMessageSavingTracer(saving_smoke_test.go), a README changelog entry v0.1.4. - sm-forum-plugin (v0.1.0): package
events(PostSaving,PostSavingEventName,OpThread,OpReply,OpUpdate),contracts.Rejection, the 422 mapping inwriteForumError, smoke testTestPostSavingTracer. - sm-moderation-plugin (new repo, v0.1.0): plugin
golem15.moderation, packagemoderation,classes.Filter,classes.NewFilter(db *gorm.DB) *Filter,(*Filter).Check(ctx context.Context, text string) (*Violation, error),classes.Match(words, links []string, text string) *Violation,classes.ParseList(text string) []string,classes.Violation{Kind, Match, Message},classes.KindWord,classes.KindLink, tablegolem15_moderation_settings(migration202610280001_create_golem15_moderation_settings), settings itemmoderation_settings, permissiongolem15.moderation.manage_settings, config keysgolem15.moderation.max_entriesandgolem15.moderation.max_entry_length, smoke testTestFilterSmoke. - go.mod fixes in sm-chatvideo-plugin, sm-herald-plugin and sm-userfriends-plugin.
- Tags: chat v0.1.4; chatchannels, chatbots, chatvideo, forum, herald, userfriends and moderation v0.1.0 (numbers read from the remote at release time).
- Full unit tests come in plan 06 (project rule).
Purpose: SC-1 needs sm-demo-app to build from tagged modules (19.4.1 D-03, TestGoModRequiresTags, scripts/check-pins.sh). D-17 and D-18 need the seams and the filter before plan 02 wires them. D-20 makes this plan 01 of six and supersedes D-19's earlier split.
Output: commits and, after the go-ahead, pushes and tags in eight plugin repositories. No change in sm-demo-app, vue-demo-app or summercms.go code.
<execution_context>
@/.claude/msd-core/workflows/execute-plan.md
@/.claude/msd-core/templates/summary.md
</execution_context>
Repos (siblings of summercms.go): ../sm-chat-plugin, ../sm-chatchannels-plugin, ../sm-chatbots-plugin (all three behind origin: fast-forward first), ../sm-chatvideo-plugin, ../sm-forum-plugin, ../sm-herald-plugin, ../sm-userfriends-plugin, and the new ../sm-moderation-plugin. Read-only references: ../sm-bm-app/plugins/golem15/{chat,chatchannels,chatbots} (the origin-main trees, for reading only), ../sm-sitemap-plugin (plugin and settings analog), ../sm-demo-app/plugins/golem15/user/classes/events.go (the "-ing" event analog).
Rules: no co-author tags in commits (user instruction overrides any attribution default); stage files by explicit path, never git add -A; one logical change per commit; nothing pushed, created or tagged before Task 5. Verify commands run from the framework root and address siblings with go -C ../<repo>. Plugin repos with a tracked go.work resolve their siblings through it (the seam-carrying ../sm-chat-plugin included). If the Docker socket is denied, run the Docker tests through sudo -u golem (CLAUDE.md).
- Fast-forward every sibling first (RESEARCH Pitfall 1): for chat, chatchannels, chatbots, chatvideo, forum, herald and userfriends run
git -C ../<repo> pull --ff-onlyand confirmgit -C ../<repo> rev-parse HEADequals the hashgit -C ../<repo> ls-remote origin refs/heads/mainprints (use the default branch each repo tracks). Record both hashes per repo for the SUMMARY. A non-fast-forward stops the task. - events/events.go: keep the three existing events untouched. Add
MessageSavingEventName = "golem15.chat.message.saving"on its own line and aMessageSavingstruct withConversationID,ActorIDandMessageID uint(MessageID is 0 on create),RootID *uint,Content stringandOp string, plus the constantsOpCreate = "create"andOpUpdate = "update". MessageSaving carries no Tx because it fires before the transaction. Rewrite the package doc: the three message events fire inside the transaction after the save; MessageSaving fires before it, has no PHP counterpart, and a listener error aborts the write; a listener refuses with contracts.Rejection. - contracts/rejection.go:
type Rejection struct { Field, Message string }with a value-receiverError() stringreturning "golem15.chat: rejected " + Field + ": " + Message. The doc comment explains that listeners return the value (not a pointer) and callers match it with errors.As, because Fire joins listener errors. - classes/service.go
SendMessageWith: after the ErrEmptyMessage check and beforelagoon.Transaction, whens.bus != nil, fire&events.MessageSaving{Op: events.OpCreate, ConversationID, ActorID: senderID, RootID: rootID, Content: content}(the trimmed content) and returnnil, erron error. classes/writes.goEditMessage: after CanEditMessage allows the edit and the new content is validated, before its transaction, fire the same event withOp: events.OpUpdateand the MessageID. No other line of either method changes. - api/errors.go
writeChatError: before the existing switch, declarevar rej contracts.Rejectionand, whenerrors.As(err, &rej), callwriteValidation(w, map[string][]string{field: {rej.Message}})with field = rej.Field, or "content" when Field is empty, then return. The other branches stay byte-identical. - saving_smoke_test.go
TestMessageSavingTracer(Docker; skips under -short like the other HTTP tests): boot with bootWeb; register on the app's event bus a*events.MessageSavinglistener returningcontracts.Rejection{Field: "content", Message: "not allowed"}when Content contains the word "blocked"; create a group conversation with two participants through the harness; then- POST
/_chat/api/v1/conversations/{id}/messageswith content "this is blocked": 422, body errors.content equals ["not allowed"], and golem15_chat_messages has 0 rows; - POST the content "hello": 201, 1 row;
- PUT
/_chat/api/v1/messages/{id}with "blocked edit": 422, and the stored content is still "hello"; - POST
/_chat/api/v1/messages/{id}/replieswith "blocked reply": 422, and the row count is still 1.
- POST
- README.md: in Features and API reference, add MessageSaving (when it fires, no Tx, Op values), MessageSavingEventName, OpCreate, OpUpdate and contracts.Rejection, with a neutral example host listener (
acme). Add a changelog entry "v0.1.4: pre-save MessageSaving event and Rejection (additive; no listener means no change)". Name no consuming application.
Commit in ../sm-chat-plugin by path (feat: pre-save MessageSaving event and Rejection), README in the same commit. Do not push or tag.
go -C ../sm-chat-plugin vet ./... && go -C ../sm-chat-plugin test -count=1 -short ./... && go -C ../sm-chat-plugin test -count=1 -run '^TestMessageSavingTracer$' -v . 2>&1 | grep -q -- '^--- PASS: TestMessageSavingTracer'
<fails_when>Non-zero exit: vet or the short suite red (php_method_map or golden tests broken by the change), or no "--- PASS: TestMessageSavingTracer" line (Docker unavailable so it skipped, a 201 where 422 was expected, or a stored row after a refusal).</fails_when>
<acceptance_criteria>
- go -C ../sm-chat-plugin test -count=1 ./... (with Docker) passes, including the unchanged php_method_map_test.go and golden_test.go.
- git -C ../sm-chat-plugin diff HEAD~1 --stat -- php_method_map_test.go golden_test.go testdata prints nothing.
- grep -c 'MessageSavingEventName = "golem15.chat.message.saving"' ../sm-chat-plugin/events/events.go prints 1.
- grep -c 'errors.As(err, &rej)' ../sm-chat-plugin/api/errors.go prints 1.
- grep -c 'v0.1.4' ../sm-chat-plugin/README.md prints at least 1.
- The SUMMARY records the before and after HEAD of all seven siblings, and each after-HEAD equals origin's default branch.
</acceptance_criteria>
A host can refuse a chat message before it is stored, the client gets the existing 422 envelope, and without a listener chat behaves byte-identically.
- New package events (events/events.go):
PostSavingEventName = "golem15.forum.post.saving";PostSavingwithContextType string,ContextID,ActorID,ThreadIDandPostID uint,Title,BodyandOp string;- constants
OpThread = "thread"(ThreadID 0, Title set),OpReply = "reply"andOpUpdate = "update". - The package doc says forum fires no post-save events, PostSaving is a Go-only seam fired before render and persistence, and a listener error aborts the write.
- contracts/rejection.go: the same shape as chat's, with "golem15.forum: rejected " in Error().
- ForumService, all guarded by
s.bus != nil, firing after the access and required-field checks and beforebreakwater.Render, returning the error unchanged:- CreateThread fires PostSaving with OpThread, the trimmed title and the body;
- Reply fires it with OpReply, the ThreadID and the body;
- EditPost (lifecycle.go) fires it with OpUpdate, the PostID, its ThreadID and the body.
- api/errors.go
writeForumError: before the switch,errors.As(err, &rej)writes 422{rej.Field: [rej.Message]}, with field "body" when Field is empty. - saving_smoke_test.go
TestPostSavingTracer(Docker): boot through bootWeb with the fixture resolver that allows posting; register a PostSaving listener rejecting Title or Body containing "blocked" (Field "title" or "body"). Then:- POST a thread whose title holds the word: 422 errors.title, no thread and no post row;
- a clean thread: 201;
- a reply whose body holds the word: 422 errors.body;
- PUT the first post with the word: 422, and content_html is unchanged.
- README: add Features "Pre-save seam" and the API reference rows (events.PostSaving, PostSavingEventName, Op constants, contracts.Rejection), and correct the Overview so it says forum fires only this pre-save event. Add a changelog line "v0.1.0: first tag; adds the pre-save PostSaving seam". Name no application.
Commit in ../sm-forum-plugin by path (feat: pre-save PostSaving event and Rejection). Do not push or tag.
go -C ../sm-forum-plugin vet ./... && go -C ../sm-forum-plugin test -count=1 -short ./... && go -C ../sm-forum-plugin test -count=1 -run '^TestPostSavingTracer$' -v . 2>&1 | grep -q -- '^--- PASS: TestPostSavingTracer'
<fails_when>Non-zero exit: vet or the short suite red, or no "--- PASS: TestPostSavingTracer" line (skipped without Docker, a refused write that still stored a row, or the wrong 422 field).</fails_when>
<acceptance_criteria>
- go -C ../sm-forum-plugin test -count=1 ./... passes with Docker, php_method_map_test.go and golden_test.go unedited (git -C ../sm-forum-plugin diff HEAD~1 --stat -- php_method_map_test.go golden_test.go prints nothing).
- grep -rn 'sm-chat-plugin' ../sm-forum-plugin/go.mod ../sm-forum-plugin/events ../sm-forum-plugin/contracts prints nothing.
- grep -c 'PostSaving{' ../sm-forum-plugin/classes/forum_service.go prints 2 and grep -c 'PostSaving{' ../sm-forum-plugin/classes/lifecycle.go prints 1.
</acceptance_criteria>
Forum threads, replies and edits can be refused before render and storage with the existing 422 envelope; without a listener nothing changes.
- go.mod: go 1.27.0, require
git.golem15.com/golem15/summercms v0.5.1plus gorm and gormigrate at the versions sitemap's go.mod uses, andreplace git.golem15.com/golem15/summercms => ../summercms.go. Rungo mod tidy. Track a go.work withuse .and the same replace, as sitemap does. - plugin.go: the interface assertions (party.Plugin, pact.HasConfig, pact.HasMigrations, pact.HasModels) and
//go:embed config. Register keeps the app. Boot calls lagoon.OnDatabase and publishesclasses.NewFilter(db)withapp.Publish. The package doc says the plugin is a content filter other plugins' hosts wire into their pre-save seams, and that it imports no content plugin. - config/config.yaml:
max_entries: 500,max_entry_length: 200. - models/settings.go:
Settingssingleton ongolem15_moderation_settings(ID uint,Enabled bool,BannedWords *string,BannedLinks *string).BeforeValidaterefuses:- a list longer than max_entries (lang key
golem15.moderation::lang.errors.too_many); - an entry longer than max_entry_length (
errors.too_long); - a link entry that is neither a host name nor an http(s) URL (
errors.link). models/registry.goAll().
- a list longer than max_entries (lang key
- models/settings/fields.yaml:
enabled(switch),banned_words(textarea, comment "one word or phrase per line"),banned_links(textarea, comment "one domain or URL per line; subdomains match"), with the sitemap header comment block. - updates/202610280001_create_golem15_moderation_settings.go:
CREATE TABLE IF NOT EXISTS golem15_moderation_settings (id INTEGER PRIMARY KEY, enabled BOOLEAN NOT NULL DEFAULT TRUE, banned_words TEXT NULL, banned_links TEXT NULL)andINSERT INTO golem15_moderation_settings (id) VALUES (1) ON CONFLICT (id) DO NOTHING. Rollback drops the table. updates/registry.goAll(). - admin.go:
Settings()returns item Codemoderation_settings(lang keys for label, description and category, Icon "shield", Permissions [golem15.moderation.manage_settings], Formmodels/settings/fields.yaml, NewModel), plus AdminFS and LangFS, with the sitemap assertions (AdminAssets, HasSettings, HasLang). admin_permissions.go declares the permission on the role list sitemap uses. - lang/en and lang/pl: plugin name, settings label, description and category, field labels and comments,
errors.*,violation.word("The text contains a word that is not allowed." / "Tekst zawiera niedozwolone słowo.") andviolation.link("The text contains a link that is not allowed." / "Tekst zawiera niedozwolony link."). - classes/filter.go:
KindWord = "word",KindLink = "link";Violation{Kind, Match, Message string};ParseList(text string) []stringsplits lines, trims them, lowercases them and drops empty lines and duplicates;Match(words, links []string, text string) *Violationis pure and returns the first violation, words before links:- a word or phrase matches case-insensitively between non-letter, non-digit boundaries (built from
[^\p{L}\p{N}_], start or end of text) with regexp.QuoteMeta; - a link entry that is a host (example.com) matches any host in the text equal to it or ending in "." plus it: http(s) URLs,
www.prefixes and bare domains (labels of letters, digits and hyphens with at least one dot); - an entry with a path matches a URL whose host and path start with it.
- a word or phrase matches case-insensitively between non-letter, non-digit boundaries (built from
NewFilter(db) *Filter.(*Filter).Check(ctx, text) (*Violation, error)reads the singleton row, returns nil when Enabled is false, recompiles the matchers only when the stored text differs from the cached text (guard the cache with a sync.Mutex), and fills Message from the lang phrase fortowel.Locale(ctx)through the framework phrasebook, falling back to the English text.
- classes/filter_smoke_test.go
TestFilterSmoke(pure, no Docker): "Spam here" against the word spam gives a word violation; "spamming" gives none; "Kup TANIO teraz" against the phrase "kup tanio" gives a word violation; "visit https://www.bad.example/x" and "bad.example" against the link bad.example give link violations; "good.example" gives none. - README.md in the standard plugin structure:
- H1, one-sentence summary, import line, a
**Name:**beach mnemonic, Overview, Features, Usage, API reference, Configuration (the two keys), Dependencies, Testing; - Usage shows a neutral host (
acme) wiring Check into another plugin's pre-save event without importing it here.
- H1, one-sentence summary, import line, a
Commit in ../sm-moderation-plugin (feat: golem15.moderation banned word and link filter). Do not create a remote, push or tag.
go -C ../sm-moderation-plugin vet ./... && go -C ../sm-moderation-plugin test -count=1 -short ./... && go -C ../sm-moderation-plugin test -count=1 -run '^TestFilterSmoke$' -v ./classes 2>&1 | grep -q -- '^--- PASS: TestFilterSmoke'
<fails_when>Non-zero exit: the module does not build or vet, the short suite fails, or no "--- PASS: TestFilterSmoke" line (a boundary or host rule wrong).</fails_when>
<acceptance_criteria>
- go -C ../sm-moderation-plugin list -deps ./... | grep -cE 'sm-(chat|forum)-plugin' prints 0.
- grep -c 'golem15_moderation_settings' ../sm-moderation-plugin/updates/202610280001_create_golem15_moderation_settings.go prints at least 2.
- grep -c 'golem15.moderation.manage_settings' ../sm-moderation-plugin/admin_permissions.go prints at least 1.
- grep -c '^\*\*Name:\*\*' ../sm-moderation-plugin/README.md prints 1.
- git -C ../sm-moderation-plugin remote prints nothing.
</acceptance_criteria>
A shared, chat-agnostic moderation plugin exists locally: admins edit banned words and links in settings, and any host can call Filter.Check from a pre-save seam.
Then verify the family:
- all eight repos (chat, chatchannels, chatbots, chatvideo, forum, herald, userfriends, moderation) pass
go vet ./...andgo test -count=1 -short ./...through their go.work; - chatchannels, chatbots, chatvideo, herald and userfriends pass
GOWORK=off go build ./..., which resolves chat v0.1.3 and user v0.1.13 from git.golem15.com and proves no sibling path is needed. Grep the changed files of all eight repos for consuming application names (the sm-*-app repository names next to summercms.go, and their vendor prefixes) and remove any hit in the files this plan changed.
Commit per repo by path (chore: require tagged chat, user and SummerCMS modules; drop sibling replaces). Do not push or tag.
for r in sm-chat-plugin sm-chatchannels-plugin sm-chatbots-plugin sm-chatvideo-plugin sm-forum-plugin sm-herald-plugin sm-userfriends-plugin sm-moderation-plugin; do go -C ../$r vet ./... && go -C ../$r test -count=1 -short ./... || exit 1; done && for r in sm-chatchannels-plugin sm-chatbots-plugin sm-chatvideo-plugin sm-herald-plugin sm-userfriends-plugin; do GOWORK=off GOPRIVATE='git.golem15.com/*' go -C ../$r build ./... || exit 1; done
<fails_when>Non-zero exit: any repo fails vet or its short suite, or a GOWORK=off build fails (for example "unknown revision v0.0.0" or a sibling replace path that no longer resolves).</fails_when>
<acceptance_criteria>
- grep -cE '^replace .*=> \.\./(sm-|fonoteka)' ../sm-chatvideo-plugin/go.mod ../sm-herald-plugin/go.mod ../sm-userfriends-plugin/go.mod prints 0 for each file.
- grep -c 'v0.0.0' ../sm-chatvideo-plugin/go.mod ../sm-userfriends-plugin/go.mod prints 0 for each file.
- grep -c 'sm-chat-plugin v0.1.3' ../sm-chatvideo-plugin/go.mod ../sm-userfriends-plugin/go.mod prints 1 for each file.
- git -C ../sm-<repo> status --porcelain prints nothing for all eight repos after the commits.
</acceptance_criteria>
Every chat-family module resolves its dependencies by tag, so a demo build without go.work can require them.
<threat_model>
Trust Boundaries
| Boundary | Description |
|---|---|
| chat/forum HTTP clients to the plugin APIs | message and post bodies are untrusted input; the seam runs on them before storage |
| host listeners to plugin services | host code decides refusals; a listener error must not leak internals |
| admin settings to the filter | administrators edit the lists that every message is matched against |
| build machine to git.golem15.com and module proxies | tags become immutable inputs of every consumer |
STRIDE Threat Register
| Threat ID | Category | Component | Severity | Disposition | Mitigation Plan |
|---|---|---|---|---|---|
| T-20-01 | Tampering | chat write paths that skip the seam | high | mitigate | MessageSaving fires in SendMessageWith (SendMessage, replies and ReplyTo funnel into it) and EditMessage; TestMessageSavingTracer covers send, reply and edit; plan 06 adds the full matrix |
| T-20-02 | Information disclosure | listener errors surfacing in API bodies | medium | mitigate | only contracts.Rejection maps to 422 with its own Field and Message; any other listener error keeps the existing opaque 500 path of writeChatError and writeForumError |
| T-20-03 | Denial of service | filter matching cost | medium | mitigate | RE2 linear-time regexps from QuoteMeta'd entries; at most 500 entries of at most 200 characters per list (BeforeValidate); matchers compiled once per list version |
| T-20-04 | Elevation of privilege | moderation settings screen | medium | mitigate | settings item behind the permission golem15.moderation.manage_settings, granted to the same role as sitemap settings |
| T-20-05 | Tampering | one-way module tags | medium | mitigate | tags only on HEADs that passed vet and tests in Tasks 1-4; next free number read from the remote; go-ahead at Task 5; ls-remote check and a GOWORK=off scratch build after pushing |
| T-20-SC | Tampering | npm/pip/cargo installs | high | mitigate | no package-manager install: Go modules are the project's own tagged repositories plus gorm and gormigrate at versions already in sm-sitemap-plugin's go.sum (GOPRIVATE, go.sum committed) |
| </threat_model> |
<success_criteria> The chat family and the moderation plugin are released by tag (SC-1 prerequisite), with the D-18 seams additive and parity-safe and the D-17 filter shared and chat-agnostic. </success_criteria>
Create `.planning/phases/20-demo-instance-with-every-shared-plugin/20-01-SUMMARY.md` when done: per repository the before and after HEAD, the tag and its commit, the go.mod changes, how the moderation repository was created, and the checkpoint answer.