fix: serialize property writes and expose n8n results

- Serialize property set and remove commands per vault note to avoid lost frontmatter writes.
- Wait briefly for successful property writes to hit disk before releasing the note lock.
- Return property path, name, value, type, operation, and ok status in n8n outputs.
- Include property details on continue-on-fail errors so failed items are visible in n8n.
- Bump obsidian-api to 1.0.7 and n8n-nodes-obsidian-cli-api to 0.2.8.
- Add regression coverage for concurrent property writes to the same note.

packages/n8n-nodes-obsidian-api/nodes/ObsidianApi/output.ts

@@ -1,6 +1,7 @@
 import type { IDataObject, INodeExecutionData } from 'n8n-workflow';
 
 import type { ObsidianCommandResult } from '../../shared/ObsidianApiClient';
+import { propertyDetailsFromArgs } from './propertyOutput';
 
 export function outputForResult(result: ObsidianCommandResult, resource: string, operation: string, itemIndex: number): INodeExecutionData {
 	const stdout = result.stdout ?? '';
@@ -17,6 +18,9 @@ export function outputForResult(result: ObsidianCommandResult, resource: string,
 	if (resource === 'property' && (operation === 'propertyRead' || operation === 'properties')) {
 		return paired({ content: stdout }, result, itemIndex);
 	}
+	if (resource === 'property' && (operation === 'propertySet' || operation === 'propertyRemove')) {
+		return paired({ ok: true, operation, ...propertyDetailsFromArgs(result.command) }, result, itemIndex);
+	}
 
 	const parsed = result.parsed_stdout;
 	if (parsed) return paired(parsed, result, itemIndex);