[l1ttps]

Summary

Syncs core-api/resources/connectors/manifest.json with oasm-platform/oasm-connectors#37, which adds matchRegex / filterRegex URL filters to the katana, gau, ffuf, dirsearch and arjun connectors. Users can now target specific pages (login, admin, …) from a tool config profile or a workflow step's inline config.

Related: #746.

• matchRegex — report only URLs matching at least one pattern
• filterRegex — drop URLs matching any pattern (wins over matchRegex)

Patterns are Go RE2, matched against the full URL.

The sync also picks up nessus 0.2.0 (disableTlsChecks), which is already on oasm-connectors main; task sync-connectors from main produces the same change.

No core-api / console code changes

Everything is schema-driven:

• core-api validates profiles and inline config with Ajv against the connector configSchema (maxItems: 20, minLength: 1, maxLength: 512) and ships the config to the worker unchanged.
• The console renders both fields from the schema. SchemaForm seeds array fields with [""], and normalizeValues drops empty strings on submit, so saving a config without patterns still passes minLength: 1.

Merge order

Merge oasm-connectors#37 first and publish the connector images. Until then, the new keys reach connector images that ignore them (no error, no filtering).

Testing

• Rebuilt the compose stack with this manifest and the rebuilt connector images: migration exit 0, API logs Connector registry loaded 15 connector(s), worker connected.
• In the console, created a project with katana, gau, ffuf, dirsearch and arjun steps and set both pattern lists inline; the stored workflow (workflows.content) carries matchRegex / filterRegex for all five jobs.