docs: add Sentova as a worked custom-name adapt example#108
Merged
Conversation
Document the household pest-monitor "Sentova" spec across the three doc
surfaces as a worked example of the custom-project-name path. Verified
2026-05-25 (agent 0.2.1, VISUAL=0): generate overall PASS, walked on iOS +
Android via the plugin's generate-app + walk-app skills.
- plugin/README.md: full generate -> walk-app session with the project name
passed in plain language ("project name is Sentova").
- README.md: Usage example tying --project-name to the plugin/MCP plain-language
form; kept out of the VISUAL=2 matrix table.
- docs/SPEC.md: add the household pest-sighting log to the SS4 adapt-path variants.
Framed accurately as an *adapt* (keeps the ItemTag toggle, renamed/extended),
not a replace; planner rename targets vary run to run, so mappings are cited as
one run's pick.
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
1 participant
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.
What
Documents the household pest-monitor Sentova spec across the three doc surfaces as a worked example of the custom-project-name path, and adds the household pest-sighting variant to the SPEC's adapt-path list.
Verified 2026-05-25 (agent
0.2.1,VISUAL=0):generate-appoverall PASS (Layer 1 3/3 · Layer 2 3/3 fast · reviewer PASS), thenwalk-appdriven on iOS + Android, via the plugin's two skills.Changes
plugin/README.md— fullgenerate-app→walk-appsession, with the project name passed in plain language (project name is Sentova).README.md— Usage example tying--project-name="Sentova"to the plugin/MCP plain-language equivalent. Deliberately kept out of theVISUAL=2matrix table (this was aVISUAL=0generate + interactive walk, not a full Layer-3 run).docs/SPEC.md— add "household pest-sighting log" to the §4 adapt-path variants.Framing notes (accuracy)
ItemTagtwo-state toggle and renames/extends it (Shop→Household,Shopkeeper→Resident,ItemTag→Sighting,Idled→Active,Completed→Resolved). The custom name (out/sentova/,Sentova.xcodeproj,Sentova API) comes from theprojectNamepath (src/dispatch.ts, CLI--project-name, MCPgenerate_app), independent of the domain rename.ItemTag→Detection), so mappings are cited as "one run's pick," not fixed.Docs-only; no code changes.
🤖 Generated with Claude Code