Repository navigation
Ctxo v0.18.0
Packages published in this release
@ctxo/cli@0.18.0— https://www.npmjs.com/package/@ctxo/cli/v/0.18.0@ctxo/domain@0.18.0— https://www.npmjs.com/package/@ctxo/domain/v/0.18.0@ctxo/lang-csharp@0.11.0— https://www.npmjs.com/package/@ctxo/lang-csharp/v/0.11.0@ctxo/lang-go@0.12.0— https://www.npmjs.com/package/@ctxo/lang-go/v/0.12.0@ctxo/lang-java@0.13.0— https://www.npmjs.com/package/@ctxo/lang-java/v/0.13.0@ctxo/lang-java-analyzer@0.13.0— https://www.npmjs.com/package/@ctxo/lang-java-analyzer/v/0.13.0@ctxo/lang-typescript@0.11.0— https://www.npmjs.com/package/@ctxo/lang-typescript/v/0.11.0@ctxo/plugin-api@0.9.2— https://www.npmjs.com/package/@ctxo/plugin-api/v/0.9.2
Compatible set
Versions tested together in this release:
| Package | Version |
|---|---|
@ctxo/cli |
0.18.0 |
@ctxo/domain |
0.18.0 |
@ctxo/lang-csharp |
0.11.0 |
@ctxo/lang-go |
0.12.0 |
@ctxo/lang-java-analyzer |
0.13.0 |
@ctxo/lang-java |
0.13.0 |
@ctxo/lang-sql |
0.1.0 |
@ctxo/lang-typescript |
0.11.0 |
@ctxo/plugin-api |
0.9.2 |
@ctxo/sql-extract |
0.1.0 |
CLI changelog
Minor Changes
- 0d185f3: Cursor gets a fold reminder. Cursor's
stophook cannot block, so with@ctxo/domainctxo init --domain(Cursor selected) now registersctxo domain-cursor-hookin.cursor/hooks.jsonforbeforeSubmitPromptandstop, merged into the hooks already there. The first prompt of a conversation records where it starts; every prompt gets exactly{"continue":true}(also without@ctxo/domainand on any error), and a repeat prompt answers without loading the module or running git. On astopwithstatus: "completed"the reminder runs the Claude Code fold guard's own decision and, when the guard would block, prints{"followup_message":"ctxo domain reminder: ..."}with the guard's reason. At most once per conversation (else per generation, else per 10 minutes), quiet while a follow-up runs, withdomain.guard.enabled: falseand on any error; it never blocks and always exits 0; an aborted or errored stop prints nothing.domain.guard.enabled: falsealso keeps init and doctor from adding the entries.ctxo doctorreports a missing, duplicated or unreadable reminder entry underdomain_agent_setupwhen.cursor/exists, andctxo doctor --fixnow repairs the domain agent setup (loader rules, the Claude Code guard hooks, the Cursor reminder, thectxo-domain-foldskill), keeping other hooks and never writing an unreadable file. Module API:CtxoModuleRegistration.doctorFixes(ModuleDoctorFix,DoctorFixContext). - 5d47390:
index.testsglobs now reach the language plugins.@ctxo/plugin-apiadds an optionalPluginContext.testGlobs(type-only and additive, so the plugin peer ranges are unchanged);@ctxo/clisets it inctxo indexandctxo watchto the default test globs followed by the validindex.testsglobs, each once.@ctxo/lang-typescriptdecides test blocks (describe,it,test), their edges, SQL call-site scopes and fact owners with those globs, soindex.tests: ["spec/**/*.check.ts"]makes the blocks ofspec/loans/policy.check.tstest symbols. With a CLI that predates the field, the TypeScript plugin keeps its built-in default rule. Behaviour change: a current CLI sends all its default test globs, including**/*.Tests/**and**/*.Test/**, so TypeScript files under such folders now get test blocks.index.testsdoes not support negation: a!entry is skipped (it no longer turns every other file into a test file in the contexts view), the TypeScript plugin skips one too, andctxo doctorwarns and names it (useindex.ignoreto leave files out). Re-runctxo indexafter upgrading or changingindex.tests. - 49a000f:
ctxo watchnow refreshes the domain artifacts. With@ctxo/domaininstalled, watch runs the domain index pass (the onectxo indexruns) after the re-index of the changed files, sograph.json,maturity.json,shadow-candidates.json,contexts.jsonandboundaries.jsonfollow your edits and the domain tools stop answeringstale: true. A registry, card or glossary edit runs the pass after a quiet period of 1 s, or twice the last pass when that is longer; changed source files run it oncewatch.snapshotMinFileChangesof them are pending, 5 s after the last event; a due pass is never postponed more than 30 s; at start, one pass runs only when the graph is stale. For the same index at the same commit the pass writes the bytesctxo indexwrites; the change-log fields (moved files, discovery, history) keep the values of the lastctxo index. A registry created while watch runs gets no pass (no facts were requested), with a warning on each skipped pass until watch is restarted. Passes never overlap, a failing pass is logged and watch goes on, and without@ctxo/domainwatch behaves as before. The stale hints now name the watch refresh.shadow-candidates.jsonnow writes factdetailkeys in codepoint order, so a full and an incremental run give the same bytes. Module API:classifyWatchPath(path, indexed),watchArtifactsStale()andIndexPassContext.factsRequested.
Patch Changes
- e838b4d: Normalization facts are business normalization (FC-4b). Many
normalizationfacts were not. Every tier of the C#, TypeScript, Java and Go plugins now reports the nearest call that receives a normalized value (its consumer, up to the statement and never past a lambda), with its receiver and declaring types in the full tiers, and the shared finisher drops the fact when that consumer is a message sink: a logging method on a known logger type (Microsoft.Extensions.Logging, Serilog, NLog, log4net,System.Diagnostics.Debug/Trace, java.util.logging, SLF4J, log4j, commons-logging, Golog,log/slog, logrus, zap, zerolog, and in TypeScriptConsole, pino, winston, NestJSLogger/LoggerService, bunyan, log4js, tslog), the same methods on a logger-named receiver in every tier whenever no known logger type resolves, or an exception or error construction (new ...Exception,new Error,errors.New,fmt.Errorf).auth.LogInorwriter.WriteLineare no sinks, andlog.info("saved", repo.upsert(email.toLowerCase()))keeps its fact. Display text (an interpolation hole or+operand next to text with whitespace) is dropped only when it goes to a sink or a formatting API (StringBuilder.Append*,string.Format,fmt.Sprintf,Console.Write*); SQL templates and space-joined keys keep their facts. Calls on formats (Pathand character calls, hex or base64 output, file extensions, separator-only trims) give none, and a chain is one fact, the outermost call, also across lines.ctxo indexandctxo watchdropnormalizationfacts in test files, as they dropretry-timeoutfacts; the@ctxo/domaintext scan applies the sink rule to the call enclosing a normalization on its line. Thecallevidence gainsconsumer,consumerTypesandinProse, with new conformance vectorsisMessageSink,isDisplayCall,isTechnicalNormalizationandfeedsNormalization. The Java full tier needs@ctxo/lang-java-analyzerat this release (runctxo update); an older JAR reports no consumers, so only the format, chain and test-file rules apply there. Ashadow-specs.yamlresolution recorded for a dropped call, such as the inneremail.Trim()of a chain, turns stale (check 12 warns) and can be removed. - Updated dependencies [5d47390]
- Updated dependencies [e838b4d]
- @ctxo/plugin-api@0.9.2