Harbor Operations packages a manifest checker as an image-based function. Its application selects a subnet and compute architecture; the function then selects an image, memory and timeout. Those settings need to agree with the workload without being mistaken for a successful invocation.
Create a local application and function definition using the current container-function command. The image reference is fictional and immutable. The browser never pulls it, authenticates to a registry or invokes a handler. It also does not connect a queue trigger. Review the identity, network and execution evidence that a real deployment would need before promising that a manifest was processed. Configuration is useful evidence, but it is only one boundary in the complete event workflow.
Application, image, limits and actual execution are separate review items.